tools/list

Tool discovery is transparently proxied from the upstream MCP server.

tools/list does not need a zero-knowledge authorization decision. The gateway forwards the request to the upstream MCP client and returns the upstream result.

While proxying the response, zkMCP stores each tool's output schema so later tools/call responses can be projected correctly by the MCP SDK.

This preserves the existing server's tool definitions instead of creating a second copy inside zkMCP.

Integration patterns

Practical ways to introduce zkMCP into an existing agent and MCP deployment.

tools/call

The MCP enforcement point where zkMCP normalizes a requested side effect, proves authority, and forwards only after authorization succeeds.