# Claude Code

# Claude Code + Nitrosend MCP {#claude-code--nitrosend-mcp}


[Claude Code](https://docs.anthropic.com/en/docs/claude-code) is Anthropic's CLI tool for working with Claude in your terminal. Connect Nitrosend via MCP and Claude Code becomes a full email marketing command center.


## What is MCP? {#what-is-mcp}


**MCP (Model Context Protocol)** is an open standard that lets AI tools connect to external services. When you add Nitrosend as an MCP server to Claude Code, Claude gets native access to the full public set of email marketing tools — no API wrappers, no middleware, no boilerplate.


## Setup {#setup}



### Step 1: Install the Nitrosend plugin {#step-1-install-the-nitrosend-plugin}


Run these in your terminal:

```bash
claude plugin marketplace add nitrosend/claude
claude plugin install nitrosend@nitrosend
```

The plugin brings the Nitrosend MCP server and Nitrosend's email skills (setup, composing, campaigns, flows, transactional email, imports and analytics). Inside a Claude Code session, the same thing is `/plugin marketplace add nitrosend/claude`, then `/plugin install nitrosend@nitrosend`.

Prefer the server on its own, without the skills? One command does it:

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

Use one or the other, not both.


### Step 2: Sign in {#step-2-sign-in}


Start Claude Code and run `/mcp`, or ask Claude to use Nitrosend. Claude Code opens the Nitrosend sign-in or shows you the login URL. Log in or create a free account. No API key needed.


### Step 3: Verify the connection {#step-3-verify-the-connection}


Ask Claude:

```
What's my Nitrosend account status?
```

Claude calls `nitro_get_status` and shows your current account, sender identity, readiness, blockers and recommendations.


## How MCP works {#how-mcp-works}


Claude Code connects directly to the Nitrosend MCP endpoint over HTTP:

1. Claude Code sends tool calls via MCP protocol to `api.nitrosend.com/mcp`
2. Authentication is handled via OAuth — you sign in once and Claude Code stores the token for you
3. Structured results come back to Claude with full context

No data is stored locally. All state lives in your Nitrosend account.


## MCP tools available {#mcp-tools-available}


Claude Code gets every public Nitrosend MCP tool. The [MCP reference](https://docs.nitrosend.com/mcp.md) lists every tool with its parameters.

For accounts with multiple brands, ask Claude to check `nitro_get_status` first. It lists the brands allowed by your [connection access](https://docs.nitrosend.com/integrations/overview.md#choose-connection-access). Use `nitro_select_brand` to switch between those brands. API keys stay with their key's brand, and `nitro_set_brand_kit` edits Brand Kit identity.


## MCP resources {#mcp-resources}


Claude can also read live resources for deeper context:

| Resource | What it provides |
|----------|-----------------|
| `nitro://guide` | Platform vocabulary, workflows, and tool descriptions |
| `nitro://schema` | Email component types, flow step types, filter definitions |
| `nitro://brand-kit` | Your Brand Kit identity — colors, fonts, tone, logo |
| `nitro://account` | Current account context, sender identity, dashboard links, tier, and limits |
| `nitro://config` | Sender defaults and verified domains |


## Example workflows {#example-workflows}



### Create a welcome flow {#create-a-welcome-flow}


```
Create a welcome email flow. When a new contact is added, send a welcome 
email immediately, wait 3 days, then send a follow-up with our top 
recommendations.
```


### Send a campaign {#send-a-campaign}


```
Create a campaign called "March Newsletter" and send it to my subscriber list. 
Use my brand colors and include a section about our new features.
```


### Check performance {#check-performance}


```
Show me insights for my last campaign. How did it compare to benchmarks?
```


### Set up Brand Kit and memory {#set-up-brand-kit-and-memory}


```
Set up my Brand Kit from https://mysite.com and then update my AI memory with 
our Q1 marketing goals.
```


## Scope-based configuration {#scope-based-configuration}


If you added the bare server with `claude mcp add`, you can choose its scope:

```bash
# User scope — available in all Claude Code sessions (recommended)
claude mcp add --transport http -s user nitrosend https://api.nitrosend.com/mcp

# Local scope — private to your current project on this machine
claude mcp add --transport http -s local nitrosend https://api.nitrosend.com/mcp

# Project scope — shared with the project via .mcp.json
claude mcp add --transport http -s project nitrosend https://api.nitrosend.com/mcp
```


## Troubleshooting {#troubleshooting}








**Connection failed**

Make sure `api.nitrosend.com` is reachable from your network. 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`.






**Authentication failed**

Run `/mcp` inside Claude Code to trigger the OAuth flow explicitly. If that still fails, reinstall: `claude plugin uninstall nitrosend@nitrosend` then install it again, or for the bare server `claude mcp remove nitrosend` then re-run the add command.






**Tool call timed out**

If calls consistently time out, check your network connection. You can also try removing and re-adding the MCP server to refresh the session.







> [!IMPORTANT]
> No API key or local dependencies required. Authentication is handled via OAuth sign-in when you first connect.
