RunPod MCP Server
Related Servers
Alternatives to RunPod MCP Server
No user-submitted related servers found.
Related Servers
AlicenseCqualityAmaintenanceThis 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.368,884 npm79Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables managing RunPod compute for the Learning-to-Swim replication through natural language, including pod lifecycle, SSH/rsync file transfer, detached training jobs, and supervised runs with cost guardrails.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Hyperbolic's GPU cloud, allowing users to view available GPUs, rent instances, establish SSH connections, and run GPU-powered workloads through natural language commands.18MIT
- AlicenseNot gradedqualityBmaintenanceExposes the RunCloud v3 API to AI assistants, allowing natural language querying and management of servers with safety profiles for destructive operations.1MIT
- AlicenseDqualityDmaintenanceA 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.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Vercel's REST API through natural language. Facilitates managing deployments, projects, domains, environment variables, teams, and more.101 npmMIT
TDQS
Scored across 26 tools
Each tool targets a distinct resource and action (e.g., create-pod vs delete-pod), with no overlap. Even without descriptions, the naming makes each tool's purpose clear.
All tools follow a consistent verb_noun pattern using underscores (e.g., create-endpoint, list-pods). Verbs are limited to create, delete, get, list, update, start, stop, and nouns are the resource types.
With 26 tools covering multiple resource types (pods, endpoints, templates, network volumes, container registry auth), the count is appropriate but slightly above the typical well-scoped range.
For each resource, the standard CRUD operations (create, get, list, delete, update) are present, plus start/stop for pods. No obvious gaps in the lifecycle coverage inferred from the tool names.