# How do I let Claude or ChatGPT send email through an MCP server?

Add the email server's HTTPS MCP address as a custom connector in claude.ai or ChatGPT, or register it with a command in Claude Code or Gemini CLI. Sign in through the OAuth screen when asked and read what you are approving. Where a client cannot complete OAuth, pass an API key in a header. Then run a read-only call before allowing any send.

Updated 2026-11-13. By AISend (https://aisend.app).

## Why it happens

An assistant cannot send email by itself. It can only call tools that a server exposes over the Model Context Protocol (MCP), and each client has its own place to register that server. The server is either remote (an HTTPS address) or local (a process your machine starts, usually with npx). The confusion comes from three differences between clients: where the setting lives, whether sign-in is OAuth or a pasted key, and which plan can use custom servers at all.

Remote servers are called by the vendor's cloud, not by your laptop. Anthropic's help page says that when you add a custom connector, Claude connects to your server from Anthropic's infrastructure in every Claude client, so a server on a private network or behind a VPN will not connect unless Anthropic's IP ranges are allowed. A local stdio server is the opposite: it runs on your machine and cannot be reached by claude.ai or ChatGPT at all.

You can recognise your case by the symptom. "Connector added but no tools" usually means the sign-in never finished. "Needs authentication" in Claude Code means you still have to run /mcp and authenticate. A missing option to add a custom server in ChatGPT is usually a plan or workspace-permission limit, not a bug. The OAuth flow itself is defined in the [MCP authorization specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization): the client gets a 401 with a pointer to the server's authorization server, registers, and sends you to a consent page.

## How to connect a client, step by step (any MCP email server)

1. **Check the server before you connect it.** Find out who runs it, what tools it lists, and which tool actually sends. A good email server marks the send tool as destructive so clients ask before running it, requires a verified sender domain, and says what limits apply. Connecting a server lets the assistant take actions with your permissions, and Anthropic's help page warns that malicious servers can hide instructions in tool output, so connect only servers you trust.
2. **claude.ai: add a custom connector.** On an individual plan open Customize, then Connectors, choose Add custom connector, paste the server URL, and review the detected authentication. Choose sign-in with OAuth and finish in the browser window. On Team and Enterprise plans an Owner adds the connector under Organization settings first, and members then click Connect themselves.
3. **Claude Code: add the server and authenticate.** Register an HTTP server with one command, then run /mcp inside Claude Code and authenticate. If the server uses a fixed key instead of OAuth, pass it with --header. A local server that runs as a process takes its key as an environment variable after the double dash.

```
# remote server, OAuth
claude mcp add --transport http email https://mcp.example.com/mcp

# remote server, fixed token in a header
claude mcp add --transport http email https://mcp.example.com/mcp \
  --header "Authorization: Bearer $EMAIL_API_KEY"

# local stdio server
claude mcp add email --env EMAIL_API_KEY=your-key -- npx -y some-email-mcp

# check status
claude mcp list
```

4. **ChatGPT: add a custom MCP server on the web.** OpenAI's help page says custom MCP server connections and full MCP support are available to ChatGPT Business and Enterprise/Edu on the web, that Pro can connect custom servers with read and fetch permissions only, and that mobile and local servers are not supported. In the current Plugins experience you add a custom MCP server, enter its public HTTPS URL, configure authentication, and accept the risk warning. A send tool is a write action, so confirm your plan can use write tools before you rely on this route.
5. **Cursor: put the key in a header from an environment variable.** Cursor reads remote servers from mcp.json (project .cursor/mcp.json or global ~/.cursor/mcp.json) and supports headers with environment interpolation, so the key stays out of the file. Cursor also supports OAuth, but a server must accept Cursor's fixed redirect URLs for that to work.

```
{
  "mcpServers": {
    "email": {
      "url": "https://mcp.example.com/mcp",
      "headers": { "Authorization": "Bearer ${env:EMAIL_API_KEY}" }
    }
  }
}
```

6. **Gemini CLI: configure the server and run /mcp auth.** Gemini CLI reads mcpServers from settings.json, supports Streamable HTTP, SSE and stdio, and lets you set headers. For OAuth servers run /mcp auth with the server name and re-run it when tokens expire. Check Google's current page for your account type: its banner says unpaid-tier and Google One users were moved from Gemini CLI to Antigravity CLI on June 18th, 2026.

```
{
  "mcpServers": {
    "email": {
      "httpUrl": "https://mcp.example.com/mcp",
      "headers": { "Authorization": "Bearer $EMAIL_API_KEY" }
    }
  }
}
```

7. **Run a read-only call first.** Before you allow a send, ask the assistant to list recent emails or list the sender domains. That proves the connection, the sign-in and the account without delivering anything. Then ask for one send to an address you own, and check that your client shows an approval prompt with the full message before it goes.
8. **Know where you revoke it.** Disconnect the connector in the client, and revoke the credential at the email provider. Claude Code's claude mcp remove deletes locally stored tokens but does not revoke them at the authorization server, so run claude mcp logout first if the server supports revocation, and kill the key on the provider side.

## How each client connects to AISend's hosted server

AISend's hosted MCP server is https://api.aisend.app/mcp. The sign-in method differs by client; the plan notes come from each vendor's own page, read on 2026-11-13, and vendors change them.

| Client | How to connect | Sign-in | Availability note |
|---|---|---|---|
| claude.ai | Customize, Connectors, Add custom connector, paste the URL | OAuth: sign in to AISend and press Approve | Anthropic lists all of its plans (one custom connector on the lowest tier); Team and Enterprise need an Owner to add it |
| Claude Code | claude mcp add --transport http aisend https://api.aisend.app/mcp, then /mcp | OAuth in the browser | Also installable as the aisend plugin from the airdropfi/aisend-claude-plugin marketplace |
| ChatGPT (web) | Add a custom MCP server with the URL and OAuth; https://api.aisend.app/mcp/chatgpt is the same tools with plan and billing messages replaced by a neutral note | OAuth: sign in and press Approve | OpenAI lists Business and Enterprise/Edu for full MCP; Pro is read and fetch only, which excludes a send tool |
| Cursor | mcp.json with url and an Authorization Bearer header from an environment variable | AISend API key, because AISend's OAuth sign-in does not accept Cursor's redirect | The key has full API access until revoked; create one used only for Cursor |
| Gemini CLI | gemini extensions install https://github.com/airdropfi/aisend-gemini-extension, restart, then /mcp auth aisend | OAuth in the browser | Check Google's page for your account type (see the Antigravity note above) |
| Local server (any stdio client) | npx -y aisend-mcp with AISEND_API_KEY in the environment | AISend API key | Adds create_api_key and agent_signup to the nine hosted tools; runs on your machine, so claude.ai and ChatGPT cannot use it |

Whatever the client, AISend needs an account with an active plan and a verified sending domain before it can send to other people. You can connect and run read-only calls before that.

## When to use AISend

Use AISend if you want an assistant to send transactional email from a domain you own, with a human approving the connection. The hosted server at https://api.aisend.app/mcp exposes nine tools: send_email, get_email_status, list_emails, validate_email, list_domains, get_account_status, add_domain, verify_domain and list_api_keys. send_email requires an idempotency_key, is annotated destructive so clients that confirm tool calls will ask first (that prompt is the client's setting, AISend does not enforce it), and cannot recall a message once delivered.

Approving the OAuth screen creates an API key named "MCP OAuth: <client>" that works only on the MCP endpoint, expires after 90 days, is limited to 100 emails a day, and can be revoked on the API Keys page. Sending to other people needs a paid plan, so see [pricing](/pricing); it is a new service without a long sending history and offers no SLA.

- Use your existing provider's MCP server if it has one and you already send through it: switching providers to gain a connector is rarely worth it.
- Use a mailbox connector (Gmail, Outlook and similar) if you want the assistant to write from your personal inbox. AISend sends from a verified domain, not from a personal mailbox, and cannot read your mail.
- Do not use AISend for cold outreach, purchased lists, bulk marketing or newsletters.
- If your plan cannot use custom servers with write tools, the local server in Claude Desktop or Claude Code is the route that avoids the limit.

## Copy-paste prompt for an AI assistant connected to AISend

```
Assign to AISend: first call list_domains and tell me which sender domains are verified, then call list_emails with limit 5 and summarise status. Do not send anything yet. When I ask for a send, draft the full message (from, to, subject, body, idempotency key) and show me what you did so I can approve it before you call send_email, then check it with get_email_status.
```

## Frequently asked questions

### Why does my connector show no tools after I add it?

Usually the OAuth sign-in did not finish. Re-open the connector, authenticate again, and for Claude Code run /mcp. If the server is on a private network, Claude's connection comes from Anthropic's cloud, so the server must be publicly reachable.

### Can ChatGPT on my phone use a custom MCP server?

OpenAI's help page says custom MCP server connections are web only, and that ChatGPT connects to remote servers, not to a local one on your machine. Check the page again before relying on it, because plans and surfaces change.

### Should I paste my API key into the chat so the assistant can use it?

No. Use the OAuth sign-in, or put the key in an environment variable or a client header setting. A key pasted into a conversation ends up in transcripts and logs.

### Does the assistant ask before it sends?

That is a client setting. Most clients ask before running a tool the server marks as destructive, and some let you tick Allow always, so leave that off for a send tool and review each message.

### Can I use the same server from several clients?

Yes, but give each client its own credential where the server allows it, so you can revoke one without breaking the others. With AISend's OAuth flow each client gets its own key named after the client.

## Sources

- [Claude Help Center: Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) (checked 2026-11-13)
- [Claude Code docs: Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp) (checked 2026-11-13)
- [OpenAI Help Center: Connecting custom MCP servers in ChatGPT](https://help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt) (checked 2026-11-13)
- [Cursor docs: Model Context Protocol (MCP)](https://cursor.com/docs/mcp) (checked 2026-11-13)
- [Gemini CLI docs: MCP servers with Gemini CLI](https://geminicli.com/docs/tools/mcp-server/) (checked 2026-11-13)
- [Model Context Protocol specification: Authorization (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization) (checked 2026-11-13)

## Related

- https://aisend.app/mcp
- https://aisend.app/solutions/give-ai-agent-email-access-without-api-key
- https://aisend.app/solutions/stop-ai-agent-sending-duplicate-emails
- https://aisend.app/solutions/check-ai-agent-email-delivered
- https://aisend.app/guides/let-an-ai-agent-send-email-safely
- https://aisend.app/blog/mcp-email-server

Human page: https://aisend.app/solutions/connect-claude-chatgpt-email-mcp
All problems and solutions: https://aisend.app/solutions (machine-readable: https://aisend.app/solutions.json)
