MCP Hub
Back to servers

Nitrosend

AI-native email marketing platform built for agents. Control campaigns, automations, contacts, templates, and analytics via MCP with OAuth authentication.

glama
Stars
1
Updated
Apr 2, 2026
Validated
Apr 21, 2026

@nitrosend/mcp

MCP server for Nitrosend — connect any AI agent to your email marketing platform.

Manage contacts, compose emails, build automated flows, and launch campaigns through natural language.


Setup by client

Most clients support OAuth — sign in via your browser, no API keys needed.

Claude Code

claude mcp add --transport http nitrosend https://api.nitrosend.com/mcp

Or add to .mcp.json:

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

OAuth sign-in happens automatically on first use.


Claude Desktop

Go to Settings → MCP Servers → Add and select Streamable HTTP transport:

https://api.nitrosend.com/mcp

Claude.ai (web + mobile)

Go to Settings → Connectors → Add custom connector and enter:

https://api.nitrosend.com/mcp

Cursor

Add to .cursor/mcp.json:

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

Cursor opens your browser to sign in on first use via mcp-remote.


VS Code (Copilot)

Add to .vscode/mcp.json:

{
  "servers": {
    "nitrosend": {
      "type": "http",
      "url": "https://api.nitrosend.com/mcp"
    }
  }
}

VS Code handles OAuth automatically via its built-in MCP auth flow.


Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

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

Windsurf supports OAuth natively for HTTP servers — sign in via your browser on first use.


Codex CLI

codex mcp add nitrosend --url https://api.nitrosend.com/mcp
codex mcp login nitrosend

Or add to ~/.codex/config.toml:

[mcp_servers.nitrosend]
url = "https://api.nitrosend.com/mcp"

Then run codex mcp login nitrosend to authenticate via OAuth.


Zed

Zed only supports stdio transport — use mcp-remote to bridge:

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

Any other MCP client

If your client supports HTTP/SSE transport, point it at:

https://api.nitrosend.com/mcp

If your client only supports stdio, use the bridge with an API key:

{
  "command": "npx",
  "args": ["-y", "@nitrosend/mcp"],
  "env": {
    "NITROSEND_API_KEY": "nskey_live_..."
  }
}

Get your API key at Settings → API Keys in the Nitrosend dashboard.


What you can do

Once connected, your agent can:

  • Read — query contacts, segments, flows, campaigns, and account status
  • Compose — create emails with sections, build multi-step flows, set up campaigns
  • Manage — import contacts, create segments, manage lists and tags
  • Deliver — preview emails, run spam checks, send tests, approve and schedule campaigns
  • Insights — view open/click/unsubscribe metrics and trends

Environment variables

VariableDescription
NITROSEND_API_KEYAPI key (nskey_live_...) — for stdio transport
NITROSEND_BEARER_TOKENOAuth bearer token — alternative to API key
NITROSEND_API_URLOverride API endpoint (default: https://api.nitrosend.com/mcp)

Requirements

  • Node.js 18+

License

MIT

Reviews

No reviews yet

Sign in to write a review