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.
Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.
Chave de API
THEDEPLOYER_API_KEY
Última verificação
2026-11-08
Estrelas
—
Ferramentas
—
Disponibilidade
—
Tools
Tool
What it does
Key
check_repo
Will a public repository deploy? What it found, what's missing, and what it would cost on each cloud
Not needed
plan_deploy
The check, plus your connected accounts and projects, and the next step to take
Needed
status
Your projects, their live addresses and their latest deployment
Needed
logs
The latest deployment's log for a project, with secrets removed
Needed
redeploy
Pulls the latest code on a live project's branch and restarts it
Needed
request_done_for_you
Asks for a done-for-you Launch or Move; you finish the order in The Deployer
Needed
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 dpl_your_key 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 ${THEDEPLOYER_API_KEY}" as
the header. Claude Code fills it in from each person's THEDEPLOYER_API_KEY environment variable.
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:
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.
This package uses Node.js, which ignores HTTPS_PROXY unless you turn that on. Add NODE_USE_ENV_PROXY
next to it, which needs Node.js 22.21 or newer, or 24.0 or newer. (The --use-env-proxy flag does the
same from Node.js 22.21 or 24.5.) On older versions, this package can't go through a proxy.
If your network inspects HTTPS with its own certificate, set NODE_EXTRA_CA_CERTS to that certificate's
file (PEM):
A key works only with The Deployer's MCP server, and only through its tools: check_repo,
plan_deploy, status, logs (with secrets removed), redeploy and request_done_for_you. It can't
touch your cloud or git credentials, your environment variables, your billing or your account settings, and
it can't create more keys. The Deployer stores only a hash of it. Revoke a key on the Profile page at any
time; use one key per tool or machine, so you can revoke one without touching the rest. Changing or
resetting your password revokes all your keys.
redeploy changes a live app. Keep your tool asking you before it runs redeploy, rather than approving
it automatically.
Tool answers come from your repositories and deployments. Treat them like any other text your agent reads.
How this package works
index.mjs is a bridge with no dependencies. It reads MCP messages from stdin, sends each one to The
Deployer's hosted endpoint over HTTPS with your key, and writes the answers to stdout. The tools run on The
Deployer, so this package doesn't change when they do.
Every request gets an answer. When The Deployer refuses one or can't be reached, the answer is an error
that says why, such as a revoked key or a timeout. The bridge never follows redirects, and it never puts
your key anywhere but the Authorization header.
Variable
Meaning
THEDEPLOYER_API_KEY
Your personal API key. Without it, only check_repo works
THEDEPLOYER_MCP_URL
The endpoint, if not https://app.thedploy.com/api/v1/mcp. It must use https://, except on this computer (127.0.0.1, ::1 or localhost)
THEDEPLOYER_TIMEOUT_MS
How long to wait for one answer, in milliseconds, from 1000 to 600000 (default 120000)
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo The Deployer?
Copie nesta página a configuração http para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
The Deployer precisa de uma chave de API?
O publicador lista estas variáveis de ambiente: THEDEPLOYER_API_KEY.
Qual transporte The Deployer usa?
The Deployer é acessado por HTTP.
Quando The Deployer foi verificado pela última vez?
Última verificação: 2026-11-08. Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.