peac

The PEAC MCP server integrates with the PEAC Protocol reference implementation to expose machine-accessible coordination for verifiable interaction records. It leverages the PEAC artifact model (policy discovery via /.well-known/peac.txt and verifiable receipts) to enable tool orchestration and cross-org communication with cryptographic proofs. This MCP server acts as a bridge that can be queried by MCP clients to discover available capabilities, initiate interactions, and return signed receipts that can be verified offline by verifiers. Use cases include automated agent workflows, governance tooling, and cross-organization automation where verifiable interaction evidence is required. The server can coordinate with MCP-powered tools and gateways to support discovery, request handling, and response delivery while emitting PEAC receipts in responses where applicable.

Prerequisites:

• Node.js 22 or newer installed on the host
• npm or pnpm available in PATH
• Access to the PEAC repository or package registry if deploying from source

1. Install Node.js prerequisites (example with Node 22+):

   • On macOS with Homebrew: brew install node
   • On Ubuntu: sudo apt-get update && sudo apt-get install -y nodejs npm

2. Clone the MCP server repository (or prepare your deployment bundle): git clone https://github.com/peacprotocol/peac.git cd peac

3. Install dependencies:

   • Using npm: npm install
   • Using pnpm: npm i -g pnpm; pnpm install

4. Build if a build script exists (optional, depending on setup): npm run build

5. Run the server:

   • Development: node path/to/server.js
   • Or using a process manager (recommended): pm2 start path/to/server.js --name peac-mcp

6. Verify the server is running:

   • Check logs for startup confirmation
   • Send a test MCP request to the configured port/endpoint

Note: If your deployment expects environment variables (e.g., for keys or endpoints), provide them via your hosting environment or an .env file and load them in your start script.

Tips and common considerations:

• The PEAC protocol relies on machine-readable policy discovery at /.well-known/peac.txt and issuer public keys at /.well-known/peac-issuer.json. Ensure these endpoints are publicly accessible to MCP clients.
• If you publish a PEAC_RECEIPT header in responses, ensure your server signs receipts with a supported Ed25519 key and that the public keys are rotatable via the issuer JWKS endpoint.
• For production deployments, use a process manager (e.g., PM2 or systemd) and enable TLS termination at the load balancer or reverse proxy.
• Environment variables often required include keys for signing receipts, issuer identifiers, and policy references. Example: { "PEAC_SIGNING_KEY": "<base64-encoded-key>", "PEAC_ISSUER_ID": "issuer-id", "PEAC_POLICY_URL": "https://your-domain/.well-known/peac.txt" }
• Keep the Node.js version aligned with the project’s compatibility (Node >= 22 as recommended by the Quick Start).
• If you upgrade to PEAC wire 0.2+ (peek at next), update dependencies and verify the receipt format compatibility in your verifier.