Add to your IDE

Which method to use

• Copy prompt / Add with AI — fastest first click. Works in any chat. No install.
• Agent Skills — best for writing integration code into this repo. Install once, then say “add OTP email with Piisend.”
• MCP — best for live account actions (send a test, list domains, inspect a message) without changing app files.

Skills and MCP are complementary. Skills teach the agent to write correct REST code. MCP lets it call your Piisend account. Ground either path in llms.txt or the full dump at llms-full.txt.

1. Copy prompt or Add with AI

On any docs snippet, use Copy or Add with AI (Cursor, Claude, ChatGPT). Or paste one of these prompts into your IDE chat. Tell the agent to read https://piisend.com/llms.txt first.

Cursor / Windsurf / Copilot

Integrate Piisend email API into this codebase.

Context:
- Provider: Piisend — https://piisend.com/docs/api
- API: POST https://api.piisend.com/api/v1/emails
- Auth: Authorization: Bearer $PIISEND_API_KEY
- Machine-readable overview: https://piisend.com/llms.txt
- Full docs dump: https://piisend.com/llms-full.txt
- IDE guide: https://piisend.com/docs/ai

Tasks:
1. Add PIISEND_API_KEY to .env.example and read it from process.env / os.environ.
2. Create lib/email.ts (or equivalent) with sendEmail({ to, subject, html, text }) and sendTemplate({ to, templateId, vars, idempotencyKey? }).
3. Wire the existing auth/signup or password-reset path to call the module.
4. Use fetch (Node 18+) or httpx from Piisend docs—no Resend, SendGrid, or other mail SDK.
5. Log errors with status + response body; do not leak API keys.

Match this project's existing patterns for HTTP clients, env vars, and error handling.

ChatGPT / Claude / Gemini

You are a senior backend engineer. Help me integrate Piisend into my product.

Read first:
- https://piisend.com/llms.txt
- https://piisend.com/docs/getting-started
- https://piisend.com/docs/api

Piisend facts:
- API: https://api.piisend.com (POST https://api.piisend.com/api/v1/emails)
- Auth: Authorization: Bearer pii_… (env PIISEND_API_KEY)
- Templates: template_id + template_vars; placeholders are {{name}}
- Sender JSON field is from_ (not from)
- Domains: POST /domains, DNS verify, then from_ on sends
- Webhooks: delivery, bounce, complaint, open, click with HMAC-SHA256 on X-Webhook-Signature

Deliver:
1. Architecture (server-only — never expose the API key to the browser)
2. Env vars checklist
3. Code for my stack with Piisend REST calls
4. Production checklist: domain verification, webhooks, suppressions, rate limits

Do not invent Piisend features. If something is unclear, say so and point me to the doc URL.

2. Agent Skills

Skills are SKILL.md playbooks your coding agent loads automatically. They keep endpoints, env vars, and gotchas (from_ vs from, no browser keys) accurate.

Install every Piisend skill:

npx skills add raodevender/piisend

Or only the send-email skill:

npx skills add raodevender/piisend --skill piisend-send-email

• piisend-send-email — REST send, templates, idempotency, Next.js / Express / FastAPI file placement
• piisend-webhooks — HMAC verification, events, suppressions
• piisend-domains — DNS, verification, branded from_

Then ask: “Add a password-reset email with Piisend” or “Wire bounce webhooks.” The agent should match this repo’s patterns and call POST https://api.piisend.com/api/v1/emails only from server code.

3. MCP server

Connect Cursor or Claude to your Piisend account with an API key. The agent can send a test email, list recent messages, check domain verification, and list templates. It does not replace Skills for writing app code.

Cursor — mcp.json

{
  "mcpServers": {
    "piisend": {
      "command": "npx",
      "args": ["-y", "@piisend/mcp"],
      "env": {
        "PIISEND_API_KEY": "pii_xxxxxxxxx"
      }
    }
  }
}

Claude Code

claude mcp add piisend -e PIISEND_API_KEY=pii_xxxxxxxxx -- npx -y @piisend/mcp

Replace pii_xxxxxxxxx with a dashboard key that has emails:send (add emails:read and templates:read to list). Never commit the key.

Local HTTP (Bearer token)

npx -y @piisend/mcp --http --port 3333

{
  "mcpServers": {
    "piisend": {
      "url": "http://127.0.0.1:3333/mcp",
      "headers": {
        "Authorization": "Bearer pii_xxxxxxxxx"
      }
    }
  }
}

Tools: send_email, list_emails, get_email, list_domains, get_domain, list_templates, list_webhooks. Discovery: /.well-known/mcp.json.

One-click plugin

The Piisend plugin bundles Skills + MCP. In Cursor, browse the plugin from this repo or run /add-plugin piisend when listed in the marketplace. In Claude Code, install from the repository plugin manifest. Until then, use the Skills and MCP commands above.

Next steps

• Quickstart — API key and first POST /emails
• API reference — curl, JavaScript, Python
• AI product page — agents calling Piisend over HTTP