
MuntuAI
io.github.design-smith由 GitHub 帳號 design-smith 發布v1.0.0更新於 Oct 24, 2026
Hosted MCP server for MuntuAI outreach campaigns, leads, senders, domains, and analytics.
概覽
供 MuntuAI 電子郵件開發信使用的託管 MCP 伺服器,讓助理管理工作區中的活動、潛在客戶、寄件者、網域與 Webhook。
- 可以做什麼
- 透過 muntu:// URI 讀取工作區、網域、寄件者、活動、草稿佇列與事件資源,支援分頁與篩選。建立、啟動、暫停、恢復、監控並寄送電子郵件活動,審閱草稿。從陣列或 CSV 連結匯入潛在客戶,並進行充實與取樣。新增、驗證與檢查網域狀態;建立、刪除、健康檢查寄件者並指派到活動。預覽、潤飾與產生活動郵件內容,並透過 Webhook 訂閱工作區事件。
- 適用情境
- 當助理需要操作 MuntuAI 電子郵件開發信工作區時使用:啟動或監控活動、匯入並充實潛在客戶、設定寄信網域,或把 Webhook 通知接入代理流程。
- 執行需求
- 遠端 MCP 端點,使用 streamable HTTP,不需本機套件。需要 MuntuAI 帳號,並在設定中建立代理金鑰,以 Authorization bearer 權杖形式送出,格式為 Bearer mnt_ . 。金鑰綁定單一工作區,並帶有自主等級(observer、copilot 或 autonomous)。需要能存取 MuntuAI API 的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 MuntuAI,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.design-smith%2Fmuntuai-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"muntuai": {
"type": "http",
"url": "https://api.muntuai.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
MuntuAI MCP
This repository contains the public documentation, manifest, and reference clients for the live MuntuAI MCP server. The runnable server implementation lives in the main Muntu backend.
The official Model Context Protocol (MCP) server for MuntuAI — giving AI agents programmatic access to email outreach campaigns, lead management, domain infrastructure, and real-time workspace events.
What This Is
MuntuAI is an AI-native email outreach platform. This MCP server lets external agents (Claude, Cursor, custom scripts) connect to a MuntuAI workspace and perform actions: create campaigns, import leads, verify domains, send emails, and subscribe to webhook events — all through a standard MCP interface over HTTP.
Protocol: Model Context Protocol over HTTP (JSON-RPC 2.0)
Transport: Streamable HTTP (text/event-stream or application/json)
Server protocol revision: 2025-03-26
Server URL: https://api.muntuai.com/api/mcp
Quick Start
1. Get an agent key
Log in to app.muntuai.com, go to Settings → Agent Keys, and create a key. Choose the autonomy level that matches what your agent needs:
You will see the raw key once: mnt_<keyId>.<secret>. Copy it immediately.
2. Configure your client
Security note: store the raw agent key in an environment variable or secret manager. Do not commit it to source control or paste it into shared files.
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
Cursor (.cursor/mcp.json or Settings → MCP):
Python:
Recommended:
Muntu uses the optional MUNTU_SESSION_ID to group requests into one logical MCP session for session-scoped safety controls and budgeting.
3. Make your first call
Once connected, ask your agent:
"List all campaigns in my MuntuAI workspace"
The agent will call resources/read on muntu://campaigns/{workspaceId} and return the campaign list.
Or via Python CLI:
What Agents Can Do
Resources (read-only views)
Tools (30 total)
Grouped by domain — see tools/README.md for the full index.
- Campaigns — create, launch, pause, resume, monitor, review drafts, send
- Leads — import from array or CSV URL, enrich, sample
- Senders — create, delete, health check, assign to campaign
- Domains — add, verify, check status
- Email generation — preview, refine, generate campaign guide
- Webhooks — subscribe to workspace events
- Meta — get agent key info
Repository Structure
Key Concepts
Workspace — All data in MuntuAI is scoped to a workspace. Your agent key is bound to one workspace and can only access data within it.
Autonomy levels — Every tool has a minimum required level. If your key's level is below the requirement, the call is rejected and the attempt is logged. See docs/autonomy-levels.md.
Campaign lifecycle — uploaded → enriching → drafting → sending → completed. Agents can observe this lifecycle through get_campaign_performance and the events resource. See workflows/monitor-campaign.md.
Domain verification — Before sending, a domain must be verified with the email provider. This involves publishing DNS records and triggering verification. See workflows/domain-setup.md.
Support
- Documentation issues: Open an issue in this repo
- Platform support: [email protected]
- Website: muntuai.com
來源:README.md,提交 b959b64
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。