@supernova123/grpc-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRPC_USE_TLS | No | Enable TLS connections. Set to 'true' to enable. | false |
| GRPC_ENDPOINT | No | Target gRPC endpoint. If not provided, use connect_endpoint tool. | |
| GRPC_TIMEOUT_MS | No | Request timeout in milliseconds. | 10000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_endpointB | Connect to a gRPC server endpoint and discover available services via server reflection |
| disconnectA | Disconnect from the current gRPC endpoint and clear cached service data |
| list_servicesA | List all gRPC services discovered via server reflection on the connected endpoint |
| list_methodsB | List all methods for a specific gRPC service |
| get_service_descriptorA | Get the full descriptor for a gRPC service including all methods, request/response types, and streaming modes |
| invoke_rpcC | Invoke a gRPC method with a JSON-serialized request body |
| health_checkB | Check gRPC server health using the standard Health Checking Protocol |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear, distinct purpose: connection management, service discovery, health checking, and invocation. There is no overlap in functionality.
All tools use consistent snake_case with a verb_noun pattern (e.g., connect_endpoint, list_services, invoke_rpc). The pattern is uniform and descriptive.
Seven tools is an ideal size for a gRPC MCP server, covering all core operations without being excessive or insufficient.
The tool set covers the full lifecycle: connect, discover, inspect, health check, invoke. Minor gap: explicit support for streaming modes could be clarified, but overall complete.