MCP Server

The Sendiee MCP server lets any Model Context Protocol-aware AI tool — Claude Desktop, Cursor, Antigravity, Continue, and others — drive your Sendiee account in natural language. Set up assistants, configure templates, schedule campaigns, pull reports, and audit billing without touching the dashboard.

We host it for you. There’s nothing to install on your machine — just point your AI tool at the URL below with your Sendiee API key.

Hosted Endpoint

The server exposes both transports on the same domain so old and new clients work:

• https://mcp.sendiee.com/mcp — Streamable HTTP (the 2025 standard). Use this for Claude Desktop, Cursor, claude.ai integrations, Antigravity.
• https://mcp.sendiee.com/sse — legacy SSE fallback for older MCP clients.
• https://mcp.sendiee.com/health — public liveness probe.

Machine-readable discovery card (serverInfo, transport, auth, capabilities): /.well-known/mcp/server-card.json.

Authentication

Every connection passes your Sendiee API key in a standard Authorization header:

Authorization: Bearer YOUR_SENDIEE_API_KEY

Get your key from Sendiee Dashboard → Settings → API Keys. The MCP server scopes your key to your session in memory only — it’s never logged and never shared across users.

Setup by client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Claude Desktop runs MCP servers as local stdio commands, so we bridge to the hosted URL through mcp-remote:

{
  "mcpServers": {
    "sendiee": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.sendiee.com/mcp",
        "--header",
        "Authorization:Bearer YOUR_SENDIEE_API_KEY"
      ]
    }
  }
}

Restart Claude Desktop. The Sendiee tools (hammer icon) and the 3 playbook prompts (typing /) appear within a few seconds.

Claude.ai (web)

Go to Settings → Integrations → Add custom MCP and paste:

• URL: https://mcp.sendiee.com/mcp
• Headers: Authorization: Bearer YOUR_SENDIEE_API_KEY

The web app speaks Streamable HTTP natively — no bridge needed.

Cursor

Edit ~/.cursor/mcp.json (or workspace .cursor/mcp.json):

{
  "mcpServers": {
    "sendiee": {
      "url": "https://mcp.sendiee.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SENDIEE_API_KEY"
      }
    }
  }
}

Other tools (Antigravity, Continue, etc.)

Any MCP-aware client that supports a remote URL + custom headers works. Use:

• URL: https://mcp.sendiee.com/mcp (or /sse if your client is older).
• Header: Authorization: Bearer YOUR_SENDIEE_API_KEY.

What the AI agent can do

The MCP server exposes 44 tools covering the full v2.0 surface, plus 3 named playbook prompts. Selected capabilities:

Example prompts to try

Once connected, just talk to the AI in plain English:

• “Set up a friendly WhatsApp customer-support assistant called ‘Acme Support’ using Claude Haiku.” — invokes the setup_whatsapp_assistant playbook.
• “How many people will receive a campaign to all VIP-tagged contacts in Mumbai?” — calls preview_campaign_audience.
• “Generate this week’s WhatsApp activity report.” — invokes the weekly_org_report playbook.
• “Show me what 919876543210 has been chatting about.” — calls get_chat_history.
• “What’s my current plan, balance, and channel health?” — calls get_org_summary.
• “Create a marketing template diwali_sale_2026 in en_US with body ‘Hi {{1}}, get 25% off. Use code {{2}}’ and a Shop Now button.” — calls create_template.

Health Check

Confirm connectivity from your machine before configuring the client:

curl https://mcp.sendiee.com/health

{
  "ok": true,
  "service": "sendiee-mcp",
  "version": "1.1.0",
  "time": "2026-04-29T20:54:33.232Z"
}

Security

• API keys are scoped per session and held in memory only — never logged, never shared between sessions.
• All traffic is HTTPS-only. The server enforces TLS via Cloudflare + Certbot.
• To revoke access, delete the API key in Sendiee Dashboard → Settings → API Keys. Active sessions on that key fail immediately on the next API call.
• Plan limits, rate limits, and per-org quotas all apply identically to MCP traffic — the AI agent can’t exceed them.

Troubleshooting