the MCP tools. Remote HTTP MCP with OAuth. Draft campaigns, send tests, build flows, manage contacts - from Claude, ChatGPT, Cursor, Codex, or Gemini. No API key juggling.
The Model Context Protocol is the open standard for connecting AI agents to tools. nitrosend is built MCP-first, not bolted on.
Every agent-facing marketing workflow is exposed as an MCP tool. No "use the dashboard for this" gaps.
One-click auth from inside your agent. Tokens never touch your terminal history.
Agents can read your account state, schema, and Brand Kit memory before they act.
Send-only MCPs give the agent one verb. nitrosend gives it the workflow surface for campaigns, flows, audiences, reviews, tests, and approvals.
Each prompt translates to one or more typed MCP tool calls. The agent plans the sequence, calls the tools, and reports back.
Every MCP action your AI agent can take. No partial implementations.
Analyze images and convert them into reusable email assets.
Draft a marketing campaign.
Build a multi-step automation flow.
Create rule-based contact segments.
Manage lists, tags, and subscriptions.
Find contacts by attributes or engagement.
Bulk import contacts from CSV.
Create and version on-brand templates.
Set brand colors, fonts, logo.
Add and verify sending domains.
Connect SES, Mailgun, Postmark for BYO.
Schedule, pause, or resend campaigns.
Inspect deliverability and bounces.
AI-generated performance insights.
Account context, sender identity, readiness, and dashboard links.
Send a preview before going live.
Free-form query against your account.
Persist brand voice and notes.
Open a support ticket from your agent.
Set account timezone, defaults, physical address.
View plan, usage, and billing info.
claude mcp add --transport http nitrosend https://api.nitrosend.com/mcpSettings → Connections → Customize → Add Connectors + → Add Custom Connector. Name it nitrosend, set the Remote MCP URL to https://api.nitrosend.com/mcp, then click Connect.
Add to .cursor/mcp.json:
{ "mcpServers": { "nitrosend": { "url": "https://api.nitrosend.com/mcp" } } }codex mcp add nitrosend --url https://api.nitrosend.com/mcp
codex mcp login nitrosendInstall the official nitrosend app from the ChatGPT app directory, then sign in. No config, no API key.
Add to ~/.gemini/settings.json:
{ "mcpServers": { "nitrosend": { "httpUrl": "https://api.nitrosend.com/mcp" } } }Windsurf, VS Code Copilot, Zed: see the integrations hub.
An email MCP server is a Model Context Protocol server that exposes email-platform operations as typed tools an AI agent can call. Instead of the agent scraping a dashboard or writing raw HTTP requests, it sees tools like nitro_compose_campaign, nitro_send_test_message, or nitro_search_contacts, calls them with structured arguments, and gets structured responses.
More than 20 tools, covering campaigns, automation flows, contacts, segments, templates, domains, providers, delivery control, insights, account, billing, Brand Kit memory, and support. App-triggered transactional sends stay in the REST API or SDK, while MCP handles drafts, tests, reviews, and approvals.
Claude Code, Claude Desktop, Claude.ai, Claude Cowork, Cursor, OpenAI Codex, ChatGPT (Developer Mode), Gemini CLI, Windsurf, VS Code Copilot, and Zed. Any client that speaks remote HTTP MCP with OAuth is supported.
No, for the supported clients above. OAuth handles auth in a browser window when you first connect. For stdio-only clients or local dev, the @nitrosend/mcp bridge accepts a NITROSEND_API_KEY environment variable.
Yes. Every plan including Free includes full MCP/API/CLI access. You only pay for emails sent and AI actions consumed, never for MCP access itself.
Yes, on Pro and above. Configure BYO (bring-your-own) sending keys for Amazon SES, Resend, Postmark, Mailgun, or SendGrid. The MCP tools route through your existing provider while Nitrosend handles templates, flows, contacts, and AI.