Skip to main content
Glama
@supernova123/grpc-mcp-server

@supernova123/grpc-mcp-server

@supernova123/grpc-mcp-server

Connect AI agents to any gRPC service — no proto files needed.

Most gRPC services are invisible to AI tools. This MCP server uses gRPC Server Reflection to auto-discover services, methods, and types at runtime, then exposes them as callable tools for Claude, Cursor, and any MCP-compatible agent.

Why This Matters

gRPC powers Kubernetes, Istio, Envoy, and thousands of microservices — but AI agents can't talk to any of them. Until now, you'd need to manually define proto schemas, generate clients, and wire everything together. This server does it automatically: point it at any gRPC endpoint with reflection enabled, and it discovers everything.

Use cases:

  • Debug microservices by invoking RPCs directly from Claude

  • Inspect live service meshes (Istio, Envoy) without kubectl

  • Build AI-powered ops tools that query gRPC health endpoints

  • Prototype API integrations without writing client code

  • Test gRPC services during development with natural language

Related MCP server: gRPC Invoke MCP

Tools

Tool

Description

connect_endpoint

Connect to a gRPC server and auto-discover all services via reflection

list_services

List every gRPC service on the connected endpoint

list_methods

List all RPC methods for a service (unary, server-stream, client-stream, bidi)

get_service_descriptor

Get full service schema: methods, request/response types, streaming modes

invoke_rpc

Call any RPC method with a JSON-serialized request body

health_check

Standard gRPC Health Checking Protocol (v1)

disconnect

Clear cached service data and disconnect

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "grpc": {
      "command": "npx",
      "args": ["-y", "@supernova123/grpc-mcp-server"],
      "env": {
        "GRPC_ENDPOINT": "localhost:50051"
      }
    }
  }
}

Cursor / VS Code

{
  "mcp": {
    "servers": {
      "grpc": {
        "command": "npx",
        "args": ["-y", "@supernova123/grpc-mcp-server"],
        "env": {
          "GRPC_ENDPOINT": "localhost:50051"
        }
      }
    }
  }
}

Direct

npx @supernova123/grpc-mcp-server

Example Usage

  1. Connect to a gRPC server:

    connect_endpoint(endpoint="localhost:50051")
  2. Discover available services:

    list_services()
  3. Inspect a service's methods:

    list_methods(service_name="grpc.health.v1.Health")
  4. Invoke an RPC:

    invoke_rpc(
      service_name="grpc.health.v1.Health",
      method_name="Check",
      request={"service": ""}
    )

Environment Variables

Variable

Description

Default

GRPC_ENDPOINT

Target gRPC endpoint (host:port)

(none — use connect_endpoint)

GRPC_TIMEOUT_MS

Request timeout in milliseconds

10000

GRPC_USE_TLS

Enable TLS connections

false

Requirements

Most gRPC servers have reflection enabled in development. For production servers, ensure grpc.reflection.V1Reflection is registered.

How It Works

  1. Connects to your gRPC endpoint via the reflection API

  2. Fetches the full service descriptor (services → methods → types)

  3. Dynamically generates MCP tool definitions from the schema

  4. Invokes RPCs by serializing JSON requests to protobuf and back

No proto files. No code generation. No compile step.

License

MIT

Available Tools

7 tools
connect_endpointB

Connect to a gRPC server endpoint and discover available services via server reflection

Inputs: endpoint (required), use_tls, timeout_ms.

disconnectA

Disconnect from the current gRPC endpoint and clear cached service data

Inputs: no named parameters.

get_service_descriptorA

Get the full descriptor for a gRPC service including all methods, request/response types, and streaming modes

Inputs: service_name (required).

health_checkB

Check gRPC server health using the standard Health Checking Protocol

Inputs: service, timeout_ms.

invoke_rpcC

Invoke a gRPC method with a JSON-serialized request body

Inputs: service_name (required), method_name (required), request, timeout_ms, +1 more.

list_methodsB

List all methods for a specific gRPC service

Inputs: service_name (required).

list_servicesA

List all gRPC services discovered via server reflection on the connected endpoint

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: connection management, service discovery, health checking, and invocation. There is no overlap in functionality.

    Naming Consistency5/5

    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.

    Tool Count5/5

    Seven tools is an ideal size for a gRPC MCP server, covering all core operations without being excessive or insufficient.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for calling gRPC methods from AI agents, enabling them to inspect gRPC APIs and invoke unary RPCs using server reflection or local .proto files.
      57 npm
      1
      MIT