Run:AI MCP Server
Related Servers
Alternatives to Run:AI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to consume 50+ NVIDIA NIM models including LLMs, image generation, and vision through 10 MCP tools with rich metadata and advanced filtering.11189 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.174Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.6 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to retrieve live GPU rental prices, compare models, and access market summaries and historical price data through four read-only MCP tools.4MIT
- AlicenseBqualityBmaintenanceEnables AI agents to submit GPU job requests, select eligible workers, track execution, and retrieve results via MCP.1421MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to drive a self-hosted video toolkit through MCP tools, including lipsync, face restoration, ffmpeg operations, and metadata retrieval.1Do What The F*ck You Want To Public
TDQS
Scored across 4 tools
Each tool has a distinct responsibility: searching the API spec, executing API calls, resolving names to IDs, and running CLI-only operations. There is no overlap; dependencies like 'search before call' are explicitly documented.
All tool names follow a consistent verb_runai_noun pattern with snake_case: search_runai_api_spec, call_runai_api, resolve_runai_names, execute_runai_cli. The naming is uniform and predictable.
With only 4 tools, the server covers an enormous API surface by using a meta-design (search + call + resolve + CLI). Each tool is essential and well-scoped, avoiding redundancy.
The toolset provides comprehensive coverage: search_runai_api_spec exposes every API endpoint, call_runai_api executes them, resolve_runai_names bridges user-friendly names to API IDs, and execute_runai_cli handles operations impossible via API (port-forward, exec, logs). No obvious gaps.