Score Studio agent plugins

Give your agents sight.

Score Studio is the computer vision layer for agents, automating data generation, annotation, training, evaluation, workflows, and deployment in one evidence-backed system.

This repository brings that complete vision loop to the major agent ecosystems through one portable MCP server, without publishing private source identifiers or internal implementation details.

Related MCP server: production-grade-mcp-agentic-system

What an agent can do

• identify the signed-in user and organization memberships;

• inspect versioned datasets and model lineage;

• start tracked training jobs with explicit compute and dataset versions;

• list measured evaluations and read immutable reports;

• start evaluations against exact model/dataset version IDs;

• inspect and verify deployments;

• list and run typed workflows while reporting deferred blocks truthfully.

The MCP tools are intentionally narrower than the full Score Studio API. Delete, billing, member administration, provider credentials, and release switching are not exposed in the first version.

Local server

Requires Node.js 20+ and a Score Studio bearer token or API key.

npm install
npm run build
SCORESTUDIO_TOKEN=your-token npm start

The API defaults to https://api.scorestudio.ai. Set SCORESTUDIO_URL only to target another Score Studio environment.

For local Streamable HTTP development:

npm run start:http

The endpoint is http://127.0.0.1:3000/mcp; each request must include its own Authorization: Bearer … header. /healthz does not require authentication.

Container deployment

The production image listens on 0.0.0.0:3000 and uses the production Score Studio API by default; callers provide their own bearer token on each request.

docker build -t score-studio-mcp .
docker run --rm -p 3000:3000 score-studio-mcp

Packages

See distribution.md for installation, deployment, and marketplace requirements.

Cursor

Import this repository as a Cursor marketplace and install score-studio. The plugin declares SCORESTUDIO_TOKEN as a required secret variable and starts the shared MCP package through npx.

Hermes Agent

hermes skills tap add score-technologies/score-studio-agent-plugins
hermes skills install score-technologies/score-studio-agent-plugins/score-studio

Then merge plugins/hermes/score-studio/config.example.yaml into ~/.hermes/config.yaml and run hermes mcp test score-studio.

Authentication and release boundary

Local packages read SCORESTUDIO_TOKEN from the host's secret configuration and optionally accept a SCORESTUDIO_URL override. They do not persist or print secrets.

A public ChatGPT listing cannot use this manual-token flow. It requires a stable public HTTPS MCP endpoint plus OAuth 2.1 discovery/authorization. That hosted OAuth boundary is deliberately left as a release gate; the repository does not claim the package is publicly installable before it exists.

License

Apache License 2.0.