MCP.so
登录

grpcmcp MCP Server

@adiom-data

基本信息

分类

其他

许可证

Apache-2.0

传输方式

stdio

作者

adiom-data

提交者

Mark Chua

关于 grpcmcp MCP Server

MCP Server for gRPC

grpcmcp MCP Server 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

grpcmcp MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is grpcmcp?

grpcmcp is an MCP server that proxies to a gRPC backend using a provided protobuf descriptor file or server reflection. It exposes unary gRPC methods as MCP tools for AI agents and clients.

How to use grpcmcp?

Install with go install github.com/adiom-data/grpcmcp, then run with flags like --reflect for reflection or --descriptors for a descriptor file. Use --hostport to serve over HTTP (Streamable HTTP or SSE) or configure via command/args in an MCP client for STDIN transport.

Key features of grpcmcp

  • Proxies to gRPC backends using reflection or descriptor files
  • Exposes unary gRPC methods as MCP tools
  • Supports Streamable HTTP, legacy SSE, and STDIN transports
  • Filters services with the --services flag
  • Attaches Bearer tokens or custom headers to backend calls
  • Can be embedded as a Go library

Use cases of grpcmcp

  • Enable AI agents to call gRPC services via natural language
  • Bridge existing gRPC infrastructure to MCP-compatible clients
  • Expose selected gRPC endpoints through a controlled MCP interface

常见问题

1

What gRPC methods does grpcmcp support?

Only unary gRPC methods are exposed as MCP tools. Client-streaming, server-streaming, and bidi-streaming methods are skipped.

2

What transports does grpcmcp support for client connections?

grpcmcp supports Streamable HTTP (default when `--hostport` is set), legacy SSE, and STDIN transport.

3

Can grpcmcp be used as a Go library?

Yes, it can be embedded via `grpcmcp.NewServer()` with a `Config` struct, allowing custom descriptor loading, HTTP clients, and dynamic header providers.

4

How does authentication work with grpcmcp?

Outbound backend auth is configured via `--bearer`, `--bearer-env`, or `--header` flags. For dynamic auth, use `ToolHeaderProvider` in library mode. Inbound MCP auth is handled by wrapping the HTTP handler with standard Go middleware.

5

How are 64-bit integers handled in MCP schemas?

With the `--string64` flag, 64-bit protobuf integer fields (`int64`, `uint64`, etc.) are exposed only as strings in MCP JSON schemas to avoid precision loss for JavaScript clients.

评论

其他 分类下的更多 MCP 服务器