AhaSend

com.ahasend由 ahasend.com 发布官方发布者v0.1.1更新于 Oct 24, 2026

Send email, check deliverability, set up domains, and run templates, contacts and campaigns.

已验证Streamable HTTP可网页运行沟通与协作商业与电商

概览

AI 生成的概览

让助手通过 AhaSend 发送邮件，并管理域名、模板、联系人、列表、营销活动、Webhook 和路由。

可以做什么
把 AhaSend 邮件平台封装为按工具集分组的 MCP 工具：发送（单次、会话和模板邮件，取消定时发送）、诊断（查询邮件、退信和送达时间统计）、域名、模板、受众（联系人和列表）、营销活动，以及管理（Webhook、路由、抑制名单、SMTP 凭据、子账户）。每个工具调用 AhaSend v2 API，API 密钥的权限范围决定显示哪些工具。营销活动发送需要用户确认表单，单次发送受收件人上限限制。
适用场景
当助手需要起草并发送事务性或营销邮件、排查邮件发送失败原因，或在对话中维护 AhaSend 的域名、模板、联系人列表和营销活动时使用。
运行要求
远程端点 mcp.ahasend.com，使用 OAuth 登录。若使用 Go 库方式，需要 AhaSend API 密钥、账户 ID、仪表盘基础地址，以及至少 32 个随机字节的确认密钥；本地开发命令读取 AHASEND_API_KEY 和 AHASEND_ACCOUNT_ID，可选 AHASEND_BASE_URL。
安装前请注意
工具可以发送邮件，创建、更新和删除域名、模板、联系人、列表、营销活动、Webhook、路由和抑制名单，并可删除 SMTP 凭据。营销活动发送需要用户明确确认，无法显示表单时不会发送。接收的邮件默认隐藏，启用 ReadInbound 后会标记为不可信，因为其中可能包含提示注入文本。确认密钥属于机密。

安装

在 SourceWeft 中

  1. 打开 控制台中的 AhaSend，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.ahasend%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "ahasend": {
      "type": "http",
      "url": "https://mcp.ahasend.com/mcp"
    }
  }
}

README

ahasend-mcp

A Go module with MCP tools for AhaSend. With these tools, an AI agent can send email, find out why an email failed, and manage domains, templates, contacts, lists, campaigns, webhooks, routes, suppressions, SMTP credentials and sub-accounts.

Each tool calls the AhaSend v2 API through ahasend-go. The API key's scopes decide what the agent can do.

The module builds a server with the official Go MCP SDK. Your program chooses how to serve it: stdio, HTTP, or any other SDK transport.

sh
go get github.com/AhaSend/ahasend-mcp

Example

