MCP Integrations

Cursor

Install the official Nitrosend plugin from the Cursor Marketplace and run your email marketing from Cursor's agent

Cursor + Nitrosend

Nitrosend is an official plugin on the Cursor Marketplace. Install it once and Cursor's agent gets the full Nitrosend tool set: compose emails, build automation flows, send campaigns, manage contacts and check analytics, all through conversation.

Setup

In Cursor's Agent chat, run:

/add-plugin nitrosend

Or install from the listing: Add Nitrosend to Cursor

Click Add to Cursor on the listing (Cursor asks you to sign in to your Cursor account first if you are not already). You can also open Customize in the Cursor sidebar, find Nitrosend and choose Install, then pick project or user scope.

The plugin bundles one remote MCP server, nitrosend, pointed at https://api.nitrosend.com/mcp. Nothing runs on your machine, so it works in the Cursor desktop app and Cursor on the web. Cloud agents keep their own MCP list: add the same URL as an HTTP server from the MCP dropdown at cursor.com/agents, or have a team admin share it under Dashboard, Plugins & MCPs, then sign in once (OAuth is per user).

Option 2: Add the MCP server manually

Prefer to manage MCP servers yourself? Add the same server to ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside the current repo for a project-local setup:

{
  "mcpServers": {
    "nitrosend": {
      "url": "https://api.nitrosend.com/mcp"
    }
  }
}

Restart Cursor if the server does not appear straight away.

Tip

Pick one path. The plugin and the manual entry add the same server, so keep one or the other and Cursor lists a single nitrosend server. Do not use mcp-remote or the local @nitrosend/mcp package for the standard Cursor setup.

Older Cursor builds without remote MCP support

If your Cursor build cannot connect to a remote MCP server directly, route through the stdio bridge instead. It needs Node on the machine:

{
  "mcpServers": {
    "nitrosend": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.nitrosend.com/mcp"]
    }
  }
}

Sign in

The first Nitrosend tool call opens a Nitrosend sign-in window. Log in or create a free account there. OAuth handles the rest: no API key, nothing to paste.

Verify the connection

Open Cursor's Agent chat and ask:

What's my Nitrosend account status?

Cursor calls nitro_get_status and shows your account, sender identity, readiness, blockers and recommendations. If the sign-in prompt does not appear after the first tool call, open Customize in the sidebar, confirm the nitrosend MCP server is enabled, and re-run the prompt.

Example workflows

Compose a campaign

Create a campaign called "April Newsletter" using my brand theme.
Target the active subscribers segment and schedule it for Tuesday at 10am.

Build an automation flow

Build a cart abandonment flow: email at 1 hour, 24 hours, then 72 hours
with a 10% discount code.

Check performance

Show me insights for my last 3 campaigns. How are they tracking against benchmarks?

Send a test email

Send a test of my latest campaign to user@example.com

MCP tools available

Cursor's agent gets every public Nitrosend MCP tool. The MCP reference lists every tool with its parameters.

Troubleshooting

Sign-in window didn't open

Open Customize in the Cursor sidebar and confirm the nitrosend MCP server is enabled. Trigger a Nitrosend tool call again. If Cursor still does not prompt for OAuth, remove and re-add the plugin (or the nitrosend entry in mcp.json) and restart Cursor once.

Tools not appearing in Cursor Chat

If you installed the plugin, check it is enabled for the scope you are working in (project or user) under Customize. If you edited mcp.json manually, make sure Cursor picked up the new config; a restart is sometimes required after adding a new server. Inspect protected-resource metadata with curl -i https://api.nitrosend.com/.well-known/oauth-protected-resource/mcp; it should return 200 OK and name https://api.nitrosend.com/mcp as the protected resource. Separately, unauthenticated GET /mcp should return 401 Unauthorized with WWW-Authenticate: Bearer resource_metadata="https://api.nitrosend.com/.well-known/oauth-protected-resource/mcp". Authenticated MCP application traffic uses POST /mcp; because Nitrosend does not offer a GET/SSE listener, authenticated GET /mcp returns 405 Method Not Allowed.

Two nitrosend servers listed

You have both the plugin and a manual mcp.json entry. Remove one. Either path works; the plugin is the one Cursor keeps up to date for you.

Info

No API key or local dependencies required. Authentication is handled via OAuth sign-in when you first connect. The plugin is free and MIT licensed; source at github.com/nitrosend/cursor.