Labsco
design-smith logo

MuntuAI MCP

from design-smith

Allow your agents to launch personalized outbound campaigns

๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedFreeQuick setup

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


What Agents Can Do

Resources (read-only views)

ResourceURIDescription
workspacemuntu://workspace/{id}Profile, policy, infrastructure counts
domainsmuntu://domains/{id}?cursor=0&limit=50All domains with DNS and verification state
sendersmuntu://senders/{id}?cursor=0&limit=50All email accounts with status
campaignsmuntu://campaigns/{id}?cursor=0&limit=20Unified campaign list
campaign-plansmuntu://campaign-plans/{id}?cursor=0&limit=20Draft review queue
eventsmuntu://events/{id}?cursor=0Recent 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

Copy & paste โ€” that's it
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 manifest

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