Claude Desktop + Nitrosend MCP

Connect Nitrosend to Claude Desktop as a Custom Connector and manage your email marketing through natural conversation. No coding, no config files — just add the connection and start prompting.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets Claude connect directly to external services. When Nitrosend is connected as an MCP server, Claude gets native access to your email marketing — campaigns, flows, contacts, templates, analytics — all through conversation.

Setup: Add Nitrosend as a Custom Connector

Open Claude Desktop Settings

In Claude Desktop, go to Settings (gear icon) > Connections.

Add Nitrosend

Click Add Custom Connector and enter:

URL: https://api.nitrosend.com/mcp

Click Connect.

Claude will open a Nitrosend sign-in window. Log in or create a free account — no API key needed.

Start using Nitrosend

Open a new conversation and ask Claude anything about your email marketing:

What's my Nitrosend account status?

Claude will use the Nitrosend MCP tools to check your account and respond with your status, recommendations, and next steps.

Tip

No API key required. The Custom Connector handles authentication through a secure sign-in flow — just log in when prompted and you're connected.

What Claude can do with Nitrosend connected

Once connected via MCP, Claude has access to 21 specialized tools and live resources about your account. Here's what that means in practice:

Compose and send emails

You: Send a welcome email to jane@example.com

Claude: I'll compose a welcome email using your brand theme and send it. Here's a preview — want me to send a test first, or go ahead?

Build automation flows

You: Create a 3-email welcome series that triggers when someone joins my newsletter list

Claude: Done. I've created a flow with: (1) Welcome email sent immediately, (2) Product highlights after 3 days, (3) Special offer after 7 days. Want me to activate it?

Check analytics

You: How did my last campaign perform?

Claude: Your "Spring Reading List" campaign had a 42% open rate and 8.3% click rate — both above industry benchmarks. The top-clicked link was...

Manage contacts

You: Import these contacts to my VIP list: jane@example.com, bob@example.com

Claude: I've added both contacts to your VIP list with email subscription enabled.

MCP resources Claude can access

Beyond tools, Claude can read live resources for deeper context:

Resource	What it provides
`nitro://guide`	Platform vocabulary, workflows, and tool usage guidance
`nitro://schema`	Email component types, flow steps, and filter definitions
`nitro://brand`	Your brand identity — colors, fonts, tone, logo
`nitro://account`	Account status, tier, and sending limits
`nitro://config`	Sender defaults and verified domains

Tips for best results

Set up your Brand Settings first. Go to Brand Settings and configure your brand colors, fonts, and logo. Claude uses this automatically when composing emails.
Use AI Memory. Go to AI Memory to tell Nitrosend about your business goals, target audience, and email strategy. Claude reads this to make smarter decisions.
Be specific about your audience. Say "send to the newsletter list" rather than just "send an email."
Ask for previews. Say "send me a test first" before going live with any campaign.

Learn how to configure Brand Settings and AI Memory to make every email smarter.

Alternative: Manual MCP configuration

If the Custom Connector method isn't available in your version of Claude Desktop, you can configure MCP manually using an API key:

Manual config file setup

Open your config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add Nitrosend to the mcpServers section:

{
  "mcpServers": {
    "nitro": {
      "command": "npx",
      "args": ["-y", "@nitrosend/mcp"],
      "env": {
        "NITROSEND_API_KEY": "nskey_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. You should see a hammer icon indicating MCP tools are available.

Info

Requires Node.js 18 or later for the manual config method. The Custom Connector method has no local dependencies.