MCP server that lets any MCP client run or join a MACP Decision session
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"macp-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# macp-mcp An MCP server that lets any MCP client (Claude Desktop, Claude Code, Cursor and others) run or join a [MACP](https://multiagentcoordinationprotocol.io) Decision session. **The first proof that MACP governs MCP tool use.** MCP decides which tools a model can call. MACP decides who may use them and when, and records what was decided. The model drives every step through ordinary MCP tool calls. The MACP runtime enforces who may propose, vote and commit, ends the session in one binding Commitment, and gives that outcome an RFC-MACP-0013 hash that anyone can recompute. [`examples/decision-via-mcp.md`](examples/decision-via-mcp.md) is a recorded run: two MCP clients drive a session to `RESOLVED`. The runtime refuses the non-initiator's `commit` call, and the commitment hash verifies. ``` MCP client (model) ──stdio──▶ macp-mcp ──gRPC──▶ MACP runtime tool calls one MACP agent enforces membership, order, (macp-sdk-python) identity; records the Commitment ``` ## Install ```bash pip install macp-mcp # or: uvx macp-mcp ``` Python 3.11 or newer. It needs a MACP runtime to talk to. For local development: ```bash docker run -p 50051:50051 -e MACP_ALLOW_INSECURE=1 -e MACP_MEMORY_ONLY=1 \ ghcr.io/multiagentcoordinationprotocol/macp-runtime:0.9.0 ``` One `macp-mcp` process is one MACP agent. To have several agents take part in a session, run one server per agent (for example, one per MCP client), each with its own `MACP_AGENT_ID`. ## Configure your MCP client ### Claude Desktop Add the server to `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "macp": { "command": "uvx", "args": ["macp-mcp"], "env": { "MACP_RUNTIME_TARGET": "127.0.0.1:50051", "MACP_AGENT_ID": "coordinator", "MACP_ALLOW_INSECURE": "1" } } } } ``` If you installed with pip, use `"command": "macp-mcp"` and drop `args`. ### Claude …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.