SendKit logoSendKit
SendKit MCP

Let AI agents run your email marketing.

Connect Claude, ChatGPT, or any MCP client to SendKit. Agents can design on-brand newsletters, preview them, and schedule campaigns with your approval.

Brand-aware design

Agents read your theme, logo, header, and footer, then build newsletters with structured blocks that stay editable.

Preview before sending

Render drafts, check warnings and spam scores, and send tests before anything reaches your audience.

Human-approved scheduling

Scheduling requires explicit confirmation and returns recipient count and quota impact first.

Endpoint and authentication

SendKit exposes a stateless Streamable HTTP MCP server. Every request uses the public API key as the identifier and the secret key as the credential. Custom clients can send an HMAC X-Signature over the raw request body instead of X-Secret-Key.

https://send-kit.com/mcp
Authorization: Bearer pk_your_public_key
X-Secret-Key: sk_your_secret_key

Scopes

ScopeAllows
readBrand, block schema, newsletters, analytics, segments, audience summary, templates, products, quota
draftCreate, update, preview, duplicate, and delete newsletters
sendSend test, schedule, and pause campaigns

Tools

Read
  • get_brand
  • get_block_schema
  • list_newsletters
  • get_newsletter
  • get_newsletter_analytics
  • list_segments
  • get_audience_summary
  • list_templates
  • get_template
  • list_products
  • get_quota
  • get_usage_guide
Draft
  • create_newsletter
  • update_newsletter
  • render_newsletter_preview
  • duplicate_newsletter
  • delete_newsletter
Send
  • send_test_newsletter
  • schedule_newsletter
  • pause_newsletter

Design with blocks

Blocks are the recommended design mode. SendKit renders them with your theme, logo, header, and footer, and the result stays editable in the visual editor.

  1. Call get_brand and get_block_schema.
  2. Create a draft with content.mode = "blocks".
  3. Call render_newsletter_preview and review warnings.
  4. Refine with update_newsletter.
  5. Send a test, then call schedule_newsletter. The MCP client asks the user to confirm.
{
  "title": "Weekly update",
  "subject": "What's new this week",
  "content": {
    "mode": "blocks",
    "blocks": {
      "selectedBlocks": [
        { "id": "hero", "name": "Rich Text" },
        { "id": "cta", "name": "Button" }
      ],
      "blockContents": {
        "hero": { "body": "<h1>Hello {{first_name}}</h1>" },
        "cta": { "text": "Read more", "href": "https://example.com" }
      }
    }
  }
}

HTML fallback

HTML is supported for advanced layouts. HTML newsletters are not editable in the visual editor and must include an unsubscribe link.

{
  "title": "Launch announcement",
  "subject": "We launched",
  "content": {
    "mode": "html",
    "html": "<h1>We launched</h1><a href=\"{{unsubscribe_link}}\">Unsubscribe</a>"
  }
}

Scheduling safely

MCP clients ask the user to confirm through the client's elicitation UI before the server commits a schedule. The REST v1 endpoint uses the same action and requires an explicit confirm: true field. The response includes the recipient count and quota impact, so agents can show both before sending. Pausing also asks the user to confirm.

{
  "newsletterId": "newsletter-id",
  "scheduledAt": "2026-11-20T09:00:00.000Z",
  "segmentId": "optional-segment-id",
  "confirm": true
}

Agent discovery

Agents can find the documentation and server metadata at these stable URLs:

  • https://send-kit.com/docs/mcp
  • https://send-kit.com/docs/mcp.md
  • https://send-kit.com/llms.txt
  • https://send-kit.com/.well-known/mcp.json

Connected agents can also call get_usage_guide or read the sendkit://docs resource.