
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 分
请在仓库或注册中心条目中声明许可证。