AhaSend Email API & SMTP relay MCP ServerVerifiedFeatured

What is AhaSend?

AhaSend is a European email API and SMTP relay for transactional and marketing email, ISO 27001 certified and running on its own servers in the EU. The AhaSend MCP server lets an AI agent work with an AhaSend account in plain language: send email, find out why a message failed, set up sending domains, build templates, manage contacts and lists, and create and send campaigns. Every tool calls the AhaSend v2 API, and the API key's scopes decide what the agent may do.

How to use AhaSend?

1. Register an AhaSend account: https://dash.ahasend.com/user/register (free plan, 1,000 emails a month).
2. Add the remote server to your AI tool with one URL, no API key to copy:

https://mcp.ahasend.com/mcp

To self-host or embed the tools in your own Go program: go get github.com/AhaSend/ahasend-mcp and serve over stdio or HTTP with the official Go MCP SDK. See the repository README.

Key features of AhaSend

• Send transactional email, template email and conversation replies; cancel scheduled sends.
• Diagnose deliveries: list and inspect messages, explain why one failed, read deliverability, bounce and delivery-time statistics.
• Manage sending domains and check their DNS.
• Create and version transactional and campaign templates in either editor: Simple Editor designs as AhaML markup, Advanced Editor designs as MJML.
• Manage contacts, lists and segments; create, test, schedule and send campaigns.
• Manage webhooks, inbound routes, suppressions, SMTP credentials and sub-accounts.
• Safety by design: campaign sends require a human confirmation, one-off sends are capped per call, received email is hidden from the agent unless enabled and marked untrusted.
• Scoped access: only the tools the API key allows are shown; a read-only mode exists.

Use cases of AhaSend

• Let an agent send password resets, order confirmations and notifications from your own domain.
• Ask "why didn't this email arrive?" and get the delivery log and bounce reason in plain words.
• Onboard a new sending domain: add it, check DNS, confirm it is ready.
• Draft a newsletter, build the template, send a test and schedule the campaign, with a person approving the send.
• Keep your CRM or app in sync with contact lists, unsubscribes and suppressions.
• Platforms: provision isolated sub-accounts for your own customers.