MCP Server

The Splashify Pro MCP server lets your AI assistant (Claude Desktop, Cursor, Windsurf, Claude Code, etc.) call the Email API directly. Send emails, verify identities, configure webhooks — all from a chat conversation.

Model Context Protocol is the open standard Anthropic shipped for connecting AI tools to external APIs. Splashify Pro hosts an MCP server that exposes every public endpoint as a tool the assistant can call.

Endpoint

The MCP server is hosted — there's nothing to install locally. Point your AI client at the SSE endpoint and authenticate with your Email API key:

URL:    https://mcp.splashifypro.com/sse
Auth:   Authorization: Bearer pk_live_...

Use the same pk_live_… key you use for the REST API (generate one at email.splashifypro.com → Settings → API Key). The MCP server uses the same auth chain, permission scope, and rate-limit budget as REST.

Add to Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "splashifypro": {
      "type": "sse",
      "url": "https://mcp.splashifypro.com/sse",
      "headers": {
        "Authorization": "Bearer pk_live_..."
      }
    }
  }
}

Restart Claude Desktop. You'll see "splashifypro" in the bottom-left tools menu.

Add to Cursor

Edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "splashifypro": {
      "type": "sse",
      "url": "https://mcp.splashifypro.com/sse",
      "headers": {
        "Authorization": "Bearer pk_live_..."
      }
    }
  }
}

Add to Claude Code

Edit ~/.claude/settings.json or your project's .mcp.json:

{
  "mcpServers": {
    "splashifypro": {
      "type": "sse",
      "url": "https://mcp.splashifypro.com/sse",
      "headers": {
        "Authorization": "Bearer pk_live_..."
      }
    }
  }
}

Add to Windsurf

Edit ~/.codeium/windsurf/mcp_config.json. Same JSON shape as Cursor.

Available tools

The MCP server exposes 35+ tools, one per Email API endpoint:

Category	Tools
Send	`partner_email_send`, `partner_email_send_template`, `partner_email_send_bulk`, `partner_email_send_raw`, `partner_email_get_status`
Identities	`partner_email_list_identities`, `partner_email_create_identity`, `partner_email_get_identity`, `partner_email_verify_identity`, `partner_email_delete_identity`
Configuration sets	`partner_email_list_configuration_sets`, `partner_email_create_configuration_set`, `partner_email_get_configuration_set`, `partner_email_delete_configuration_set`
Event destinations	`partner_email_create_event_destination`
Templates	`partner_email_list_templates`, `partner_email_create_template`, `partner_email_delete_template`, `partner_email_preview_template`
Suppression	`partner_email_list_suppression`, `partner_email_add_suppression`, `partner_email_remove_suppression`
Stats + reputation	`partner_email_get_quotas`, `partner_email_get_stats`, `partner_email_get_reputation`, `partner_email_list_events`, `partner_email_get_bounce_report`
Production access	`partner_email_list_production_access_requests`, `partner_email_submit_production_access`
Dedicated IP	`partner_email_get_dedicated_ip_request`, `partner_email_request_dedicated_ip`, `partner_email_cancel_dedicated_ip_request`
Account + security	`partner_email_list_activity_logs`, `partner_email_list_ip_allowlist`, `partner_email_add_ip_allowlist_entry`, `partner_email_remove_ip_allowlist_entry`

Example prompts

"Send a welcome email to [email protected] from [email protected]"

The assistant calls partner_email_send with the right shape, hands the message_id back to you, and offers to follow up via partner_email_get_status.

"Verify the domain mycompany.com and tell me which DNS records I need"

partner_email_create_identity is called, the response includes the SPF / DKIM / DMARC records, and the assistant explains where to publish them.

"Why are 5% of my emails bouncing?"

partner_email_get_reputation + partner_email_list_events?event_type=bounce fire in parallel; the assistant correlates the bounces against recipients and suggests fixes.

Security

Hosted, not local. Your API key never leaves your machine except as a Bearer header on outbound HTTPS requests to mcp.splashifypro.com — same path your REST calls already take.
Mutating tools confirm first. Tools that change state (partner_email_send, partner_email_create_*, partner_email_delete_*) generally require the assistant to read back the action; you approve before they fire.
Audit log. Every MCP-driven call shows up at email.splashifypro.com → Activity Log alongside REST + SDK calls so you can see who/what fired which endpoint when.
Rate limits. MCP calls share the same per-key budget as REST. Burst protection kicks in identically.

Troubleshooting

"splashifypro server not found": check the JSON config path + restart the host app. SSE transport requires the host app to support remote MCP (Claude Desktop ≥ 0.7, Cursor ≥ 0.42, Claude Code ≥ 1.0).
401 invalid_key: API key is wrong or revoked. Generate a fresh one in Splashify Pro Email.
402 insufficient_balance: wallet is empty. Recharge from Splashify Pro Email.
429 rate_limited: assistant is firing too many requests too fast — back off or apply for production access to lift the per-second cap.

Feedback + bugs

Spotted a bug or want a tool that isn't listed? Email [email protected] with the prompt that triggered it and your pk_live_ key prefix (first 12 chars). We ship MCP fixes weekly.