SnapDeploy MCP server

@snapdeploy/mcp

Deploy and manage SnapDeploy containers from your AI assistant — Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Gemini CLI, or any client that speaks the Model Context Protocol over stdio.

Say "deploy this repo to SnapDeploy" and get a live URL back. Builds, logs, environment variables, managed databases and custom domains — without leaving the chat.

Setup

token with the deploy scope (the page generates the snippets below with your token already filled in).

1. Sign in at snapdeploy.dev, open API Keys and create a

1. Add the server to your client:

Claude Code

claude mcp add --scope user snapdeploy -e SNAPDEPLOY_API_KEY=sd_pat_your_token -- npx -y @snapdeploy/mcp

Cursor (~/.cursor/mcp.json), Windsurf (~/.codeium/windsurf/mcpconfig.json), Gemini CLI** (~/.gemini/settings.json), Claude Desktop and other JSON-configured clients:

{
  "mcpServers": {
    "snapdeploy": {
      "command": "npx",
      "args": ["-y", "@snapdeploy/mcp"],
      "env": { "SNAPDEPLOY_API_KEY": "sd_pat_your_token" }
    }
  }
}

Codex CLI (~/.codex/config.toml):

[mcp_servers.snapdeploy]
command = "npx"
args = ["-y", "@snapdeploy/mcp"]
env = { SNAPDEPLOY_API_KEY = "sd_pat_your_token" }

Claude Code plugin (token stored in secure storage instead of a config file):

/plugin marketplace add AAR-Labs/snapdeploy-mcp
/plugin install snapdeploy@snapdeploy

Restart the session; the snapdeploy tools appear. Your repository must be on GitHub and GitHub must be connected to SnapDeploy once (the connector returns the link if it isn't).

Tools

Scopes nest (read ⊂ deploy ⊂ manage); the server enforces them before any tool runs. There is no delete tool, and the server refuses deletes, subscription cancellations and password changes for every token — those need a person signed in to the dashboard or the mobile app.

Safety model

same token gets 403 INTERACTIVESESSIONREQUIRED.

• Nothing destructive, ever. Even an agent that escalates to a raw API call with the

and credentials are masked — on the server, not just in this connector.

• Secrets never reach the model. Environment-variable values come back as (set)

page and every request returns 401 from that moment.

• Scoped, expiring, revocable tokens with their own rate limit. Revoke on the API Keys

deployment instead of starting another build.

• Retry-safe deploys. Identical requests inside ten minutes return the original

and upgrade link, and the assistant is told not to retry.

• Plan limits are relayed, not retried. 402/429 replies carry SnapDeploy's own message

Environment variables

Links

Cursor · Codex / Gemini CLI · Lovable exports

• Guides: Claude Code ·

API

• Reference: snapdeploy.dev/docs/mcp ·

• Design write-up: why an agent that can deploy must not be able to delete

MIT © AAR Labs