World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Read-only MCP server for Depot (depot.dev): CI failure diagnosis, build forensics, and usage.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 16/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Depot (depot.dev). Follow https://mcp.popnx.com/i/akshayjain3450-depot-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Depot (depot.dev) key (create it on the maker’s site) · 1 setting(s) to fill in (DEPOT_ORG_ID) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Depot (depot.dev) for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "depot": { "command": "npx", "args": [ "-y", "depot-mcp" ], "env": { "DEPOT_TOKEN": "your-value", "DEPOT_ORG_ID": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DEPOT_TOKEN, DEPOT_ORG_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Depot (depot.dev) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
DEPOT_ORG_ID Organization ID, sent as x-depot-org. Required only when the token can see more than one organization.Descriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"depot": {
"command": "npx",
"args": [
"-y",
"depot-mcp"
],
"env": {
"DEPOT_TOKEN": "your-value",
"DEPOT_ORG_ID": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Depot (depot.dev) and tell me what you can do for me, then show me one thing✓ If Claude says it is using Depot (depot.dev) or shows a Depot (depot.dev) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
DEPOT_PROJECT_ID Default container-build project so build tools can be called without one.DEPOT_API_URL Override the Depot API endpoint. · default https://api.depot.devDEPOT_MCP_MAX_LOG_PAGES Cap on log/step pages fetched per tool call. · default 20DEPOT_MCP_OUTPUT_BUDGET Hard character ceiling on any single tool result. · default 24000Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Depot (depot.dev) yet
Depot (depot.dev) runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Depot (depot.dev)
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Depot (depot.dev) key (create it on the maker’s site) · 1 setting(s) to fill in (DEPOT_ORG_ID) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Depot (depot.dev) for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user depot --env DEPOT_TOKEN=your-value --env DEPOT_ORG_ID=your-value -- npx -y depot-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DEPOT_TOKEN, DEPOT_ORG_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Depot (depot.dev) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
DEPOT_ORG_ID Organization ID, sent as x-depot-org. Required only when the token can see more than one organization.Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user depot --env DEPOT_TOKEN=your-value --env DEPOT_ORG_ID=your-value -- npx -y depot-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Depot (depot.dev) listed as connected
Use Depot (depot.dev) and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Depot (depot.dev) or shows a Depot (depot.dev) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
DEPOT_PROJECT_ID Default container-build project so build tools can be called without one.DEPOT_API_URL Override the Depot API endpoint. · default https://api.depot.devDEPOT_MCP_MAX_LOG_PAGES Cap on log/step pages fetched per tool call. · default 20DEPOT_MCP_OUTPUT_BUDGET Hard character ceiling on any single tool result. · default 24000Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Depot (depot.dev) key (create it on the maker’s site) · 1 setting(s) to fill in (DEPOT_ORG_ID) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Depot (depot.dev) for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "depot": { "command": "npx", "args": [ "-y", "depot-mcp" ], "env": { "DEPOT_TOKEN": "your-value", "DEPOT_ORG_ID": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DEPOT_TOKEN, DEPOT_ORG_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Depot (depot.dev) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
DEPOT_ORG_ID Organization ID, sent as x-depot-org. Required only when the token can see more than one organization.Descriptions are as written by the maker.
In the Depot (depot.dev) settings, DEPOT_TOKEN, DEPOT_ORG_ID is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Depot (depot.dev) and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Depot (depot.dev) or shows a Depot (depot.dev) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
DEPOT_PROJECT_ID Default container-build project so build tools can be called without one.DEPOT_API_URL Override the Depot API endpoint. · default https://api.depot.devDEPOT_MCP_MAX_LOG_PAGES Cap on log/step pages fetched per tool call. · default 20DEPOT_MCP_OUTPUT_BUDGET Hard character ceiling on any single tool result. · default 24000Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Depot (depot.dev) key (create it on the maker’s site) · 1 setting(s) to fill in (DEPOT_ORG_ID) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Depot (depot.dev) for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "depot": { "type": "stdio", "command": "npx", "args": [ "-y", "depot-mcp" ], "env": { "DEPOT_TOKEN": "your-value", "DEPOT_ORG_ID": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For DEPOT_TOKEN, DEPOT_ORG_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Depot (depot.dev) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
DEPOT_ORG_ID Organization ID, sent as x-depot-org. Required only when the token can see more than one organization.Descriptions are as written by the maker.
In the Depot (depot.dev) settings, DEPOT_TOKEN, DEPOT_ORG_ID is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Depot (depot.dev) and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Depot (depot.dev) or shows a Depot (depot.dev) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
DEPOT_PROJECT_ID Default container-build project so build tools can be called without one.DEPOT_API_URL Override the Depot API endpoint. · default https://api.depot.devDEPOT_MCP_MAX_LOG_PAGES Cap on log/step pages fetched per tool call. · default 20DEPOT_MCP_OUTPUT_BUDGET Hard character ceiling on any single tool result. · default 24000Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user depot --env DEPOT_TOKEN=your-value --env DEPOT_ORG_ID=your-value -- npx -y depot-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"depot": {
"command": "npx",
"args": [
"-y",
"depot-mcp"
],
"env": {
"DEPOT_TOKEN": "your-value",
"DEPOT_ORG_ID": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"depot": {
"command": "npx",
"args": [
"-y",
"depot-mcp"
],
"env": {
"DEPOT_TOKEN": "your-value",
"DEPOT_ORG_ID": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"depot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"depot-mcp"
],
"env": {
"DEPOT_TOKEN": "your-value",
"DEPOT_ORG_ID": "your-value"
}
}
}
}DEPOT_TOKEN secret required envDEPOT_ORG_ID required envDEPOT_PROJECT_ID envDEPOT_API_URL envDEPOT_MCP_MAX_LOG_PAGES envDEPOT_MCP_OUTPUT_BUDGET envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: depot-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account akshayjain3450, which owns the repo
Code last changed 19 days ago
GitHub could not identify the licence type; open the file to check
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for depot-mcp@0.2.1
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/akshayjain3450-depot-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DEPOT_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 19 days ago, and the latest version (0.2.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Depot (depot.dev) | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | NOASSERTION | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol server, read-only by default, for [Depot](https://depot.dev), the container build and CI acceleration service. It gives a coding agent Depot's own answer to "why did CI fail?" and "why did this build fail?", plus the run history, cache effectiveness, registry contents, CI configuration, and usage data behind those answers.
Community project. Not affiliated with, endorsed by, or supported by Depot. Source-available under Apache 2.0 with the Commons Clause; see License.
Not to be confused with: The Home Depot, Chromium's depot_tools, Steam depots, Perforce depots, or any other "depot". This server talks only to api.depot.dev.
Depot ships a good agent story already, but it is not MCP. Depot's answer is Agent Skills: SKILL.md files that teach an agent to drive the depot CLI, plus a documented CI API and llms.txt. Depot's own post announcing Skills notes two limitations: skills work best in clients that implement the SKILL.md convention, and they are "sometimes notorious for not being automatically used by agents."
This server covers the gaps that leaves:
depot binary on the machine. A tool call does not.depot ci rerun. This server can, and does; see Read-only model and security.The flagship tool is a thin, careful wrapper around something Depot already built: GetFailureDiagnosis, a server-side failure analysis that clusters a run's failures by root cause and returns a diagnosis, a suggested fix, and the evidence lines, already bounded so it fits in a context window. Most of this server's value is exposing that well.
| Depot Agent Skills | depot-mcp | |
|---|---|---|
Needs the depot CLI installed and logged in | yes | no |
Works in clients without SKILL.md support | no | yes |
| Invocation | agent must retrieve the skill | tool is listed in tools/list |
| Can mutate Depot (rerun, cancel, reset) | yes, anything the CLI can | off by default; opt-in write tools behind DEPOT_MCP_ALLOW_WRITES, each dry-run first; deletion behind a second flag; no reset |
| Output bounded for a context window | depends on the CLI command | every tool |
| Maintained by | Depot | community |
As of 2026-09-05 no standalone Depot MCP server exists (first-party or otherwise, in the official registry, on npm, or on PyPI), and Depot's own guidance for agents without a shell is to call the CI API directly. This server is that API call, shaped for an agent.
DEPOT_MCP_ALLOW_WRITES unset, no tool that can change anything is registered. Setting it adds ten write tools, every one of which dry-runs first and refuses unsafe requests before any write: cancel run or workflow, cancel job, retry failed jobs, retry one job, rerun workflow, dispatch workflow (optionally limited by DEPOT_MCP_DISPATCH_ALLOWLIST), set or delete a CI variable, create project, update project; see Write tools. Stopping or killing a sandbox needs the beta flag as well, and deleting a project needs DEPOT_MCP_ALLOW_DESTRUCTIVE on top; see Destructive writes. There is no reset, secret-writing, or token-minting tool.DEPOT_MCP_ENABLE_BETA=1 adds read-only tools for Depot sandboxes (depot.sandbox.v1) and the Depot registry (depot.registry.v1beta1). Those APIs are published only as protos, one of them beta in its name, so the tools stay hidden unless you ask for them; see Beta.npm run verify:apply), including dispatch, project update, and project delete. Sandbox stop and kill are covered by the verification script but have only been dry-run, because the trial organization had no sandbox to stop.@modelcontextprotocol/sdk 1.x line, which speaks 2025-11-25. The current spec revision is 2026-07-28, implemented by the v2 packages (@modelcontextprotocol/server 2.0.0, published 2026-07-28), which also serve 2025-11-25 clients. Every current client negotiates 2025-11-25, so nothing is lost today. Moving to v2 is a planned, contained change: the SDK is imported in nine files and the transport wiring lives in src/index.ts.node --version). The Docker image needs no Node on the host.depot login also works but spans every organization you belong to, so set DEPOT_ORG_ID too.Depot has three kinds of token and they are not interchangeable. Verified live on 2026-09-06, including with a user token belonging to an organization owner:
| Tool group | Organization token | User token |
|---|---|---|
depot_whoami | yes | yes |
Depot CI: depot_diagnose_ci_failure, depot_list_ci_runs, depot_get_ci_run, depot_get_ci_job, depot_get_ci_attempt, depot_list_ci_workflows, depot_get_ci_workflow, depot_wait_for_ci_run, depot_get_ci_logs, depot_get_ci_job_summary, depot_get_ci_metrics, depot_list_ci_artifacts, depot_get_ci_artifact_url, depot_compare_ci_runs | yes | yes |
depot_list_ci_secrets, depot_list_ci_variables | yes | admins and owners only |
depot_list_images | yes | yes |
depot_list_projects, depot_get_project, depot_audit_trust_policies, depot_list_project_tokens, depot_list_builds, depot_get_build, depot_diagnose_build, depot_get_usage, depot_list_project_usage, depot_get_cache_summary | yes | no: Depot answers 401 Invalid token, whatever the user's role |
Beta: depot_list_sandboxes, depot_get_sandbox, depot_list_registry_repositories, depot_get_registry_image | yes | not tested yet |
| Project token | runs nothing |
The full matrix, per tool and per Depot service, with how to obtain each token, is in docs/tokens.md. depot_whoami reports which kind it holds and names the tools that will not work.
Create a dedicated token for this server so you can revoke it independently. Depot has no read-only token scope; read the security section before you paste one anywhere.
Every client below runs the same command over stdio. The only things that vary are the file the config lives in and how that client lets you keep the token out of the file.
The generic config, which works as-is in Claude Desktop, Cursor, Windsurf, Cline, JetBrains, and most other clients:
{
"mcpServers": { "depot": { "command": "npx", "args": ["-y", "depot-mcp"], "env": { "DEPOT_TOKEN": "YOUR_DEPOT_TOKEN" } } } }
Add "DEPOT_ORG_ID": "..." to env if your token can see more than one organization. Every tool is prefixed depot_, and tool names are stable across releases.
claude mcp add depot --scope user --env DEPOT_TOKEN=YOUR_DEPOT_TOKEN -- npx -y depot-mcp
Or commit a .mcp.json at the repository root so the whole team gets it. Claude Code expands ${VAR} and ${VAR:-default} in command, args, env, url, and headers, so the token stays in each developer's shell environment and out of git. Copy .mcp.json.example:
{
"mcpServers": { "depot": { "type": "stdio", "command": "npx", "args": ["-y", "depot-mcp"], "env": { "DEPOT_TOKEN": "${DEPOT_TOKEN}", "DEPOT_ORG_ID": "${DEPOT_ORG_ID:-}" } } } }
Claude Code prompts on every MCP tool call regardless of readOnlyHint. To stop being asked, allow the read-only tools in .claude/settings.json: "permissions": { "allow": ["mcp__depot__*"] }.
Two options.
Extension bundle (one click). Download depot-mcp.mcpb from the releases page, open it with Claude Desktop (or Settings, Extensions, Advanced settings, Install extension), and paste the token into the settings form. The token field is marked sensitive in manifest.json, so Claude Desktop stores it in the OS keychain rather than in a JSON file.
Manual JSON. Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows and add the generic config above.
The button pre-fills the server; fill in DEPOT_TOKEN when Cursor shows the config. Or edit ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor resolves ${env:NAME} in command, args, env, url, and headers, so a committed project file can read the token from the environment:
{
"mcpServers": { "depot": { "command": "npx", "args": ["-y", "depot-mcp"], "env": { "DEPOT_TOKEN": "${env:DEPOT_TOKEN}" } } } }
[](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522depot%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522depot-mcp%2522%255D%252C%2522env%2522%253A%257B%2522DEPOT_TOKEN%2522%253A%2522%2524%257Binput%253Adepot-t