Tool name (sanitized to MCP rules) — also how the executor finds the operation.
Path template with a leading slash, e.g. /product/{id}.
Path-template variable names, in template order — all required.
Query parameter names.
Whether this op carries a request body (the tool exposes it under body).
GET/HEAD — safe, side-effect-free. The default projection only exposes these.
@suluk/mcp— project ONE OpenAPI v4 document into a Model Context Protocol server. The same contract that drives the API, SDK, docs, admin, and panel now drives an agent-callable surface: every operation becomes an MCP tool (read-only by default; mutations opt-in viainclude:"all"), served over the Streamable-HTTP JSON-RPC transport as a Hono-mountable app. No hand-written tool schemas, no config drift — the contract is the single source. Pure projection (toolsFrom) + pure protocol (handleRpc) are independently testable;mcpAppwires transport. CANDIDATE tooling — NOT official OAS.