Munin
Munin developer portal
Get a key →
Guide · Clients

Wire OpenClaw to Munin.

OpenClaw treats MCP servers as first-class skills — once registered, every Munin tool shows up in the assistant’s tool list with no further wiring. The fastest path is the openclaw mcp add CLI command.

1 · Mint an API key

In the dashboard, go to Settings → API keys and create a key. Scope it to what OpenClaw should be allowed to do — read-only KB, full CRM write, or everything. The token starts with mn_admin_ and is shown once.

2 · Register the server (CLI)

The one-shot command writes the entry into ~/.openclaw/openclaw.json for you. Prefer streamable-http— it’s the modern Munin transport and handles long-running tool calls without an open SSE stream.

shellwrites ~/.openclaw/openclaw.json
openclaw mcp add munin \
  --url http://localhost:3001/mcp \
  --transport streamable-http \
  --header "Authorization: Bearer mn_admin_…" \
  --timeout 20

Or edit openclaw.json directly

OpenClaw reads ~/.openclaw/openclaw.json. Merge Munin under mcp.servers:

~/.openclaw/openclaw.jsonmerge with existing servers
{
  "mcp": {
    "servers": {
      "munin": {
        "url": "http://localhost:3001/mcp",
        "transport": "streamable-http",
        "timeout": 20,
        "headers": {
          "Authorization": "Bearer mn_admin_…"
        }
      }
    }
  }
}

For OAuth instead of a static bearer, drop the headers block and set "auth": "oauth". OpenClaw will run the PKCE flow on first connect.

3 · Verify

Run the doctor with a live probe — it opens an MCP session and lists the tools the server advertised:

shell
openclaw mcp doctor munin --probe
openclaw mcp list

If the probe fails, the most common causes are a typo in the URL (the path is /mcp, not /v1/mcp), a revoked token, or a transport mismatch (use streamable-http against Munin, not the default sse).

4 · Filter tools (optional)

Use toolFilter to keep agent prompts focused. A research-only assistant might want KB and CRM lookups but nothing that writes:

~/.openclaw/openclaw.json
{
  "mcp": {
    "servers": {
      "munin": {
        "url": "http://localhost:3001/mcp",
        "transport": "streamable-http",
        "headers": { "Authorization": "Bearer mn_admin_…" },
        "toolFilter": {
          "include": ["kb_*", "crm_get_*", "crm_search_*"],
          "exclude": ["*_delete_*"]
        }
      }
    }
  }
}

5 · Tighten scope

Mint a separate key per workstation or per agent so you can revoke one without disrupting the others. Pick the smallest scope set that lets OpenClaw do its job — read-only KB is plenty for a Q&A assistant, full conv:write is only needed if you want OpenClaw to actually send replies on your behalf.