Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Inspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://depot.usefulapi.io/mcpEjecuta esto en tu terminal
claude mcp add --transport http depot https://depot.usefulapi.io/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"depot": {
"url": "https://depot.usefulapi.io/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"depot": {
"type": "http",
"url": "https://depot.usefulapi.io/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://depot.usefulapi.io/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
depot_list_projectsList the organization's Depot projects. A project is an isolated container-build cache (region, hardware, cache policy). Use the returned projectId with the build and registry tools. Depot: ProjectService/ListProjects.
depot_get_projectGet one Depot project — name, region, hardware size, cache policy, build timeout and autoscaling. Depot: ProjectService/GetProject.
depot_list_buildsList container builds in a project, newest first: status (STATUS_RUNNING / FAILED / SUCCESS / ERROR / CANCELED), timestamps, build duration, time saved by cache, and cached vs total steps. Depot: core BuildService/ListBuilds.
depot_get_buildGet one container build's status, timestamps, duration, time saved and cached/total step counts. Depot: core BuildService/GetBuild.
depot_get_build_stepsList the BuildKit steps of a container build: name, digest, start/end time, cache state (CACHED / UNCACHED), any error, and whether it has logs. Find the failing step here, then pass its digest to depot_get_build_step_logs. Depot: build.v1 BuildService/GetBuildSteps.
depot_get_build_step_logsGet the log lines (message + timestamp) of one container-build step, identified by its digest from depot_get_build_steps. Depot: build.v1 BuildService/GetBuildStepLogs.
depot_list_registry_imagesList the images stored in a project's Depot Registry: tag, digest, pushedAt and sizeBytes. Depot: build.v1 RegistryService/ListImages.
depot_get_usageGet the organization's Depot usage over a window: container builds per project (build count, minutes saved, minutes billed), GitHub Actions jobs per repo/workflow/runner (minutes elapsed and billed), storage, and agent sandboxes. Depot: UsageService/GetUsage.
depot_ci_list_runsList Depot CI runs, newest first. Filter by status (default: running + queued — pass ["failed"] to find failures), repo, commit SHA prefix, trigger event, or pull request number (requires repo). Depot: CIService/ListRuns.
depot_ci_get_run_statusGet a Depot CI run's status with its nested workflows, jobs and attempts (ids, keys, statuses, error messages). This is how to find the workflowId / jobId / attemptId for the log, diagnosis and retry tools. Depot: CIService/GetRunStatus.
depot_ci_list_workflowsList Depot CI workflows across runs, newest first, with per-status job counts. Filter by name/path text, repo, status, trigger, SHA prefix or PR number. Depot: CIService/ListWorkflows.
depot_ci_get_jobGet one Depot CI job: status, conclusion, error message, timestamps, runner config (labels, image, CPUs, memory), matrix values, parent run/workflow context, dependencies and attempt history. Depot: CIService/GetJob.
depot_ci_get_job_logsGet persisted log lines for a Depot CI job attempt, oldest first (step key/name, timestamp, line number, body). Pass job_id to read the job's latest attempt, or attempt_id for a specific one — exactly one. Pass nextPageToken back as page_token for more lines. Depot: CIService/Get
depot_ci_get_failure_diagnosisGet Depot's failure diagnosis for a CI run, workflow, job or attempt. For runs and workflows, identical failures are grouped by error fingerprint; for a job or attempt it is a focused diagnosis with evidence. Empty when no failure evidence is found. The best first call when a run
depot_gha_list_jobsList GitHub Actions jobs that ran on Depot-managed runners, newest first: status, conclusion, runner label, requested CPU/memory, duration, billable time and GitHub URL. Defaults to the last 30 days (max window 90 days). Depot: GithubActionsService/ListGithubActionsJobs.
depot_gha_search_logsSearch GitHub Actions log lines from Depot runners, newest match first (job, workflow, step, timestamp, body, lineId). Defaults to the last hour (max window 30 days). Filter by repository, workflow, runner label, action or compute id. Depot: GithubActionsService/SearchGithubActio
depot_gha_get_analyticsGet time-bucketed GitHub Actions analytics for Depot runners: job counts (successful/failed/cancelled), failure rate, elapsed and billable seconds, average duration — as totals plus hourly or daily buckets. Defaults to the last 30 days (max 90). Depot: GithubActionsService/GetGit
depot_gha_list_recommendationsList Depot's runner-size recommendations from job CPU and memory metrics: SIZE_UP when average CPU or memory reaches 90%, SIZE_DOWN when both averages stay ≤30% and peaks ≤70%, with current vs suggested size and per-minute price. Defaults to the last 30 days. Depot: GithubActions
depot_cache_list_entriesList Depot Cache entries of one type, optionally by key prefix: key, size in bytes, name and creation time (Depot returns no last-access time and no repository). Retention and size limits are set only in the dashboard (Organization Settings), not through the API. Depot: CacheServ
depot_cache_delete_entriesWRITE — deletes cached build data; a later build rebuilds it. Delete Depot Cache entries by exact key. Without confirm it only previews: it shows which keys exist, with their size, and deletes nothing. Show the preview to the user, then call again with confirm: true. Depot: Cache
depot_create_projectWRITE. Create a Depot container-build project (an isolated build cache). Idempotent by name: if an active project with the same name exists, that project is returned. Defaults: cache 50 GB / 14 days, hardware HARDWARE_16X32 on AWS builders. Depot: ProjectService/CreateProject.
depot_ci_retry_jobWRITE — starts compute. Retry one failed or cancelled Depot CI job, plus any skipped jobs that depend on it. Fails if a dependent job already started; use depot_ci_retry_failed_jobs then. Depot: CIService/RetryJob.
depot_ci_retry_failed_jobsWRITE — starts compute. Retry only the failed and cancelled jobs in a Depot CI workflow, plus skipped jobs that depend on them. Jobs that succeeded are left alone. Depot: CIService/RetryFailedJobs.
depot_ci_cancel_runWRITE — stops work in progress. Cancel a queued or running Depot CI run and all of its unfinished workflows, jobs and attempts. Cancelled jobs can be retried afterwards with depot_ci_retry_failed_jobs. Depot: CIService/CancelRun.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con el dominio usefulapi.io (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 387 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 24 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.36.3) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, LickityClick
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Use Depot from Claude, Cursor, or any MCP client — inspect projects, container builds, build steps and logs, Depot CI runs and jobs, and GitHub Actions runner usage, and retry or cancel CI work. Hosted, no local install: connect with your own Depot credentials.
Live endpoint: https://depot.usefulapi.io/mcp · Homepage: https://usefulapi.io/depot
https://depot.usefulapi.io/mcp.claude mcp add --transport http depot https://depot.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "depot": { "url": "https://depot.usefulapi.io/mcp" } } }
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Depot credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/depot/
On first connect you'll provide your Depot organization API token (Organization Settings → API Tokens). They're validated, stored per-user, and scoped to you — no keys in config files.
| Tool | Type | What it does |
|---|---|---|
depot_list_projects | read | List projects |
depot_get_project | read | Get a project |
depot_list_builds | read | List builds for a project |
depot_get_build | read | Get a build |
depot_get_build_steps | read | List a build's steps |
depot_get_build_step_logs | read | Get a build step's logs |
depot_list_registry_images | read | List registry images |
depot_get_usage | read | Get organization usage |
depot_ci_list_runs | read | List Depot CI runs |
depot_ci_get_run_status | read | Get a CI run's status tree |
depot_ci_list_workflows | read | List Depot CI workflows |
depot_ci_get_job | read | Get a CI job |
depot_ci_get_job_logs | read | Get a CI job's logs |
depot_ci_get_failure_diagnosis | read | Diagnose a CI failure |
depot_gha_list_jobs | read | List GitHub Actions jobs on Depot runners |
depot_gha_search_logs | read | Search GitHub Actions logs |
depot_gha_get_analytics | read | Get GitHub Actions analytics |
depot_gha_list_recommendations | read | List runner-size recommendations |
depot_cache_list_entries | read | List cache entries |
depot_cache_delete_entries | write | Delete cache entries |
depot_create_project | write | Create a project |
depot_ci_retry_job | write | Retry a CI job |
depot_ci_retry_failed_jobs | write | Retry a workflow's failed jobs |
depot_ci_cancel_run | write | Cancel a CI run |
depot_usage_status | meta | Usage status (free-tier meter) |
depot_request_feature | meta | Request a missing feature |
depot_upgrade | meta | Upgrade to Pro or Pro+ |
depot_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this server only. Subscribe with depot_upgrade (it returns a Stripe Checkout link). Cancel any time with depot_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running depot_upgrade before then undoes the cancel. Or write to support@usefulapi.io.
MIT © usefulapi. Not affiliated with or endorsed by Depot.