Prometheus Protocol provides an MCP-compliant server that acts as a secure trust layer for AI agents, offering identity (Passport), on-chain payments (Bank Account), and a trusted marketplace (App Store) as a cohesive, end-to-end stack. The MCP server exposes endpoints and tooling to register and verify agents, fetch canister/app data, and orchestrate interactions with DeFi primitives and marketplaces. With the included CLI and APIs, developers can programmatically manage identity proofs, token transfers, service registrations, and verifications, enabling agents to discover and interact with vetted services in a trusted environment.

To use the server, install the monorepo dependencies, start the MCP server, and connect your client or CLI tooling to the server’s endpoints. The repository provides a clI and scripts to bootstrap local development, deploy test canisters, and run verifier bots. Typical workflows include registering an agent identity, linking it to a marketplace service, configuring test tokens, and performing secure on-chain transactions through the integrated DeFi primitives. The server is designed to be compatible with MCP specifications and integrates with the Prometheus Protocol tooling for app discovery, audits, and verifiable identity.

Prerequisites:

• Node.js >= 18.x
• pnpm installed
• Git

1. Clone the repository git clone https://github.com/prometheus-protocol/prometheus-protocol.git cd prometheus-protocol

2. Install dependencies (monorepo) pnpm install

3. Build or prepare the server package (if a build step exists)

   Depending on the project structure, you may need to build packages

   pnpm -w build || echo "Build step may be optional for MCP server; follow repo-specific instructions."

4. Run the MCP server (local development)

   Ensure required environment variables are set as needed

   npm_config_unsafe_perm=true pnpm --filter @prometheus-protocol/server start

5. Verify the server is running curl http://localhost:PORT/health

Notes:

• Some steps may differ depending on the exact server package layout in the monorepo. Refer to QUICKSTART.md and docs/ for precise commands.
• If using Docker, consult the Docker deployment guidance in the repo if available.

Tips and common issues:

• Environment variables: The MCP server may expect DB_CONNECTION_STRING, PROMETHEUS_API_URL, and PORT. Provide sensible defaults or use a .env file.
• Monorepo management: Use pnpm workspaces to install and run specific packages to minimize install time.
• If endpoints return 404 or 500, ensure the server index file path in mcp_config matches the actual server entry point in the repository.
• For local testing, you can use the provided scripts to register dev verifiers and generate env files for docker-compose, as described in the Getting Started section of the README.
• Compatibility: This server aims to be MCP-compliant; verify with the MCP specification during integration to ensure all required endpoints and capabilities are exposed.