codabench-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODABENCH_BASE_URL | No | Override for tests | https://www.codabench.org |
| CODABENCH_API_TOKEN | Yes | DRF token, sent as Authorization: Token <token> | |
| CODABENCH_ALLOW_WRITE_RAW | No | Set to 1 to allow non-GET methods through codabench_request | 0 |
| CODABENCH_MAX_DOWNLOAD_BYTES | No | Cap for download_dataset | 5368709120 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_competitionsC | Search public Codabench competitions. Auto-paginates up to max_pages. |
| get_competitionB | Get full details of a single Codabench competition. |
| list_competition_phasesC | List all phases of a Codabench competition. |
| get_phaseC | Get full details of a single phase. |
| get_competition_rulesA | Get a competition's rules, terms, evaluation criteria, and any other descriptive pages concatenated into a single markdown string. |
| list_competition_tasksC | List all tasks attached to a Codabench competition. |
| get_taskB | Get full details of a single task, including dataset keys. |
| get_leaderboardC | Get the leaderboard for a phase. |
| get_my_profileA | Get the authenticated user's Codabench profile. |
| download_datasetA | Download a Codabench dataset/bundle to a local absolute path. Streams directly to disk and returns the SHA-256. Refuses to overwrite unless overwrite=True. |
| list_my_submissionsB | List the authenticated user's submissions, newest first. |
| get_submissionC | Get full details of a submission including scores. |
| get_submission_logsC | Get stdout/stderr/ingestion logs for a submission. |
| submit_to_phaseB | Submit a zipped model bundle to a competition phase. Performs Codabench's 3-step upload: POST /api/data/, PUT to signed URL, PUT /api/data/upload_completed/, POST /api/submissions/. |
| poll_submissionA | Poll a submission until it reaches a terminal state (finished/failed/cancelled) or |
| codabench_requestA | Generic Codabench REST escape hatch. Use when no curated tool fits. Path must start with '/api/'. By default only GET/HEAD/OPTIONS are allowed; start the server with CODABENCH_ALLOW_WRITE_RAW=1 to permit POST/PUT/PATCH/DELETE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct resource or action (competitions, phases, tasks, submissions, datasets, profile), and the generic escape hatch is clearly marked for edge cases. No two tools overlap in purpose.
Most tools follow a consistent verb_noun pattern (e.g., 'get_competition', 'list_phase', 'submit_to_phase'). The only outlier is 'codabench_request', which uses a different convention, but it's a single exception.
16 tools are well-scoped for a Codabench API wrapper, covering all common participant operations without being excessive. Each tool addresses a specific need.
The tool set covers the full participant workflow (browsing competitions, submitting, polling, downloading datasets, checking leaderboards) and includes a generic escape hatch for missing operations. Minor administrative actions (e.g., managing teams) are absent but not core to the domain.