Does googleapis/mcp-toolbox support native gRPC as an MCP transport?

2 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Native gRPC transport is not supported in mcp-toolbox as of the latest comment in this thread (July 2026); the feature request is still open and was kept at P2 priority. A maintainer explained that gRPC is not currently a supported transport under the Model Context Protocol (MCP) standard, and mcp-toolbox implements the standard MCP server transports. They could not commit to prioritizing a native gRPC listener while that is the case. The maintainer pointed to the community discussion at https://github.com/modelcontextprotocol/modelcontextprotocol/issues/966 (opens external site) ↗ and recommended advocating there for gRPC to become a standard MCP transport.

  No code or configuration fix was given. The only workaround described in the thread is running Envoy Proxy in front of mcp-toolbox to transcode gRPC connections from AI agents into HTTP/SSE. The reporter said it works as a proxy but adds extra configuration and infrastructure overhead. If your clients are gRPC-only, that Envoy layer is the only option presented in this thread until MCP itself gains a gRPC transport.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Worked)

  Reporter ran Envoy Proxy in front of mcp-toolbox to transcode gRPC MCP connections from their agents into HTTP/SSE. They reported it works as a proxy but adds configuration and infrastructure overhead.

  Source: https://github.com/googleapis/mcp-toolbox/issues/3080 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport