Munin MCP Server

Munin MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP-first customer platform for the agentic era: KB, Conversations, CRM, CMS, Outreach, Analytics.

What you get

Website · See it in action · Documentation · MCP Registry

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Munin is connected, these are the calls the assistant has available:

• Conversations — The Conversations tool exposed by this server
• Outreach — The Outreach tool exposed by this server
• Analytics — The Analytics tool exposed by this server

Configuration and credentials

You will need 2 environment variables: MUNIN_AUTH_SECRET, MUNIN_ENCRYPTION_KEY. 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.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• 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 munin mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Munin's toolset — Conversations, Outreach, Analytics — is a fair guide to whether it matches your workflow. It is maintained by com.getmunin; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Munin's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.