# depot-mcp

Read-only MCP server for Depot (depot.dev): CI failure diagnosis, build forensics, and usage.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.2.1
- **Author:** io.github.akshayjain3450
- **License:** Unknown
- **npm:** depot-mcp
- **Source:** https://github.com/akshayjain3450/depot-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 25 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-09T14:32:21.913Z
- **Version scanned:** 0.2.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `depot_audit_trust_policies`
- `depot_list_project_tokens`
- `depot_diagnose_build`
- `depot_get_build`
- `depot_list_builds`
- `depot_get_cache_summary`
- `depot_list_ci_artifacts`
- `depot_get_ci_artifact_url`
- `depot_compare_ci_runs`
- `depot_list_ci_secrets`
- `depot_list_ci_variables`
- `depot_diagnose_ci_failure`
- `depot_dispatch_ci_workflow`
- `depot_get_ci_job`
- `depot_get_ci_attempt`
- `depot_get_ci_logs`
- `depot_get_ci_metrics`
- `depot_list_ci_runs`
- `depot_get_ci_run` — Show one Depot CI run as its workflow -> job -> attempt tree, with the status of every node and the ids needed to drill in. Use this to see the shape of a run: 
- `depot_get_ci_job_summary`
- `depot_set_ci_variable`
- `depot_delete_ci_variable`
- `depot_wait_for_ci_run`
- `depot_list_ci_workflows`
- `depot_get_ci_workflow`
- `depot_cancel_ci_run`
- `depot_cancel_ci_job` — Cancel a single queued or running Depot CI job (CancelJob), leaving the rest of its workflow and run untouched. Use this for one stuck or pointless job, for exa
- `depot_retry_ci_failed_jobs`
- `depot_retry_ci_job`
- `depot_rerun_ci_workflow`
- `depot_update_project`
- `depot_delete_project`
- `depot_create_project`
- `depot_list_projects` — List Depot container build projects with their region, runner hardware, and cache policy. Use this to find a projectId for depot_list_builds, depot_diagnose_bui
- `depot_get_project`
- `depot_list_registry_repositories`
- `depot_get_registry_image`
- `depot_list_images`
- `depot_stop_sandbox`
- `depot_kill_sandbox`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"depot\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"depot-mcp\"\n      ],\n      \"env\": {\n        \"DEPOT_TOKEN\": \"<YOUR_DEPOT_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `DEPOT_TOKEN` — Depot Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 54, ceiling 54 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/depot-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/depot-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/depot-mcp
- HTML page: https://forgeregistry.com/registry/depot-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.