A
licenseA
qualityC
maintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.
13
Apache 2.0
meshive-mcp
Officialby meshive
Related Servers
Alternatives to meshive-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to manage and orchestrate autonomous agents, budgets, and multi-agent workflows within the OpenMesha agentic operating system.91Apache 2.0
- AlicenseBqualityCmaintenanceEnables MCP-compatible clients to manage AI agent teams, including agents, Kanban issues, projects, goals, approvals, budgets, and raw API access.30MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables agents to administer a self-hosted AI control plane for users, organizations, subscriptions, API keys, model providers, and service health, with local-first model routing and cloud failover.Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI agents to submit GPU job requests, select eligible workers, track execution, and retrieve results via MCP.1421MIT
- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
TDQS
A3.9/5.0
Scored across 44 tools
Disambiguation4/5
Most tools map cleanly to distinct resources and actions (pods vs storages vs servings vs tasks vs assets), and the estimate_/create_ and preview/confirm pattern is explicitly documented. A few potential overlaps exist (operation_status vs transactions, watched_folders vs set_watched_folders, and the many list tools), but the descriptions clearly distinguish read vs write and preview vs confirm.
Naming Consistency4/5
There is a recognizable convention: bare nouns (pods, storages, templates, tasks, assets) for list/get readers and verb_noun (create_pod, delete_storage, deploy_serving, submit_task, set_watched_folders) for mutations. Minor deviations like detect_model, download_links, and account break the pattern slightly, but consistency is high.
Tool Count3/5
44 tools is heavy, well beyond the 3-15 sweet spot, though the server covers a broad GPU-cloud platform (pods, storage, serverless serving, tasks, assets, billing, hosting). Each tool generally earns its place, but the surface is large enough to feel borderline for agent navigation.
Completeness4/5
Coverage is strong: full lifecycle for pods, storages, models, servings, and tasks, plus reads, logs, billing, and diagnostics. Minor gaps exist (no update for account/workspace metadata, limited non-scale serving edits), but core workflows are covered without dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues