depot-mcp

Overview Schema Source Related Servers Discussions Admin

Check the Depot token and its visible scope

depot_whoami

Read-onlyIdempotent

Verify the configured Depot token and list accessible organizations and projects. Use this first when other Depot tools return empty results or permission errors to diagnose token scope.

Instructions

Verify the configured Depot token and report which organizations and projects it can actually see.

Call this first whenever another Depot tool returns an empty list or a permission error. Depot's most common confusing failure is a token that spans several organizations with none selected: requests then resolve against the wrong organization and return empty results rather than an error. This tool says plainly whether that is happening and what to set.

Also reports whether write tools are enabled (DEPOT_MCP_ALLOW_WRITES) and which mutating tools are registered, whether the destructive gate is open (DEPOT_MCP_ALLOW_DESTRUCTIVE, which adds depot_delete_project only when writes are on too), and whether the beta sandbox and registry tools are registered (DEPOT_MCP_ENABLE_BETA). With the write flag unset no mutating tool exists, and nothing here can retry, cancel, rerun, or delete anything.

Never returns the token or any part of it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`apiUrl`	Yes
`failures`	Yes
`projects`	Yes
`warnings`	Yes
`betaTools`	Yes
`tokenKind`	Yes
`activeOrgId`	No
`betaEnabled`	Yes
`tokenSource`	Yes
`orgSelection`	Yes
`projectCount`	No
`mutatingTools`	Yes
`organizations`	Yes
`writesEnabled`	Yes
`destructiveTools`	Yes
`destructiveEnabled`	Yes
`mutatingToolsAvailable`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.2.1Sep 8, 2026

addedOutput schema / properties / betaEnabled
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / betaTools

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / destructiveEnabled
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / destructiveTools

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / mutatingTools

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / mutatingToolsAvailable / const
```
Removed value: -0
```

addedOutput schema / properties / tokenKind

Added value: +{
+  "enum": [
+    "organization",
+    "user",
+    "unknown"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "apiUrl",
-  "tokenSource",
-  "organizations",
-  "orgSelection",
-  "projects",
-  "writesEnabled",
-  "mutatingToolsAvailable",
-  "warnings",
-  "failures"
-]New value: +[
+  "apiUrl",
+  "tokenSource",
+  "tokenKind",
+  "organizations",
+  "orgSelection",
+  "projects",
+  "writesEnabled",
+  "destructiveEnabled",
+  "betaEnabled",
+  "betaTools",
+  "mutatingToolsAvailable",
+  "mutatingTools",
+  "destructiveTools",
+  "warnings",
+  "failures"
+]

First observedv0.1.0Sep 5, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes beyond the readOnlyHint and idempotentHint annotations by explicitly stating it never returns the token or any part of it, and details the conditions under which write, destructive, beta, and registry tools are registered. This provides strong behavioral transparency with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary purpose and then expands into relevant behavioral details. While somewhat lengthy, each sentence adds meaningful context about capabilities, limitations, and environment flags, so the structure is reasonably tight and purposeful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and an output schema, the description fully explains what the tool checks, what it reports, and what it will never return. It also covers environmental dependencies and relationships to sibling tools, making it complete for an agent to know when and how to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the input schema is empty, so there are no parameter semantics to explain. The description still adds useful context about what the tool inspects and reports, making the parameter dimension non-issue and slightly above the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool verifies the configured Depot token and reports which organizations and projects it can see, using specific verbs like 'verify' and 'report.' This distinguishes it from sibling tools that focus on CI runs, builds, images, or usage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to call this tool first when another Depot tool returns an empty list or permission error, and explains the common token scoping failure. It also provides guidance about when mutating tools are absent and what the tool cannot do, giving clear actionable direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.