score-studio-mcp
OfficialRelated Servers
Alternatives to score-studio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.64MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT

AgentMark MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceMCP server for AgentMark. Exposes the full AgentMark API to AI editors: list traces and spans, manage datasets, write scores, run experiments, manage apps, deployments, environments, and annotation queues.352AGPL 3.0- AlicenseAqualityAmaintenanceMCP server that gives agents the same interface as dashAI's GUI: explore datasets, list models, train, track jobs, and read metrics.1024 PyPIMIT
- AlicenseBqualityBmaintenanceMCP server that initializes, manages, and operates traceable agentic infrastructure across your digital ecosystem, serving as a control plane to know project states, health, and initialize missing setups.371MIT

picsellia-mcpofficial
FlicenseNot gradedqualityDmaintenanceMCP server that wraps the Picsellia Python SDK, giving AI assistants access to computer vision platform capabilities such as datasets, experiments, models, deployments, and monitoring.-
TDQS
Scored across 12 tools
Each tool targets a distinct resource or action: auth, workflows, datasets, models, training, evaluations, and deployments. The similar-looking start/run tools are clearly separated by their object types.
Tools consistently use the scorestudio_ prefix with snake_case verb_noun names. Minor deviations like whoami and run_workflow vs start_training are easy to predict but not perfectly uniform.
With 12 tools, the server is well-scoped for an MLOps platform covering auth, workflows, datasets, models, training, evaluations, and deployments. Each tool has a clear purpose and none feel redundant.
Core read and start operations are present, but there are gaps: models only support listing, training jobs cannot be fetched after starting, and deployment management is limited to listing and verification. Agents may hit dead ends when trying to check training results or detailed model state.