gRPC's strong typing and reflection/descriptor discovery make it a great alternative for the tool calling / MCP. In the first part I'd tried out ListTools + a generic CallTool over gRPC.
Now, I updated and am calling gRPC calls directly (tool → grpc_service/grpc_method) with Protovalidate + CEL for client/server pre-validation.
It helps solve the following issues of MCP : tool poisoning, version updating drift/undocumented changes, weaker trust boundaries, and proxy-unfriendly auth. The recent Vercel mcp-to-ai-sdk and Cloudflare’s Code-Mode are indications that we really want to adopt this kind of strong typing and I think gRPC is a great fit.
gRPC's strong typing and reflection/descriptor discovery make it a great alternative for the tool calling / MCP. In the first part I'd tried out ListTools + a generic CallTool over gRPC.
Now, I updated and am calling gRPC calls directly (tool → grpc_service/grpc_method) with Protovalidate + CEL for client/server pre-validation.
It helps solve the following issues of MCP : tool poisoning, version updating drift/undocumented changes, weaker trust boundaries, and proxy-unfriendly auth. The recent Vercel mcp-to-ai-sdk and Cloudflare’s Code-Mode are indications that we really want to adopt this kind of strong typing and I think gRPC is a great fit.
Part 1 : https://medium.com/@bharatgeleda/reimagining-mcp-via-grpc-a1...