Skip to main content
Glama
runpod

RunPod MCP Server

Official
by runpod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to RunPod MCP Server

No user-submitted related servers found.

    Related Servers

    • RunPod MCP Server

      Niel-RunPod
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with the RunPod REST API through Claude or other MCP-compatible clients for managing pods, endpoints, templates, network volumes, and container registry authentications.
      26
      MIT

    • my-mcp-server

      15972289829
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      67 npm
      -

    • OpenAPI MCP Server

      luciVuc
      A
      license
      Not graded
      quality
      C
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      20 npm
      MIT
    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

    C2/5.0

    Scored across 36 tools

    Disambiguation3/5

    Most tools are distinct resource+action pairs (pods, endpoints, templates, volumes, registry auths), but run-endpoint vs runsync-endpoint and get-job-status vs stream-job overlap enough to cause confusion. Many tools have no descriptions, so the boundaries between similar operations are not clearly reinforced.

    Naming Consistency3/5

    The set mostly follows a lowercase hyphenated verb_noun pattern like list-pods and create-endpoint, which is predictable. However, runsync-endpoint is an awkward compound, endpoint-health breaks the verb-first pattern, and singular/plural naming is inconsistent for container registry auths.

    Tool Count2/5

    At 36 tools, this is a heavy surface that will feel overwhelming for an agent, especially with several overlapping job-related operations. It exceeds the 25+ threshold and would benefit from consolidation or clearer grouping.

    Completeness5/5

    The tool surface covers full CRUD for pods, endpoints, templates, volumes, and registry auths, plus pod lifecycle and serverless job operations. There are no obvious dead ends that would prevent a typical workflow from being completed.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources