MuntuAI MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MuntuAI MCPList all campaigns in my MuntuAI workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: sendcraft-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:
Level | What it can do |
| Read anything — campaigns, leads, domains, senders, events |
| Read + create and modify — campaigns, domains, senders, leads, webhooks |
| Everything above + pause, resume, delete |
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):
{
"mcpServers": {
"muntu": {
"url": "https://api.muntuai.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:MUNTU_AGENT_KEY}"
}
}
}
}Cursor (.cursor/mcp.json or Settings → MCP):
{
"mcpServers": {
"muntu": {
"url": "https://api.muntuai.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:MUNTU_AGENT_KEY}"
}
}
}
}Python:
pip install requests
export MUNTU_AGENT_KEY="mnt_YOUR_KEY_HERE"
python clients/python/muntu_mcp_client.py list-campaignsRecommended:
export MUNTU_SESSION_ID="$(uuidgen)"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:
python clients/python/muntu_mcp_client.py list-campaigns
python clients/python/muntu_mcp_client.py list-domains
python clients/python/muntu_mcp_client.py list-emailsWhat Agents Can Do
Resources (read-only views)
Resource | URI | Description |
workspace |
| Profile, policy, infrastructure counts |
domains |
| All domains with DNS and verification state |
senders |
| All email accounts with status |
campaigns |
| Unified campaign list |
campaign-plans |
| Draft review queue |
events |
| Recent system events (filterable) |
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
muntuai-mcp/
├── README.md # This file
├── QUICKSTART.md # 5-minute setup guide
├── docs/
│ ├── authentication.md # Token format, headers, rate limits
│ ├── autonomy-levels.md # Permission model
│ ├── resources.md # All 6 resources with schemas
│ ├── events.md # All event types and payloads
│ ├── webhooks.md # Register, sign, verify
│ └── errors.md # Error codes and handling
├── tools/
│ ├── README.md # Full tool index
│ ├── campaigns.md
│ ├── leads.md
│ ├── senders.md
│ ├── domains.md
│ ├── email-generation.md
│ └── meta.md
├── workflows/
│ ├── README.md # What workflows are
│ ├── launch-first-campaign.md
│ ├── review-and-send-drafts.md
│ ├── domain-setup.md
│ └── monitor-campaign.md
├── reference/
│ ├── event-types.md
│ ├── resource-schemas.md
│ └── tool-schemas.md
├── clients/
│ └── python/
│ ├── muntu_mcp_client.py # Reference Python client
│ ├── README.md
│ └── examples/
├── agent-guides/
│ ├── for-claude.md
│ ├── for-cursor.md
│ └── decision-guide.md
└── .well-known/
└── mcp-manifest.json # Machine-readable capabilities manifestKey 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: support@muntuai.com
Website: muntuai.com
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Email for AI agents: send, read replies as threads, run campaigns, with per-key limits.
Email for AI agents — send, receive as a webhook, manage domains, templates, routing.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email for AI agents: send mail, manage contacts, automations & webhooks. Zero-DNS first send.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceProvides AI agents with a free, functional email address via the Model Context Protocol without requiring manual registration. It enables comprehensive email capabilities including sending, receiving, and managing messages, contacts, and automated settings.129660MIT
sendcraft-mcpofficial
AlicenseAqualityDmaintenanceEnables AI agents to send emails, manage campaigns, subscribers, templates, and domains via the SendCraft email API.2617MIT
@sendbyte/mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.1114MIT
Tratto MCP Serverofficial
FlicenseAqualityDmaintenanceLets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.2-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/design-smith/MuntuAI-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server