Skip to main content
Glama
Yuki4-dev

gRPC MCP Server

by Yuki4-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to gRPC MCP Server

No user-submitted related servers found.

    Related Servers

    • Generalized MCP Server

      sarptandoven
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Dynamically exposes Python SDKs (Kubernetes, GitHub, Azure) through an agent-friendly gRPC interface. Enables interaction with cloud services and platforms using natural language by automatically converting SDK functionality into callable functions.
      -

    • 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.
      31
      1
      MIT

    • gcp-mcp-server

      LokiMCPUniverse
      F
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server for Google Cloud Platform, enabling interaction with Resource Manager, Compute Engine, Cloud Storage, BigQuery, Pub/Sub, and Cloud Logging via natural language.
      3
      -

    • Pro Tools MCP Server

      skrul
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Pro Tools via the PTSL gRPC API, providing session management, timeline navigation, track control, clip management, editing, markers, transport, audio analysis, and more.
      18
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: sending requests, loading proto definitions, and retrieving method information. There is no overlap or ambiguity in their intended functions.

    Naming Consistency5/5

    All tool names follow a consistent camelCase verb-noun pattern (sendRequest, loadProto, getMethodInformation). Naming is uniform and predictable.

    Tool Count4/5

    Three tools is compact but sufficient for the core gRPC workflow: load definitions, inspect methods, and send requests. It is slightly minimal but not overly thin for the stated purpose.

    Completeness4/5

    The set covers the essential lifecycle: loading proto files, retrieving method details, and making requests. Minor gaps like service listing or advanced request features exist, but core operations are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources