macp MCP server
Commit 8. Nov. 2026Ermöglicht es MCP-Clients, kontrollierte Entscheidungssitzungen mit verifizierbaren Commitments über das Multi-Agent Coordination Protocol durchzuführen oder daran teilzunehmen.
Auch bekannt als multiagentcoordinationprotocol/macp-mcp
- Stars
- 0
- Tools
- 8
- Downloads, 30 Tage
- —
- Neueste Version
- —
- Letzter Commit
- 8. Nov. 2026
- Lizenz
- Apache-2.0
Was ist macp MCP?
Ermöglicht es MCP-Clients, kontrollierte Entscheidungssitzungen mit verifizierbaren Commitments über das Multi-Agent Coordination Protocol durchzuführen oder daran teilzunehmen. Er stellt 8 Tools bereit, etwa start_session, propose, vote.
Zusammenfassung generiert aus dem README des Projekts
Über macp MCP server
macp-mcp ermöglicht es Entwicklern, die Nutzung von Multi-Agent Tools durch kontrollierte Entscheidungssitzungen zu verwalten, wenn sie Clients wie Claude Desktop, Claude Code oder Cursor nutzen. Es fungiert als Schnittstelle zwischen einem MCP Client und einer MACP Runtime und erlaubt es Modellen, spezifische Aktionen vorzuschlagen, darüber abzustimmen und diese zu committen. Dies stellt sicher, dass die Tool-Ausführung nicht allein durch ein Modell entschieden wird, sondern Regeln für die Mitgliedschaft und Identität unterliegt, die von der Runtime erzwungen werden.
Nutzer können diesen Server lokal mit einer Dockerisierten MACP Runtime ausführen oder sich über einen Bearer Token mit einer Produktionsumgebung verbinden. Der Server stellt spezifische Tools wie start_session, propose, vote und commit bereit, um den Lebenszyklus einer Entscheidung zu verwalten. Er enthält außerdem einen Gate-Mode, der als Proxy fungiert, Tool-Aufrufe von einem Upstream-Server abfängt und ein Quorum oder eine Entscheidungssitzung erfordert, bevor der Aufruf fortgesetzt werden darf. Dies erstellt durch RFC-MACP-0013 Hashes für jedes Ergebnis einen verifizierbaren Audit-Trail.
Was du damit machen kannst
- 1Koordinierung von Multi-Agent Deployment-EntscheidungenEin AI Agent kann eine Session starten, um einen spezifischen Rollout-Plan vorzuschlagen und Stimmen von anderen Teilnehmern einzuholen.
- 2Durchsetzung von Tool-Use-PoliciesEntwickler können den Gate-Proxy nutzen, um sicherzustellen, dass sensible Tools wie das Schreiben von Dateien erst nach der Zustimmung eines Quorums an Genehmigern ausgeführt werden.
- 3Verifizierung von EntscheidungsergebnissenDu kannst einen Commitment-Hash neu berechnen, um sicherzustellen, dass die aufgezeichnete Entscheidung nicht manipuliert wurde.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
macp MCP tools 8
Erkannt aus dem READMEstart_sessionproposevoteget_commitmentverifyevaluatecommitget_session
| start_session | — | |
| propose | — | |
| vote | — | |
| get_commitment | — | |
| verify | — | |
| evaluate | — | |
| commit | — | |
| get_session | — |
Konfiguration
MACP_AGENT_IDMACP_ALLOW_INSECUREMACP_AUTH_TOKENMACP_RUNTIME_TARGET
| Name | Beschreibung | Typ |
|---|---|---|
| MACP_AGENT_ID | — | |
| MACP_ALLOW_INSECURE | — | |
| MACP_AUTH_TOKEN | — | |
| MACP_RUNTIME_TARGET | — |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarmultiagentcoordinationprotocol/macp-mcp is public and reachablegithub.com/multiagentcoordinationprotocol/macp-mcp ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-08github.com/multiagentcoordinationprotocol/macp-mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell8 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNo tool named like delete, drop or execBestanden
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenmacp-mcp
An MCP server that lets any MCP client (Claude Desktop, Claude Code, Cursor and others) run or join a MACP 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 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
pip install macp-mcp # or: uvx macp-mcp
Python 3.11 or newer. It needs a MACP runtime to talk to. For local development:
docker run -p 50051:50051 -e MACP_ALLOW_INSECURE=1 -e MACP_MEMORY_ONLY=1 \
ghcr.io/multiagentcoordinationprotocol/macp-runtime:0.14.1
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):
{
"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 Code
claude mcp add macp \
--env MACP_RUNTIME_TARGET=127.0.0.1:50051 \
--env MACP_AGENT_ID=coordinator \
--env MACP_ALLOW_INSECURE=1 \
-- uvx macp-mcp
Or check it into a project's .mcp.json:
{
"mcpServers": {
"macp": {
"command": "uvx",
"args": ["macp-mcp"],
"env": {
"MACP_RUNTIME_TARGET": "127.0.0.1:50051",
"MACP_AGENT_ID": "alice",
"MACP_ALLOW_INSECURE": "1"
}
}
}
}
Then ask the model something like: "Start a MACP decision with alice on which deployment plan to use, propose a canary rollout, and vote for it."
Against a production runtime
Drop MACP_ALLOW_INSECURE and pass the bearer token the runtime issued for
this agent:
"env": {
"MACP_RUNTIME_TARGET": "macp.example.com:443",
"MACP_AGENT_ID": "coordinator",
"MACP_AUTH_TOKEN": "<token issued for coordinator>"
}
Environment variables
| Variable | Default | Meaning |
|---|---|---|
MACP_RUNTIME_TARGET |
127.0.0.1:50051 |
Runtime gRPC address (host:port). |
MACP_AGENT_ID |
mcp-agent |
The MACP agent this server acts as. With dev-agent auth it is also the bearer token. With MACP_AUTH_TOKEN it is the identity the runtime must bind the token to. |
MACP_AUTH_TOKEN |
unset | Bearer token issued by the runtime. When unset, dev-agent auth is used, which needs a runtime started with MACP_ALLOW_INSECURE=1. |
MACP_ALLOW_INSECURE |
off | 1 uses plaintext gRPC. For a local runtime only. |
MACP_TLS_CA_FILE |
system trust | PEM bundle for a private CA. Cannot be combined with MACP_ALLOW_INSECURE. |
MACP_DEFAULT_TTL_MS |
300000 |
Session TTL used when start_session is called without ttl_ms. |
MACP_REPLAY_IDLE_MS |
1000 |
How long a history read waits for the next envelope before treating the replay as complete. |
The server logs to stderr only, because stdout carries the MCP protocol. A bad configuration exits with status 2 and a one-line message.
Tools
| Tool | Kind | What it does |
|---|---|---|
start_session |
write | Start a Decision session with this agent as initiator. Takes intent, participants and optional ttl_ms and context_id. Returns the session_id to share. |
propose |
write | Put an option (proposal_id, option, rationale) up for decision. |
vote |
write | Cast this agent's APPROVE / REJECT / ABSTAIN vote on a proposal. |
get_commitment |
read | The resolved session's binding Commitment, the exact payload bytes (payload_b64) and its RFC-MACP-0013 commitment_hash. |
verify |
read | Recompute a commitment hash with the SDK verifier, either from the runtime's recorded history (session_id) or from bytes you hold (payload_b64). Returns match, mismatch or cannot_verify. |
evaluate |
write | Record a scored assessment (APPROVE / REVIEW / BLOCK / REJECT, confidence 0..1) before voting. |
commit |
write | Resolve the session with a binding Commitment (action, authority_scope, reason). Under the default policy only the initiator can commit. |
get_session |
read | The session's state, participants, proposals, evaluations, votes, approve totals and majority winner. |
The first five are the core loop: start, propose, vote, read the outcome and check it. The other three are the minimum needed to make that loop usable from MCP:
commit: a Decision session only resolves, and only produces a Commitment forget_commitmentandverifyto read, when someone commits. Without this tool an MCP client could never finish a session it started.get_session: MCP is request/response, and the runtime'sGetSessionreturns metadata only. Without this tool a model joining a session has no way to see what was proposed or how the votes stand. It rebuilds the session view from the runtime's replayable history.evaluate: the Decision mode's assessment step. It lets an agent record a reasoned, scored opinion (including aBLOCK) that other participants and later auditors can see, separately from the bare vote.
Objections, cancellation, signals and other modes are deliberately left out. They belong to orchestrators built on macp-sdk-python.
Errors the model can act on, such as a runtime rejection or a bad argument,
come back as tool errors with the text "<CODE>: <message>", for example
FORBIDDEN: Forbidden when a non-initiator tries to commit. The code is the
MACP error code (the Ack failure code, then the macp-error-code trailer,
then the gRPC status name).
The server is stateless. Every read replays the session from the runtime, so a restart loses nothing, and several servers (agents) can share one session.
Gate an MCP server's tool calls (macp-mcp gate)
macp-mcp gate is an MCP proxy. Put it in front of any stdio MCP server, and
the tool calls you name in a policy file run only after a MACP session
approves them:
macp-mcp gate --policy gate.json --upstream npx -y @modelcontextprotocol/server-filesystem /srv
Everything after --upstream is the upstream's command line. Your MCP client
spawns the gate instead of the upstream. The gate lists the upstream's tools
unchanged.
{
"version": 1,
"server": "filesystem",
"rules": [
{ "tool": "write_file", "mode": "macp.mode.quorum.v1",
"participants": ["alice", "bob", "carol"], "threshold": 2, "ttl_ms": 120000 },
{ "tool": "move_*", "mode": "macp.mode.decision.v1",
"participants": ["alice", "bob"], "ttl_ms": 60000 }
]
}
A tools/call that matches no rule is forwarded as-is. The first rule that
matches (* and ? are wildcards) makes the gate, acting as MACP agent
MACP_AGENT_ID, do this:
-
Open a Quorum or Decision session with the rule's
participantsas approvers. Itscontext_idissha256:plus the hex SHA-256 of the RFC 8785 canonical JSON of{arguments, server, tool}, which binds the session to this exact call. The approvers find it by thatcontext_id(ListSessions/WatchSessions) and vote with any MACP client. -
Commit as soon as the outcome is settled: approve once
thresholdapprovers (default: a strict majority) have approved, deny once that can no longer happen. Each approver's first ballot counts. -
Approved: forward the call. The upstream's result comes back with the Commitment attached, next to any
_metathe upstream set:"_meta": { "io.multiagentcoordinationprotocol/commitment": { "session_id": "…", "mode": "macp.mode.quorum.v1", "outcome": "approve", "commitment_hash": "sha256:…" } }commitment_hashis the RFC-MACP-0013 hash. Check it with theverifytool or any MACP SDK. -
Refused: return a tool error and never call the upstream. The error starts with
POLICY_DENIED(the approvers denied it, or a runtime policy refused the commitment) orSESSION_NOT_OPEN(the session expired or was cancelled first). An argument holding an integer outside ±(2^53−1) is refused withINVALID_ARGUMENTbefore any session opens, because it has no canonical form to bind.
The gate passes its environment on to the upstream, minus MACP_AUTH_TOKEN.
examples/gated-tool-call.md is a recorded run
against the pinned runtime: one passthrough, one approved write, one rejected
write and one expired delete.
contract/gate/ pins the policy schema, the CLI, the session
shape, the refusal texts and the context_id vectors. The TypeScript twin
uses a byte-identical copy.
Binding a runtime policy (policy_version)
A rule can bind the session, through policy_version, to an RFC-MACP-0012
policy registered on the runtime. Set the rule's threshold to at least the
bound policy's threshold. The gate commits on its own tally, so with a lower
rule threshold it commits early and the runtime refuses the Commitment:
- Decision: the refusal is
POLICY_DENIED: <runtime message>. - Quorum: macp-runtime 0.14.0 applies a policy threshold inside the mode's
commitment-readiness check, so the refusal is
INVALID_ENVELOPE(an invalid payload), notPOLICY_DENIED.
In both modes the gate fails safe. The call is refused after the first
approval, the upstream is never called, and the gate cancels the session
(CANCELLED). The note under policy_binding in
contract/gate/session.json records the same
behaviour. Integration tests pin it against runtime 0.14.0:
tests/integration/test_gate_policy.py
(added in #12)
and the TypeScript twin's
gate-policy.test.ts
(#10).
Tool contract
contract/tools.json pins the tool names,
descriptions, annotations, input schemas and output schemas. It is fully
inlined JSON Schema 2020-12. The TypeScript twin
(macp-mcp-typescript)
exposes the identical surface and tests against a byte-identical copy of this
file. Any change to the tool surface changes the manifest (make contract)
and needs the matching change in the TypeScript twin.
Development
make setup # pip install -e ".[dev]"
make lint typecheck test # ruff, mypy strict, unit tests + 85% coverage gate
make verify-contract # advertised tools == contract/tools.json; gate contract checks
make test-integration-docker # CI's integration gate: pinned runtime image + stdio MCP clients
make transcript # re-record examples/*.md transcripts (runtime on :50051)
Releases follow macp-sdk-python: release-please opens the release PR, and
merging it tags vX.Y.Z, which publishes to PyPI through trusted publishing.
License
Apache-2.0
macp MCP Fragen
Welche Tools bietet macp MCP?
Er stellt 8 Tools bereit, darunter start_session, propose, vote, get_commitment, verify.
Was bewirkt MACP für die Nutzung von MCP Tools?
Während MCP entscheidet, welche Tools ein Modell aufrufen kann, entscheidet MACP, wer sie wann nutzen darf, und protokolliert diese Entscheidung.
Kann ich das nutzen, um spezifische Tool-Aufrufe einzuschränken?
Ja, du kannst den 'macp-mcp gate' Proxy verwenden, um für bestimmte in einer Policy-Datei definierte Tools eine Genehmigung durch eine MACP-Session zu erzwingen.
Wie verifiziere ich ein Entscheidungsergebnis?
Du kannst das verify Tool nutzen, um einen Commitment-Hash aus der aufgezeichneten Historie der Runtime oder aus bereitgestellten Payload-Bytes neu zu berechnen.
Ist der Server stateful?
Nein, der Server ist stateless, da jeder Lesevorgang die Session aus der Runtime repliziert.