go
server, err := ahasendmcp.NewServer(	&mcp.Implementation{Name: "my-app", Version: "1.0.0"},	ahasendmcp.Options{		Client:           api.NewAPIClient(api.WithAPIKey(apiKey)),		AccountID:        accountID,		DashboardBaseURL: "https://dash.ahasend.com",		ConfirmationKey:  key, // at least 32 random bytes	},)if err != nil {	return err}return server.Run(ctx, &mcp.StdioTransport{})

Options

FieldWhat it does
ClientThe ahasend-go client, with the API key. Required.
AccountIDThe account the tools work on. Required.
DashboardBaseURLThe AhaSend dashboard URL, used in campaign links. Required.
ConfirmationKeyA secret of at least 32 bytes that signs campaign send questions. Required.
ScopesThe API key's scopes. Only tools the key can use are shown. nil shows every tool.
ToolsetsShow only these toolsets. nil shows all.
ReadOnlyShow only tools that change nothing.
StatelessSet to true if you serve over stateless HTTP.
MaxRecipientsPerSendThe most recipients for one send. Default 50.
ReadInboundLet the message tools return email the account received. Off by default.
BlockedIf set, every tool call returns this text as an error and does nothing.
RecorderGets one record per tool call: tool name, success, error kind and time taken. Never the inputs or results.

If you serve many users, build a new server for each request with that user's key and scopes. This is cheap. Use the same ConfirmationKey on every instance.

Catalogue() lists every tool with the scopes it needs. OfferedScopes() lists every scope the tools use, for a page where a user picks scopes.

Tools

ToolsetTools
sendingsend_email, send_conversation_email, send_template_email, cancel_scheduled_email
diagnosticslist_messages, get_message, diagnose_message, get_deliverability_stats, get_bounce_stats, get_delivery_time_stats
domainslist_domains, get_domain, add_domain, check_domain_dns, update_domain, delete_domain
templateslist_templates, get_template, get_published_template, create_template, update_template, delete_template, discard_template_draft, publish_template, list_template_versions, get_template_version, restore_template_version, list_campaign_templates, get_campaign_template, create_campaign_template, update_campaign_template, delete_campaign_template
audiencelist_contacts, get_contact, create_contact, upsert_contacts, update_contact, delete_contact, list_contact_lists, list_lists, get_list, create_list, update_list, delete_list, list_list_contacts, add_contacts_to_list, upsert_list_contact, remove_contact_from_list, list_segments, get_segment, create_segment, update_segment, delete_segment, preview_segment, list_segment_contacts, list_contact_segments
campaignslist_campaigns, get_campaign, create_campaign, update_campaign, delete_campaign, duplicate_campaign, send_campaign_test, send_campaign, schedule_campaign, unschedule_campaign, get_campaign_stats, list_campaign_recipients
managementget_account, list_webhooks, get_webhook, create_webhook, update_webhook, delete_webhook, list_routes, get_route, create_route, update_route, delete_route, list_suppressions, add_suppression, remove_suppression, list_smtp_credentials, get_smtp_credential, delete_smtp_credential, list_sub_accounts, get_sub_account, create_sub_account, update_sub_account, get_sub_account_usage

Each tool needs the scopes its API endpoint needs. send_campaign and schedule_campaign also need campaigns:read and lists:read, and segments:read to send a campaign that uses segments. The campaign template tools also need campaigns:read. preview_segment, list_segment_contacts and list_contact_segments need contacts:read as well as segments:read.

List tools return 20 items by default and at most 100. Pass the returned cursor to get the next page.

There are no tools to create API keys or SMTP credentials, change account settings, billing or team members, remove all suppressions, or delete or suspend sub-accounts.

Simple Editor designs and AhaML

The template, campaign template and campaign tools read and write a design of the dashboard's Simple Editor as AhaSend Markup (AhaML), an XML form of the design, in the content's markup field. get_template returns a template's working copy, the draft while one exists, so an agent edits what it read; get_published_template returns the copy a send uses.

The server has one resource, ahasend://docs/ahaml: the AhaML reference, with every tag, attribute, limit and error code. It is also at https://ahasend.com/docs/send-api/ahaml. The resource is listed on every connection, so an agent without web access can read it.

Safety rules

Campaign sends need a person's yes. send_campaign and schedule_campaign show the user a form with the send time, the number of contacts, the campaign name, subject, sender, lists and segments, and the excluded lists and segments. They send only if the user answers yes. If the campaign changes after the question, the tool asks again. If the client cannot show a form, the tool sends nothing and returns a link to the campaign in the dashboard.

One-off sends have a recipient limit. A single send to more than MaxRecipientsPerSend recipients (default 50) is refused. Use a campaign for bulk email.

Received email is hidden by default. Anyone can send email to an account's inbound addresses, and that email can contain text that tries to trick the agent. Unless ReadInbound is on, the message tools do not return received email. When it is on, received messages are marked untrusted: true.

Errors

When the API refuses a call, the tool returns an error with the API's message and what to do next. When it refuses AhaML, the error lists the problems, up to the first 100, each with its code, line, column, path and hint; the API's message gives how many there are.

Trying it locally

cmd/ahasend-mcp-dev serves every tool over stdio with your own API key. It is for testing only.

sh
go build -o ahasend-mcp-dev ./cmd/ahasend-mcp-devclaude mcp add ahasend \  -e AHASEND_API_KEY=... -e AHASEND_ACCOUNT_ID=... \  -- ./ahasend-mcp-dev

Set AHASEND_BASE_URL to use an API other than the default.

License

MIT

来源：README.md，提交 e67830c

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.1.1最新Oct 14, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分