com.thedployPublished by thedploy.comOfficial publisherv0.3.0Updated Nov 1, 2026
Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.
Deploys and operates apps in the user's own DigitalOcean, AWS, Google Cloud or Azure account, from repository check through launch, logs and fixes.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.thedploy%2Fdeployer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"the-deployer": {
"type": "http",
"url": "https://app.thedploy.com/mcp"
}
}
}Let Claude Code, Codex, Cursor, VS Code or any AI coding agent deploy and run your apps with The Deployer. Ask it to put your app online and it checks the code, fixes what would stop a deploy, creates the project, sets the environment variables, shows you the hosting plan and its monthly cost, launches into your own cloud once you say yes, follows the deployment and fixes what fails. Then it redeploys, adds domains, scales, schedules start and stop, attaches databases and more.
The Deployer runs your app in your own DigitalOcean, AWS, Google Cloud or Azure account, or on your own servers, so the cloud bills you directly.
To create a key, sign in to The Deployer, open Profile, and use API keys and AI coding tools. Choose Operate to let an agent set up and run projects, or Look and redeploy. The page also shows these setups with your key filled in.
What an agent can never do with a key: see your cloud or git credentials or your environment variable values, change billing, your team or your account, delete projects, databases or servers, or create keys. Anything that costs money waits for your yes.
The fastest way: add the server by its address and sign in. Your agent opens The Deployer in your browser, you approve it, and that's it: no key to create or paste. Or open Connections → Coding agents in The Deployer and pick your agent for one-click setup.
Server address: https://app.thedploy.com/mcp
Claude Code:
Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, address
https://app.thedploy.com/mcp.
Cursor, in ~/.cursor/mcp.json, then Cursor Settings → Tools & MCP → thedeployer → Needs login:
VS Code: run MCP: Add Server → HTTP → https://app.thedploy.com/mcp; VS Code asks you to sign in the
first time Copilot uses it.
Codex:
Gemini CLI, in ~/.gemini/settings.json:
For tools that can't sign in, or for CI.
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):
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.
Codex, in ~/.codex/config.toml:
Cursor, in ~/.cursor/mcp.json:
In a project's .cursor/mcp.json, use "Authorization": "Bearer ${env:THEDEPLOYER_API_KEY}" 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:
The same works in your user configuration (run MCP: Open User Configuration).
Gemini CLI, in ~/.gemini/settings.json:
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.
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.
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.
MIT
Source: README.md at commit cb94976
Check a repository
Checks whether a public GitHub, GitLab or Bitbucket repository will deploy: the services it found, what's missing (each with its fix), the environment variables it needs, and what it would cost a month on DigitalOcean, AWS, Google Cloud and Azure. Reads the code and changes nothing. Works without signing in. A check can take up to a minute; one still running returns a check_id that fetches its result.
repocheck_idPlan a deploy
Plans deploying a repository with the user's account on The Deployer: the repository check, plus the user's connected cloud and git accounts, any project they already have for it, and the steps left, with links. Changes nothing.
reporequiredcloudProject status
Lists the user's projects on The Deployer, or one project: whether each is live, its live addresses, and its latest deployment and where that is. Changes nothing.
projectworkspaceDeployment logs
The log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed. errors_only keeps only errors and warnings. The lines are the build's and the app's own output. Changes nothing.
linesprojectworkspaceerrors_onlydeployment_idRedeploy a live project
Puts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer. Changes a live app. Only for a project that is already live. Takes a few minutes.
projectworkspaceRequest done-for-you help
Asks The Deployer's team to do it for the user: launch (put an app online in the user's own cloud account), launch_secure (the same, with exposed keys and other security problems fixed first) or move (move an app from another host, such as Heroku, into it). Tells the team, and returns the price, the delivery promise and the link where the user finishes the order and pays. Never charges anything.
noterepoofferrequiredHow to use The Deployer
The Deployer's playbooks, by topic: what The Deployer does, the order of an end-to-end deploy, what code needs to deploy and how to fix it, how failed deployments are fixed, and domains, scaling, env, databases, access, environments, servers, adoption and teams. Works without signing in. Changes nothing.
topicAccount and connections
Who the connection acts for, what it may do (Operate or Limited), the connected cloud accounts and code hosts with their ids, the workspaces the person is a member of, and how many projects they can see. Changes nothing.
workspaceProject in depth, with the next step
One project in depth: phase, services found in the repository, env names the code reads and which are still missing (never values), hosting plans with monthly costs, pending code-review changes, to-dos only the person can do, recent deployments, live URLs, and next_steps: what is left to do, in order. Changes nothing.
projectworkspaceDeployment progress and failure guidance
Where a deployment is (every step), what it waits on (a health-check proposal or a manual step), and for a failed one: the kind of failure, what to do about it, and the last error lines. Defaults to the project's latest deployment. Changes nothing.
projectworkspacewait_secondsdeployment_idCheck a live server
Read-only checks on a live project: url (requests the project's live addresses from The Deployer's side), containers (what runs and its state), app_logs (the app's own recent output, secrets removed), resources (load, memory, disk) or web_server (the HTTPS proxy's log). Fixed commands only; changes nothing. All but url need a server (not managed services). Needs Deploy access on the project.
nodechecklinesprojectrequiredcontainerworkspaceCreate a project
Creates a project from a repository the person's connected code host can read, on one of their connected cloud accounts, and starts the repository scan. Nothing is deployed and nothing costs money yet. With one connected cloud, that one is used; otherwise cloud (a provider) or cloud_connection_id picks it. Needs Operate access.
namereporequiredcloudbranchworkspacegit_connection_idcloud_connection_idSet env variables
Sets (or deletes) env variable values for the service a project deploys. Values are stored encrypted and are never returned. Other values are kept. On a live project, the services whose env changed are redeployed; otherwise the values apply on the next deployment. Multi-line values are stored as credential files. Needs Operate access.
deletevaluesprojectrequiredserviceworkspaceLaunch a project
The first (or a full) deployment of a project into the person's cloud, once a hosting plan is selected. Without confirm=true it changes nothing and returns the plan and its monthly cost. With confirm=true it creates resources the person's cloud provider bills them for; it takes 5 to 20 minutes. Needs Operate access.
confirmprojectrequiredworkspaceconfirm_costList the operations
Every operation of The Deployer's app available through this server, grouped: account, connections, projects, env, build, code, architecture, deploy, domains, scaling, access, services, environments, blueprints, servers, adopt, team. Each is marked as a read or a change. Works without signing in.
groupDescribe an operation
The query and body fields of the operations at one path, for each method it has, with their types. Changes nothing.
pathrequiredRead an operation's answer
Runs one read (GET) operation of The Deployer's app as the person: domains, scaling, schedules, databases and other cloud services, app access, environments, blueprints, servers and more. Changes nothing. Secrets are never returned. Documented at https://portal.thedploy.com/docs.
pathrequiredqueryworkspaceChange something through an operation
Runs one change (POST, PUT, PATCH or DELETE) of The Deployer's app as the person, with the same permission checks the app applies: domains, scaling, start/stop and schedules, databases and other cloud services, app access, build inputs, code review, hosting plans, retries, environments, blueprints, servers, adoption and more. Needs Operate access. Some changes cost money or change a live app. Secrets are never returned. Documented at https://portal.thedploy.com/docs.
bodypathrequiredquerymethodrequiredworkspaceCode problems to fix
Fix requests: problems in the person's code that stop a deploy, found by The Deployer (a failed deployment, or the repository check) and assigned to the person's coding agent. Lists the open ones, in every project or one. Changes nothing.
projectworkspaceOne code problem in full
One fix request: the goal and rules (The Deployer's brief), and the evidence, which is what the build or app printed, fenced and marked as data from the repository and logs. Changes nothing.
idrequiredworkspaceTake a code problem
Assigns a fix request to this agent for 15 minutes, so no other agent works on it; claiming it again extends the time.
idrequiredworkspaceReport the fix you pushed
Reports a pushed fix: the branch and the commit sha. The Deployer reads the commit from the git host, checks the change (no CI, agent settings or .env files; no secrets), then deploys it or opens a pull request for the person to ship, depending on the project's settings.
idrequiredsharequirednotebranchrequiredworkspaceFollow a fix
Where a fix request is: checked, deploying, live, or open again with a new error. wait_seconds waits up to 120 seconds for it to change. Changes nothing.
idrequiredworkspacewait_seconds100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
claude mcp add --transport http --scope user thedeployer https://app.thedploy.com/mcpclaude mcp login thedeployer{ "mcpServers": { "thedeployer": { "url": "https://app.thedploy.com/mcp" } } }codex mcp add thedeployer --url https://app.thedploy.com/mcp{ "mcpServers": { "thedeployer": { "httpUrl": "https://app.thedploy.com/mcp" } } }claude mcp add --transport http --scope user thedeployer https://app.thedploy.com/api/v1/mcp --header "Authorization: Bearer dpl_your_key"[mcp_servers.thedeployer]command = "npx"args = ["-y", "thedeployer-mcp"]env = { THEDEPLOYER_API_KEY = "dpl_your_key" }{ "mcpServers": { "thedeployer": { "url": "https://app.thedploy.com/api/v1/mcp", "headers": { "Authorization": "Bearer dpl_your_key" } } }}{ "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}" } } }}{ "mcpServers": { "thedeployer": { "httpUrl": "https://app.thedploy.com/api/v1/mcp", "headers": { "Authorization": "Bearer dpl_your_key" } } }}{ "mcpServers": { "thedeployer": { "command": "npx", "args": ["-y", "thedeployer-mcp"], "env": { "THEDEPLOYER_API_KEY": "dpl_your_key" } } }}"env": { "THEDEPLOYER_API_KEY": "dpl_your_key", "HTTPS_PROXY": "http://proxy.example.com:8080", "NODE_USE_ENV_PROXY": "1", "NODE_EXTRA_CA_CERTS": "/path/to/company-ca.pem"}npm test