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 分