English Français العربية

SnapDeploy

Official registry Cloud and DevOps

Deploy and manage SnapDeploy apps from your AI assistant: builds, logs, env vars, add-ons, domains.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @snapdeploy/mcp
Claude Code 
claude mcp add snapdeploy -e 'SNAPDEPLOY_API_KEY=<your snapdeploy_api_key>' -e 'SNAPDEPLOY_READ_ONLY=<SNAPDEPLOY_READ_ONLY>' -- npx -y @snapdeploy/mcp@0.1.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "snapdeploy": {
            "command": "npx",
            "args": [
                "-y",
                "@snapdeploy/mcp@0.1.2"
            ],
            "env": {
                "SNAPDEPLOY_API_KEY": "<your snapdeploy_api_key>",
                "SNAPDEPLOY_READ_ONLY": "<SNAPDEPLOY_READ_ONLY>"
            }
        }
    }
}

Environment variables

  • SNAPDEPLOY_API_KEY required secret Scoped personal access token (sd_pat_…) from https://snapdeploy.dev/api-keys
  • SNAPDEPLOY_READ_ONLY Set to 1 to expose only the read tools

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. @snapdeploy/mcp
  2. Setup
  3. Tools
  4. Safety model
  5. Environment variables
  6. Links

@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

  1. Sign in at snapdeploy.dev, open API Keys and create a token with the deploy scope (the page generates the snippets below with your token already filled in).
  2. 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/mcp_config.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

ScopeTools
readlist_apps get_status get_logs get_deployments check_quota list_repos detect_env_vars
deploydeploy deploy_image set_env start_container stop_container wake_container
managecreate_database add_domain assign_always_on

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.

Prebuilt images. deploy builds from a connected GitHub repository; there is no image tool. To run a public Docker image, use the dashboard (Deploy Your Application → Docker Image) or POST /api/mobile/containers with name, image, imageTag, port, then POST /api/mobile/containers/{containerId}/start. Images must come from Docker Hub, ghcr.io, quay.io or public.ecr.aws, publish linux/amd64 or linux/arm64, and pass SnapDeploy's create-time policy check; a 400 Security policy violation is final and must not be retried. Full rules: https://snapdeploy.dev/llms-full.md

Safety model

  • Nothing destructive, ever. Even an agent that escalates to a raw API call with the same token gets 403 INTERACTIVE_SESSION_REQUIRED.
  • Secrets never reach the model. Environment-variable values come back as (set) and credentials are masked — on the server, not just in this connector.
  • Scoped, expiring, revocable tokens with their own rate limit. Revoke on the API Keys page and every request returns 401 from that moment.
  • Retry-safe deploys. Identical requests inside ten minutes return the original deployment instead of starting another build.
  • Plan limits are relayed, not retried. 402/429 replies carry SnapDeploy's own message and upgrade link, and the assistant is told not to retry.

Environment variables

VariableRequiredMeaning
SNAPDEPLOY_API_KEYyesScoped token (sd_pat_…) or legacy API key
SNAPDEPLOY_READ_ONLYno1 exposes only the read tools
SNAPDEPLOY_BASE_URLnoDefaults to https://snapdeploy.dev

MIT © AAR Labs

Frequently asked questions

What is SnapDeploy?

Deploy and manage SnapDeploy apps from your AI assistant: builds, logs, env vars, add-ons, domains.

How do I install SnapDeploy?

It runs on your machine. In Claude Code: claude mcp add snapdeploy -e 'SNAPDEPLOY_API_KEY=<your snapdeploy_api_key>' -e 'SNAPDEPLOY_READ_ONLY=<SNAPDEPLOY_READ_ONLY>' -- npx -y @snapdeploy/mcp@0.1.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does SnapDeploy need an API key?

Yes. It expects SNAPDEPLOY_API_KEY, which you set in its configuration.

Is SnapDeploy open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains SnapDeploy?

It is published by AAR-Labs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.