The MCP architecture
MCP defines: (a) a host — the AI client (Claude Desktop). (b) a server — a tool provider (us, GitHub MCP, filesystem MCP, etc). (c) a transport — JSON-RPC over stdio or HTTP. (d) a tool surface — typed tools with schemas. The host invokes tools from servers; servers respond. Standard RPC pattern, scoped to AI integration.
Tools we expose
GenZAgents MCP server exposes 16 tools: draft_receipt, verify_receipt, countersign_receipt, lookup_agent_reputation, restore_chat, capture_session, snapshot_agent_memory, list_my_agents, list_my_receipts, list_my_chats, get_agent, get_owner, request_agent_access, watchlist_add, dispute_receipt, transfer_agent. Each is documented in the server's tools/list response so the host can describe them to the model.
Why MCP server vs API key
Pure API integration would require every IDE / chat host to write custom integration code. MCP is the standardisation: write the server once; every MCP-supporting host gets it for free. As MCP adoption grows (Claude Desktop, Cursor, Cline, Windsurf, ChatGPT eventual support, future hosts), our integration footprint grows with no per-host work.
MCP transport — stdio + HTTP
We support both transports. Stdio: the host launches the server as a subprocess, communicates over stdin/stdout. Used by Claude Desktop, Cursor. HTTP: the server runs as a long-running process; the host connects via HTTP. Used by some custom hosts. Same tools either way.
MCP tool authorization
When the model wants to call a tool, the host typically asks the user "OK to call genzagents.draft_receipt?". Some tools (read-only lookups) can be marked auto-approve; others (write tools, payment-adjacent tools) require explicit consent. Standard MCP pattern; lets users stay in control of what the model does on their behalf.
What if MCP becomes irrelevant
Possible but unlikely. MCP is an Anthropic-led standard but actively adopted by OpenAI ecosystem (via the openai-mcp adapter), the Claude ecosystem, Cursor / Cline / Windsurf, and emerging agent frameworks. If a competing standard emerges (Google's ANP or similar), we add support — the receipt-issuance layer is protocol-agnostic.