Nitrosend
Operate email campaigns, automations, transactional sends, contacts, and analytics from your agent through NitroSend’s MCP instead of clicking through a separate marketing UI.
Overview
NitroSend MCP is an MCP server for the Grow phase that exposes AI-native email campaigns, automations, transactional sends, contacts, and analytics to your agent.
What is this MCP server?
- AI-native email marketing via MCP (campaigns, automations, transactional)
- Contacts and analytics tools exposed to agents
- Remote streamable HTTP at api.nitrosend.com/mcp plus npm @nitrosend/mcp (v0.6.2)
- stdio transport option via npx -y for local MCP wiring
- Suites indie SaaS and ecommerce operators automating email from Claude Code or Cursor
- Package and server version 0.6.2 in registry metadata
- Five capability areas: campaigns, automations, transactional, contacts, analytics
- Two transports: streamable-http remote and npm stdio via npx
What problem does it solve?
Updating segments, triggering lifecycle emails, and checking campaign stats from a marketing UI slows agents that could orchestrate sends programmatically.
Who is it for?
Indie SaaS and ecommerce builders who already use or plan NitroSend and want agent-driven email operations.
Skip if: Pre-launch projects with no list or builders who need only DNS/JSON dev utilities.
What do I get? / Deliverables
Your agent can drive NitroSend campaigns, automations, transactional email, and analytics through MCP so growth work stays in your dev workflow.
- Agent-managed campaigns, automations, and transactional sends
- Contact operations and analytics queries via MCP
- Dual connect path: hosted remote or local npm MCP server
Recommended MCP Servers
Journey fit
Email marketing MCPs belong in Grow because solo builders use them after launch to nurture users, announce features, and run lifecycle programs. Lifecycle is the best subphase—campaigns, automations, and transactional email are core retention and activation mechanics, not SEO or support tickets.
How it compares
Email marketing lifecycle MCP, not observability (New Relic) or agent action governance (Neura Relay).
Common Questions / FAQ
Who is NitroSend MCP for?
Solo builders and small teams running NitroSend who want Claude Code, Cursor, or similar agents to manage email campaigns, automations, and analytics via MCP.
When should I use NitroSend MCP?
Use it in Grow when you are executing lifecycle email—onboarding drips, announcements, transactional messages—and want MCP tools instead of manual dashboard steps.
How do I add NitroSend MCP to my agent?
Either add remote https://api.nitrosend.com/mcp (streamable HTTP) or run npx -y @nitrosend/mcp for stdio per package registry metadata, following NitroSend auth requirements.