# Claude Desktop

# Claude Desktop + Nitrosend MCP {#claude-desktop--nitrosend-mcp}


Nitrosend is an official connector in the Claude directory. Enable it once under **Settings → Connectors**, sign in, and Claude can run your email marketing through natural conversation. No coding, no config files, no URL to paste.



> [!IMPORTANT]
> Claude Desktop, Claude.ai and Claude Cowork users should enable the Nitrosend connector. Do not install `@nitrosend/cli` or run `nitrosend login` for the standard Claude setup; the CLI is for terminal and CI workflows, not connector onboarding.




## What is MCP? {#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: Enable the Nitrosend connector {#setup-enable-the-nitrosend-connector}




1. **Open Connectors**

   In the Claude Desktop app, go to **Settings** → **Connectors**.

2. **Find Nitrosend and connect**

   Search for **Nitrosend** and click **Connect**. The same listing is at [claude.ai/directory/nitrosend](https://claude.ai/directory/nitrosend): open that link in Claude.ai (web) to add the connector there, and it is available in Claude Desktop, Cowork and the Claude mobile apps as well.

3. **Sign in**

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

4. **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 and no server URL required. The connector handles authentication through a secure sign-in flow: log in when prompted and you're connected.




## What Claude can do with Nitrosend connected {#what-claude-can-do-with-nitrosend-connected}


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


### Draft and test campaigns {#draft-and-test-campaigns}


> **You**: Draft a welcome campaign for my Newsletter list
>
> **Claude**: I'll compose a welcome campaign using your brand theme. Here's a preview — want me to send a test before approval?


### Build automation flows {#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 {#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 {#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 {#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-kit` | Your Brand Kit identity — colors, fonts, tone, logo |
| `nitro://account` | Account status, tier, and sending limits |
| `nitro://config` | Sender defaults and verified domains |


## Tips for best results {#tips-for-best-results}


- **Set up your Brand Kit first.** Go to Brand Kit ([app.nitrosend.com/my/brand](https://app.nitrosend.com/my/brand)) and configure your brand colors, fonts, and logo. Claude uses this automatically when composing emails.
- **Use AI Memory.** Go to AI Memory ([app.nitrosend.com/my/settings/memory](https://app.nitrosend.com/my/settings/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.







**[Brand Kit & AI Memory](https://docs.nitrosend.com/integrations/mcp-brand-kit-memory.md)**

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






## Fallback: custom connector {#fallback-custom-connector}


If your Claude organisation restricts directory connectors, ask an organisation owner to enable Nitrosend, or to add it as a custom connector: **Settings** → **Connectors** → **Add custom connector**, name `Nitrosend`, remote MCP URL `https://api.nitrosend.com/mcp`. Same tools, same sign-in flow.


## Legacy fallback: Manual MCP configuration {#legacy-fallback-manual-mcp-configuration}


If neither the directory listing nor custom connectors are available in your version of Claude Desktop, update Claude Desktop first. Only use this local stdio fallback when you cannot use connectors at all and you understand that it stores an API key in your local Claude config:





**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:

```json
{
  "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.





> [!IMPORTANT]
> Requires Node.js 18 or later for the manual config method. The directory connector has no local dependencies and remains the recommended path.
