Free trial The cheapest email marketing platform: try Moosend free for 30 days, no credit card. Don't miss your seat. The cheapest email marketing platform Start free trial →
News AI & MCP

SMTP2GO Launches an MCP Server So Claude, ChatGPT and Cursor Can Send and Trace Email

SMTP2GO's new remote MCP server connects any SMTP2GO account to Claude, ChatGPT, Cursor and four other AI clients, with an API key as the only credential and a strong warning to scope its permissions.

Alaa Touil
Email infrastructure specialist, 8+ years in SMTP and deliverability
Event Nov 21, 2026 6 min read Nov 21, 2026 0 views
Independent email news, no paywall.Add as preferred sourceBuy us a coffeeRSS
SMTP2GO Launches an MCP Server So Claude, ChatGPT and Cursor Can Send and Trace Email (SMTPedia News)

Transactional email provider SMTP2GO has launched a remote MCP server that connects an SMTP2GO account to AI tools such as Claude, ChatGPT and Cursor. In a blog post published on 21 November 2026, co-founder Simon Slade says the server lets users send a test email, find out what happened to a message or check how the SMTP2GO API works, all from a chat or a code editor.

The server is open to customers on any SMTP2GO plan. It uses the account's API key as its only credential, and SMTP2GO is blunt about the risk: requests are carried out for real, and the API covers far more than sending, including account changes. The company advises a dedicated key with only the permissions the work needs.

Key facts

  • Announcement: 21 November 2026, on the SMTP2GO blog
  • Server URL: https://developers.smtp2go.com/mcp (remote, Streamable HTTP)
  • Clients documented: Claude Desktop, Claude Code, Cursor, the ChatGPT desktop app, Codex CLI, Gemini CLI and Lovable
  • Tools: list-endpoints, get-endpoint, search-endpoints, execute-request and get-server-variables
  • Authentication: an SMTP2GO API key, sent in the X-Smtp2go-Api-Key header or as a Bearer token; no OAuth
  • Availability: every SMTP2GO plan; no separate MCP price is stated
  • Billing: each recipient of a message sent through the server counts as one email on the plan, including in Sandbox mode

What SMTP2GO launched

SMTP2GO, founded in 2006 in Christchurch, New Zealand, sells SMTP relay and an email API to businesses and managed service providers. Its new MCP server exposes that API to AI clients. Four of its five tools are for discovery: they list, search and describe API endpoints, so an assistant can explain what an endpoint requires before anything is sent. The fifth, execute-request (shown as "Execute API Request" in Claude Desktop), performs real calls against the account.

SMTP2GO describes three audiences. Developers can check endpoint requirements or send test emails from their editor. IT admins and MSPs can ask whether a given message was delivered, bounced or rejected. Everyday users can write an email in a chat and send it from a verified address; in Claude Desktop and the ChatGPT desktop app the server is added through a settings form, with no terminal.

The company also draws a line around what the server is for. For an agent that only needs to send, it points to its separate send-email Skill, documented for Codex and Claude Code. For an application's own mail, it recommends SMTP, the API or an official library rather than an AI client.

Permissions decide what the assistant can do

Because the API key is the only credential, its permissions are the real control. For sending, SMTP2GO recommends a key limited to three permissions: /email/send, /allowed_senders/view and /domain/view. Other tasks need their own permission:

  • Tracing one email (delivered, bounced or rejected) needs /activity/search. Activity history covers 30 days by default on paid plans and 5 days on the free plan.
  • Checking suppression status needs /suppression/view.
  • Checking email cycle usage needs /stats/email_cycle.
  • Checking the key's own permissions works with any key and changes nothing.

A key without the right permission returns "You do not have permission to access this API endpoint"; a missing, invalid or disabled key returns 401 Unauthorized. SMTP2GO's documentation adds that discovery tools may work without authentication, while execute-request always needs the key.

Sender verification and DMARC

Mail sent through the server must come from a verified sender; any other From address is rejected. A single address can be verified by clicking a confirmation link, with no DNS change. SMTP2GO notes that this shortcut is closed when the address's domain publishes a DMARC record that restricts which servers may send its mail. In that case, the domain itself must be verified as a sender domain before real sending.

Safety advice from SMTP2GO

The announcement is unusually direct about the ways an AI client can go wrong. SMTP2GO recommends keeping the key out of project files and shared configuration, setting a sending rate limit on the key so a looping agent cannot send too fast, and disabling or deleting the key once the work is done. Its documentation warns that Claude Code's project scope writes to a .mcp.json file that is usually committed to version control, and that Gemini CLI writes to the current project by default unless the user scope is chosen.

For testing, the key can be put in Sandbox mode: messages are processed but not delivered, appear as Rejected in the Activity report, and still count towards the plan. SMTP2GO also stresses that a client reporting "sent" is not proof of delivery, and suggests a first run that ends with a test email to yourself, confirmed in Reports, Activity.

Where this fits

SMTP2GO joins a growing list of email platforms that open their accounts to AI clients. SMTPedia has recently covered MCP launches from GMass, Rule and Iterable, most of them for marketing campaigns. SMTP2GO's server is closer to an operations tool: its most useful everyday job may be answering "what happened to this email?" for a support or IT team, without opening the dashboard.

What it means for senders

What changes

SMTP2GO customers can now connect their account to Claude, ChatGPT, Cursor and four other AI clients through a remote MCP server, to send test emails, trace messages and query the API in plain language.

Who is affected

SMTP2GO customers on any plan, in particular developers, IT admins and MSPs who already use AI clients, and anyone who manages the account's API keys.

When

Available now, announced on 21 November 2026.

Action checklist

  • Create a dedicated API key for MCP, so it can be disabled without breaking other integrations.
  • Grant only the permissions you need: /email/send, /allowed_senders/view and /domain/view for sending, plus /activity/search if you want message tracing.
  • Set a sending rate limit on the key before an agent uses it.
  • Keep the key out of committed files such as a project .mcp.json; use environment variables or a secret manager.
  • Verify your sending domain if it publishes a restrictive DMARC record, instead of relying on single-address verification.
  • Test in Sandbox mode first, remembering that sandbox messages still count towards your plan.
  • Confirm delivery in Reports, Activity, not from the AI client's "sent" message.

Sources

  1. SMTP2GO blog: Send Email From Claude, Cursor or ChatGPT with the SMTP2GO MCP Server, 21 November 2026 (primary source)
  2. SMTP2GO developer documentation: MCP server (primary source)

SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.

Get SMTPedia news first on Google

Add us as a preferred source to see our stories in Top Stories and Discover.

Add as preferred source

Useful story?

SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.

Buy SMTPedia a coffee

Newsletter

Get the next rule change before it bounces your mail