Skip to main content
Glama
friendlygeorge

@supernova123/grpc-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @supernova123/grpc-mcp-server

No user-submitted related servers found.

    Related Servers

    • gRPC Invoke MCP

      grulex
      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.
      20 npm
      1
      MIT

    • spiderswitch

      hiddenpath
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.
      Apache 2.0

    • agentforge

      doggychip
      F
      license
      A
      quality
      F
      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
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources