Msty Admin MCP
Related Servers
Alternatives to Msty Admin MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceUnified MCP server with 46 tools for AI expert consultations, memory service integration (semantic search, knowledge graphs), workflow automation, and code sandboxing.MIT
- AlicenseBqualityDmaintenanceComprehensive MCP server for Google Stitch with 36 tools covering design-to-code workflows, including screen generation, code extraction, design analysis, and project management.44152 npm5MIT
- FlicenseNot gradedqualityDmaintenanceA production-grade MCP server with 6 sandboxed tools and an agent orchestration engine for autonomous task completion, featuring an evaluation suite with CI/CD quality gates.-
- FlicenseCqualityDmaintenanceComprehensive MCP server for managing all IBM Cloud services, offering 180+ tools across 16 domains to enable AI assistants to fully manage IBM Cloud infrastructure.1002-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that establishes feedback-oriented development workflows with a Web UI and desktop app, allowing users to provide interactive feedback to AI models through prompts, images, and session tracking.-
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP server for intelligent task management with 0-100 evaluation scoring, session-based workflow tracking, and real-time status monitoring for AI assistants.2 npm3MIT
TDQS
Scored across 56 tools
Many tools target distinct resources (Bloom evaluations, Studio entities, model services, Nexus), but several clusters overlap: get_service_status vs analyse_msty_health vs get_server_status, multiple chat_with_*_model variants, and multiple list_*_models tools. Descriptions help, but boundaries remain fuzzy for status/health and model-selection tasks.
Names are predominantly snake_case with verb_noun or verb_entity order, and spelling is consistently British (analyse, optimise). Minor deviations exist: bloom_* prefixes some Bloom tools, and retrieval verbs vary across get, read, and query.
With 56 tools, the set is far beyond the typical 3-15 well-scoped range. The breadth includes many niche, overlapping, and read-only inspection tools, making the surface difficult for an agent to navigate efficiently.
The server covers a wide read-only surface: installation health, databases, services, models, Bloom evaluations, Studio entities, migrations, and Nexus. However, mutation operations (create/update/delete) are largely absent for Studio entities, and import/sync tools only validate or report rather than perform changes, creating admin dead ends.