macp-mcp 0.1.0__tar.gz

macp_mcp-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

macp_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,225 @@
+Metadata-Version: 2.4
+Name: macp-mcp
+Version: 0.1.0
+Summary: MCP server that lets any MCP client run or join a MACP Decision session
+Author-email: Multi-Agent Coordination Protocol <macp@multiagentcoordinationprotocol.org>
+License: Apache-2.0
+Project-URL: Homepage, https://multiagentcoordinationprotocol.io
+Project-URL: Repository, https://github.com/multiagentcoordinationprotocol/macp-mcp
+Project-URL: Changelog, https://github.com/multiagentcoordinationprotocol/macp-mcp/blob/main/CHANGELOG.md
+Project-URL: Bug Tracker, https://github.com/multiagentcoordinationprotocol/macp-mcp/issues
+Keywords: mcp,macp,multi-agent,coordination,model-context-protocol
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: macp-sdk-python<0.19,>=0.18.0
+Requires-Dist: mcp<3,>=2.3.0
+Requires-Dist: typing-extensions>=4.12
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-cov>=5.0; extra == "dev"
+Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Requires-Dist: build>=1.0; extra == "dev"
+Requires-Dist: twine>=5.0; extra == "dev"
+Requires-Dist: jsonschema>=4.0; extra == "dev"
+Dynamic: license-file
+
+# 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 Code
+
+```bash
+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`:
+
+```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:
+
+```json
+"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 for `get_commitment` and `verify` to 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's `GetSession`
+  returns 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 a `BLOCK`) 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](https://github.com/multiagentcoordinationprotocol/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.
+
+## Tool contract
+
+[`contract/tools.json`](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](https://github.com/multiagentcoordinationprotocol/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
+
+```bash
+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
+make test-integration-docker  # CI's integration gate: pinned runtime image + stdio MCP clients
+make transcript               # re-record examples/decision-via-mcp.md (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-0.1.0/README.md

@@ -0,0 +1,190 @@
+# 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 Code
+
+```bash
+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`:
+
+```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:
+
+```json
+"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 for `get_commitment` and `verify` to 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's `GetSession`
+  returns 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 a `BLOCK`) 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](https://github.com/multiagentcoordinationprotocol/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.
+
+## Tool contract
+
+[`contract/tools.json`](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](https://github.com/multiagentcoordinationprotocol/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
+
+```bash
+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
+make test-integration-docker  # CI's integration gate: pinned runtime image + stdio MCP clients
+make transcript               # re-record examples/decision-via-mcp.md (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