Munim MCP server

Munim

<!-- mcp-name: io.github.vishalsg42/munim --> <!-- The line above is how the MCP Registry verifies that this package is ours: it looks for it in the PyPI long description, which is this file. Do not remove it. -->

One MCP server holding a live session with every client's account at once.

A coding agent can be logged in to one Cloudflare account. One Vercel. One Resend. Connect a second client and the first goes away. So the person looking after a dozen small businesses runs a dozen agent sessions, and none of them can answer a question about more than one client.

Munim holds them all. Each client gets its own registration with the provider, its own token and its own namespace in the tool list, so one agent can read across every client and write inside the one you named.

Kloudfirst       -> Kloudfirst@gmail.com's Account   (3 tools)
Ivy & Fern       -> ivy@example.com's Account        (3 tools)

both sessions opened concurrently, one process, no logout

That is a real run against two real Cloudflare accounts, not a diagram. The second account is a client's and their address is replaced here: they did not consent to a public repository, and this file is also the PyPI page. Reproduce it with your own two: scripts/crossaccountprobe.py.

Install

Requires Python 3.10+. Nothing else: no Node, no build step, no account to create first.

uv tool install munim          # or: pipx install munim, or: pip install munim
claude mcp add munim -- munim-mcp

If a coding agent is doing the install for you, point it at llms-install.md, which says the parts that are easy to get wrong when nobody is watching the terminal, and where it has to stop and hand back.

Start

munim clients                          # who you look after, and what is connected
munim clients add "Ivy & Fern"         # write one down, connect nothing yet
munim connect "Ivy & Fern" cloudflare  # a browser opens; that is the whole setup

There is no wrong order. Connect first and the account you sign in to names the client, or write the client down first and connect whenever. Both arrive in the same place.

Then ask your coding agent something a single logged-in session cannot answer:

which of my clients has a domain expiring this quarter?
check ivyandfern.co.uk for Ivy & Fern Studio

Doing the work, not just the diagnosis

Munim does not wrap each provider in verbs of its own. Every provider here runs its own MCP server with its own tools, so Munim forwards them and supplies the credential:

munim tools "Ivy & Fern" cloudflare          # what that account can be asked to do
munim call  "Ivy & Fern" cloudflare execute --args '{"code": "..."}'

Your coding agent gets the same two as listprovidertools and callprovidertool. There is no model in this path, so it works with agents off, and every call is written to the run log with the tool and its arguments. A call names one client and resolves that client's credentials alone.

When a provider's own MCP server does not publish what you need, callproviderapi goes a layer down and makes one HTTP call to that provider's API with the same client's credential. Vercel publishes no environment-variable write and no way to attach a domain to a project, which is what this is for. It takes a path and never a URL, and refuses anything that would send the credential to another host.

Shortened. The full README is on GitHub.