The Deployer MCP server

The Deployer MCP server

Use The Deployer from Claude Code, Cursor, VS Code and other AI coding tools. Ask whether a repository will deploy, plan a deploy, see where your projects stand, read the latest deployment log, or put your latest code live, without leaving the editor.

The Deployer runs your app in your own DigitalOcean, AWS, Google Cloud or Azure account, so the cloud bills you directly.

Tools

To create a key, sign in to The Deployer, open Profile, and use API keys and AI coding tools. The page also shows these setups with your key filled in.

Setup

The hosted server needs nothing installed. Replace dplyourkey with your key.

Keep the key out of files you commit. Put it in your user-level settings, or have your tool read it from an environment variable or a prompt, as shown below for project files.

Claude Code, for all your projects (stored in ~/.claude.json):

claude mcp add --transport http --scope user thedeployer https://app.thedploy.com/api/v1/mcp --header "Authorization: Bearer dpl_your_key"

To share the server in a project's .mcp.json, use "Authorization": "Bearer ${THEDEPLOYERAPIKEY}" as the header. Claude Code fills it in from each person's THEDEPLOYERAPIKEY environment variable.

Cursor, in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "thedeployer": {
      "url": "https://app.thedploy.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer dpl_your_key" }
    }
  }
}

In a project's .cursor/mcp.json, use "Authorization": "Bearer ${env:THEDEPLOYERAPIKEY}" instead, so Cursor reads the key from your environment.

VS Code, in .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:

{
  "inputs": [
    { "type": "promptString", "id": "thedeployer-key", "description": "The Deployer API key", "password": true }
  ],
  "servers": {
    "thedeployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer ${input:thedeployer-key}" }
    }
  }
}

The same works in your user configuration (run MCP: Open User Configuration).

Gemini CLI, in ~/.gemini/settings.json:

{
  "mcpServers": {
    "thedeployer": {
      "httpUrl": "https://app.thedploy.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer dpl_your_key" }
    }
  }
}

Tools that start a local command (Cline, Windsurf and others) use this package, which needs Node.js 18 or newer. Add it to the tool's user-level MCP settings:

{
  "mcpServers": {
    "thedeployer": {
      "command": "npx",
      "args": ["-y", "thedeployer-mcp"],
      "env": { "THEDEPLOYER_API_KEY": "dpl_your_key" }
    }
  }
}

If your tool's configuration looks different, its MCP documentation has the equivalent fields: a URL with an Authorization header, or a command with an environment variable.

Proxies and company networks

With the hosted server, your AI tool makes the connection, so its own proxy settings apply.

Shortened. The full README is on GitHub.