I built a small Go library named grpc-mcp-gateway that applies the grpc-gateway principle to MCP.
It seems the world of tooling is going toward LLMs, and I wanted to experiment through my current favorite stack (Go/gRPC).
Basically, instead of having to code your server from scratch, and maintain it piece by piece, you can just write the public API desired on a Protofile and it maps directly into your gRPC server, making it quite easy to develop and extend MCP tools for your projects.
I wasn’t happy with existing MCP libraries, and I really like having the gateway definitions live directly in my Protofiles. It makes the API more maintainable and readable for me. I'm pretty sure several people would think the same given the success of the library it's inspired from.
Let me know what you think. Cheers!
Top comments (0)