Munin MCP server

Munin

Your whole customer operation, behind one MCP endpoint.

Website · See it in action · Documentation · MCP Registry

CRM, conversations, outreach, CMS, knowledge base, and analytics on one Postgres schema — exposed as MCP tools your agents drive, not screens you click through. Headless the way a headless CMS is: the dashboard owns settings, auth, and the human half of the work — an inbox where a person takes over a conversation, and a review queue where they approve what the agent proposed — but there is no admin UI to click your way through the data itself. Every action runs through MCP tools, callable from any MCP-compatible client (Claude, Cursor, ChatGPT, custom runners) — same tools, same permissions, same audit log, whether a human or an agent is driving. Munin even ships its own: an in-process, per-org agent runner that answers live conversations and works the curation queue against an LLM provider you configure — so the platform runs out of the box, with external MCP clients optional.

The console — settings, auth, the inbox, and the review queue. It drives the same MCP tools your agents call.

The review queue — outbound never sends itself. An agent drafts, files the evidence behind the draft, and waits; approving is the human's keystroke.

The embeddable chat widget — answering a live customer from the knowledge base, ready to hand off to a human and be picked back up by the agent.

Modules at a glance

These six modules aren't separate products — they share one Postgres schema, one permission model, and one audit log. Together with integrations and platform plumbing they add up to 223 MCP tools and 58 skills. Watch how they tie together:

Core modules

Shortened. The full README is on GitHub.