InfoQ 中文T2·78 pts
- Registry and Proxy are split: the control plane owns tool definitions, schemas and ownership, while the runtime translates MCP requests into HTTP, gRPC or TChannel calls
- AutoCrawler scans Protobuf and Thrift IDL registries to auto-generate MCP schemas and uses LLMs to write tool descriptions, lowering onboarding cost
- Response Projection lets agents request only needed fields instead of full payloads, easing context bloat
- Practitioners note the design closely mirrors existing API and GraphQL gateways, and that security and governance concerns persist under MCP