Skip to main content
Glama
Niel-RunPod

RunPod MCP Server

by Niel-RunPod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to RunPod MCP Server

No user-submitted related servers found.

    Related Servers

    • RunPod MCP Server by runpod

      RunPod MCP Serverofficial

      runpod
      A
      license
      C
      quality
      A
      maintenance
      This Model Context Protocol server enables interaction with RunPod's REST API through Claude or other MCP-compatible clients, providing tools for managing pods, endpoints, templates, network volumes, and container registry authentications.
      36
      6,800 npm
      79
      Apache 2.0

    • terraform-cloud-mcp

      severity1
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that integrates Claude with the Terraform Cloud API, allowing Claude to manage your Terraform infrastructure through natural conversation.
      62
      23
      MIT

    • MCP Server Demo

      Drakoxw
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server implementation that can be run directly or through Docker, enabling AI assistants to interact with external systems through the MCP standard.
      2
      -

    • 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.
      74 npm
      -
    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

    D1.9/5.0

    Scored across 26 tools

    Disambiguation5/5

    All 26 tools have distinct names combining a unique action verb and resource noun, making each tool clearly differentiated from the others without any overlap.

    Naming Consistency5/5

    Every tool follows the consistent verb_noun pattern in snake_case, using appropriate verbs like create, delete, get, list, start, stop, and update with the same set of resource nouns.

    Tool Count2/5

    With 26 tools, the server exceeds the recommended range of 3-15 for a well-scoped set. The number feels heavy for managing five resource types, though the operations are systematic.

    Completeness4/5

    Most resources have full CRUD coverage plus start/stop for pods. The only missing operation is update for container-registry-auth, but overall the tool surface covers the core lifecycle actions well.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources