Publish from a coding agent (MCP)

Depot has a hosted MCP server, so a coding agent can do what you'd do with the CLI and dashboard: find or create the game, put an uploaded build on a channel, publish the store page, issue tester keys and hand you the link.

ConnectCopy Anchor Link

Add a remote MCP server with the URL https://mcp.depot.games/mcp in your client's MCP settings. For Claude Code:

claude mcp add --transport http depot https://mcp.depot.games/mcp

The first time the agent uses it, your browser opens Depot's sign-in:

1. Sign in with your Depot account (in the browser, never in the chat).
2. Choose a studio. A connection acts in exactly one studio. In two studios? Connect twice.
3. Approve what the agent may do there. You see each permission in plain words.

The agent never sees your password, and it never gets more than your own role in the studio allows. Revoke access by removing the connection in your client; removing someone from the studio cuts their agent off at once.

What the agent can doCopy Anchor Link

depot_get_share_link and depot_get_game also say whether a game is for sale through Depot, at what price, and why not if a price is set but buyers can't pay (sales turned off, Stripe account not ready). Agents can read that but not change it.

Not available to agents: members, invitations, API keys, connecting Stripe, prices, turning sales on or off, refunds, deleting anything. Use the dashboard for those.

Uploading the buildCopy Anchor Link

The MCP server runs in the cloud and can't read your files. The agent uploads with the Depot CLI in your terminal, then publishes over MCP. depot_prepare_publish gives it the exact commands:

depot login --api https://api.depot.games
depot keys generate && depot keys enroll --game my-game   # first push from a machine
depot push --game my-game --platform macos-arm64 --release 1.0.0 --input build/ --launch-file launch.json

Then depot_publish_build checks the upload finished, moves the channel (only if nobody moved it since the agent looked), optionally publishes the store page, and returns the share link.

Safety railsCopy Anchor Link

• Unlisted by default. Store pages are published unlisted unless you ask for public.
• Confirmations. Moving the stable channel, making a page public, changing a game's address, rolling back, and revoking keys or access all need the agent to ask you first and pass confirm: true.
• No raw links. The share link is the game's store page; players get the game through Depot with the access you chose (buying it, a free claim, a key or an invitation).
• Stale changes are refused. Moving or rolling back a channel names the revision the agent last saw. If someone moved it since, the call fails with revision_mismatch and nothing changes; the agent re-reads and asks you.
• Retries are safe. Issuing keys and granting access take an idempotency key: a retry returns the first result (the same batch, without showing its codes again; the same grant) instead of doing it twice. Granting to someone who already owns the game reports already_owned and leaves their access as it is.
• Keys stay private. Codes appear once in the result; listing batches never shows codes.
• Text is data. Game descriptions and notes in results are treated as data, not instructions.

Try itCopy Anchor Link

Publish the build in build/mac to Depot for testers and give me a link.

The server also offers prompts (publish-alpha, publish-update, issue-tester-keys) and two resources (depot://docs/publishing, depot://docs/access) your client can show.