--- title: "AhaSend now has an MCP server" description: "A customer says the invoice never arrived. Normally someone searches the message log and translates an SMTP error into plain language. With the AhaSend MCP server, you ask your AI tool: \"Why didn't yesterday's invoice to Bakkerij de Vries arrive?\" It finds the message in your account and explains what happened." url: https://ahasend.com/blog/ahasend-now-has-mcp-server markdown_url: https://ahasend.com/blog/ahasend-now-has-mcp-server.md lang: en type: blog_post published: 2026-10-19 updated: 2026-10-19 author: "Mark Kraakman" category: "Product Update" image: https://cms.ahasend.com/sites/default/files/2026-10/mcp-server.png --- # AhaSend now has an MCP server _By Mark Kraakman, October 19, 2026, in Product Update_ ![AhaSend now has an MCP server](https://cms.ahasend.com/sites/default/files/2026-10/mcp-server.png) A customer says the invoice never arrived. Normally someone searches the message log and translates an SMTP error into plain language. With the AhaSend MCP server, you ask your AI tool: "Why didn't yesterday's invoice to Bakkerij de Vries arrive?" It finds the message in your account and explains what happened. Video file [Video](https://cms.ahasend.com/sites/default/files/2026-10/mcp-blog-animation.mp4) The MCP server connects AI tools such as Claude, ChatGPT, Cursor, VS Code, Codex and Mistral Vibe to your AhaSend account. You add one address to your tool, log in through your browser and choose what the agent may do. You never create or copy an API key: AhaSend makes one for the connection, and you'll see it on your API Keys page. ## What you can ask Ask in plain language. The agent works in the account you connected, within the permissions you gave it: - "How did our deliveries to Microsoft look last week?" - "Add shop.example.com and tell me which DNS records to create. Check them again when I'm done." - "Set up a webhook that sends our bounces to https://example.com/hooks/ahasend." - "Build a password reset template in the style of our order confirmation." - "Make a list of everyone who signed up to our App this year and draft a newsletter about our new opening hours." The statistics questions are where it gets interesting, because the agent does the arithmetic you would otherwise do in a spreadsheet. I asked "How fast were we delivering last week?" and the answer came down to this: 1,390 transactional emails delivered, 9 seconds on average from acceptance to delivery, Gmail in 1.4 seconds. ## A newsletter from start to send, in one conversation [Campaign Builder](https://ahasend.com/blog/campaign-builder-live-newsletters-and-campaigns-every-ahasend-plan/) is where the MCP server saves the most clicks, because a campaign is a chain of small jobs that an agent on the Marketer preset can do for you. Say you run a WordPress site and want a monthly update for your readers: 1. **The list.** "Here is the subscriber export from our WordPress site. Make a list called Monthly update, add everyone with a confirmed address, and map their first name and the date they signed up to custom fields." The agent reads the export, creates the list and the fields, and adds the contacts. 2. **The template.** "Import this MJML file as a campaign template called Monthly update, and set the logo to our October logo." 3. **The content.** "Take the three posts we published on our blog this month, write a short intro for each, link to the full article, and put them in a new campaign called October update from that template." 4. **The checks.** "Send me a test." 5. **The send.** "Schedule it for Thursday 10:00." Here the agent stops and your AI tool shows you the send time, the number of contacts, the campaign name, the subject, the sender and the list(s) and asks you to confirm. Nothing goes out until you say yes. Afterwards, "How did October update do compared to September?" gives you delivered, opens, clicks, unsubscribes and bounces side by side, and "Who bounced, and why?" lists the recipients. The agent creates the contacts, templates and campaigns through the same API as the dashboard, so everything it makes is there for you to open, edit or delete by hand. ## Connect your AI tool Connecting takes about two minutes: 1. Log in at [dash.ahasend.com](https://dash.ahasend.com) and open **API Keys**. 2. Click **Connect an AI tool**. The panel shows the server URL, `https://mcp.ahasend.com/mcp`, and a tab per tool: Claude Code, Codex, Cursor, VS Code, Claude.ai, ChatGPT and Mistral Vibe. Pick yours and follow the steps on the tab. ![Connect an AI tool](https://cms.ahasend.com/sites/default/files/styles/cke_media_resize_large/public/2026-10/connect.png?itok=a23e55HC) 3. Authorize the connection. The authorization page asks which account the tool may work on and what it may do. Pick a preset at the top, Read-only, Developer, Marketer or Full, or set Read or Write per area. Under **Advanced options** you can limit the connection to some of your domains or to sandbox sending. Click **Authorize** and you are back in your tool. ![Authorize](https://cms.ahasend.com/sites/default/files/styles/cke_media_resize_large/public/2026-10/authorize.jpg?itok=HGYiHeLw) The connection shows up on the API Keys page as a key whose name starts with "MCP:". ## Guardrails we built in An agent that can send email needs limits that don't depend on the agent behaving well. These are built into the server: - **AhaSend enforces the permissions, not the agent.** Every action goes through the API with the connection's key, so the agent can do only what you allowed, and it only sees the tools those permissions allow. On the read-only connection I used for this post, Claude got 33 tools, all of them reads; the tools that send, change or delete were not there to be called. - **Some things stay in the dashboard.** Whatever you choose, the agent cannot create API keys or SMTP credentials, change account settings, billing or team members, remove all suppressions at once, or delete or suspend sub-accounts. - **A campaign only goes out after you say yes.** Before the agent sends or schedules a campaign, your AI tool shows you the send time, the number of contacts, the campaign name, the subject, the sender and the lists, and asks you to confirm. If your tool can't show that question, nothing is sent: the agent gives you a link to the campaign in the dashboard and you send it yourself. - **One email, at most 50 recipients.** The agent can't send a single email to more people than that. For a bigger audience, use a campaign, with the confirmation and checks that come with it. What we can't control: your AI tool may give the agent other tools, such as web access, and AhaSend has no say over those. Contact fields and bounce messages contain text written by other people, and an agent can mistake such text for instructions. Give a connection only the permissions its job needs. ## Who it's for Developers can set up a sending domain, wire up a webhook or debug a bounce. Marketers can build a list and draft a campaign in a conversation. And support can answer "did my email arrive?" on a read-only connection. [Start for free on AhaSend →](https://dash.ahasend.com/user/register)