Skip to main content
Glama
score-technologies

score-studio-mcp

Official
README.md
# 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.

## 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.

```bash
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:

```bash
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.

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

## Packages

| Host | Package | Discovery route |
| --- | --- | --- |
| ChatGPT + Codex | `plugins/openai/score-studio` | OpenAI universal plugin directory |
| Claude Code | `plugins/claude/score-studio` | Anthropic marketplace or this repo's marketplace |
| Gemini CLI | `plugins/gemini/score-studio` | Git install and Gemini extension gallery |
| Cursor | `plugins/cursor/score-studio` | This repository's Cursor marketplace; standalone marketplace repo remains supported |
| Hermes Agent | `skills/score-studio` + `plugins/hermes/score-studio` | Hermes GitHub skill tap plus native MCP client |
| Lovable | Shared remote MCP endpoint | Custom chat connector; no equivalent public plugin submission flow yet |
| GitHub Copilot / VS Code | Shared local or remote MCP endpoint | Manual MCP config, then GitHub MCP Registry when eligible |
| Windsurf | Shared local or remote MCP endpoint | MCP Marketplace submission or manual Cascade config |
| Other MCP hosts | Shared remote MCP endpoint | Streamable HTTP `/mcp` |

See [distribution.md](docs/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

```bash
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`](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.

TDQS

A3.5/5.0

Scored across 12 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues