MuntuAI MCP Server

Hosted MCP server for MuntuAI outreach campaigns, leads, senders, domains, and analytics.

Local serverstdioPython

What is the MuntuAI MCP server?

Hosted MCP server for MuntuAI outreach campaigns, leads, senders, domains, and analytics. Exposed over MCP by the muntuai mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

Its toolset

Everything the assistant can do here goes through one of these:

  • 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
  • Webhooks — subscribe to workspace events
  • Meta — get agent key info

Adding it to your client

requests on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 2 environment variables: MUNTU_AGENT_KEY, MUNTU_SESSION_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MuntuAI's toolset — Campaigns, Leads, Senders and 3 more — is a fair guide to whether it matches your workflow. It is maintained by design-smith; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the muntuai mcp server does with a few real requests.

Available tools

ToolWhat it does
Campaignscreate, launch, pause, resume, monitor, review drafts, send
Leadsimport from array or CSV URL, enrich, sample
Senderscreate, delete, health check, assign to campaign
Domainsadd, verify, check status
Webhookssubscribe to workspace events
Metaget agent key info

How to install the MuntuAI MCP server

{
  "mcpServers": {
    "muntu": {
      "url": "https://api.muntuai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MUNTU_AGENT_KEY}"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MUNTU_AGENT_KEYCredential the server authenticates with.Yes
MUNTU_SESSION_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use MuntuAI to Campaigns.
  • Use MuntuAI to Leads.
  • Use MuntuAI to Senders.

Frequently asked questions

It connects MuntuAI to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Campaigns, Leads, Senders, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MuntuAI directly.