Wire Claude to Munin.
Both Claude Desktop and Claude.ai add remote MCP servers through the same Custom Connectors UI. Point either surface at your Munin org, sign in with your Munin account, and the assistant gains every tool your role allows — KB search, CRM lookups, conversation drafts, CMS writes, the lot. There is no API key to mint or paste.
Availability
Custom connectors ship on the Free, Pro, Max, Team, and Enterprise plans, on both Claude.ai (web) and the Claude Desktop apps for macOS and Windows. The Free plan allows one custom connector.
1 · Add Munin as a custom connector
On Free, Pro, and Max, open Claude Desktop or Claude.ai and go to Customize → Connectors → Add custom connector. On Team and Enterprise, an Owner adds it once for the organization under Organization settings → Connectors → Add → Custom, and each member then connects with their own Munin account. Fill in:
- Name
- Munin (or whatever you want to see in the connector list).
- Remote MCP server URL
https://mcp.dev.getmunin.com- Authentication
- OAuth. Leave the client ID and secret under Advanced settings blank — Munin supports dynamic client registration, so Claude registers itself. If your dialog asks instead, pick Sign in now and Register automatically.
2 · Sign in and approve
Click Connect. Claude opens Munin in a new window: sign in, review the modules and scopes Claude is asking for, and click Authorize. The connection acts as you — it inherits your role and can’t exceed it, and it can’t manage the team, billing, or API keys, or delete the org. It binds to the organization you have open in the dashboard when you approve, so switch first if you belong to more than one. Once you’re back in Claude the connector lights up and shows the tools it discovered.
3 · Enable per conversation
Adding the connector doesn’t auto-attach it to every chat. In the composer, open the + button → Connectors, and toggle Munin on. Claude will then call Munin tools when it decides they’re relevant — or you can name a tool directly in the prompt.
4 · Verify
Ask Claude “What MCP tools do you have for Munin?”. It should list the tools your role can use. If nothing shows up, the most common causes are a typo in the URL (the path is /mcp, not /v1/mcp), a sign-in that wasn’t completed or was later revoked — reconnect from Customize → Connectors — or the connector not enabled in the conversation.
5 · Manage access
Access lasts 90 days and refreshes automatically while Claude keeps using it. Revoke it at any time from Settings → Agents, after which Claude has to sign in again before it can call Munin.
Need narrower access than your role — a read-only answer-bot, say? Some Claude organizations have a Request headers section in the connector dialog (in beta). There you can choose No sign-in and add an authorization header with the value Bearer mn_admin_…, using a key from Settings → API keys scoped to exactly what Claude should do. Without that section, OAuth is the only option.