Skip to main content

The Deployer

com.thedploy/deployerVersion 0.3.0

Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.

Status

Responds450 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:19 UTC
Latency
450 ms
Remotes responding
2 of 2
Sign-in
OAuth sign-in, No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://app.thedploy.com/api/v1/mcpResponds450 ms
No sign-in

Claude Code

claude mcp add --transport http deployer https://app.thedploy.com/api/v1/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: deployer
Remote MCP server URL: https://app.thedploy.com/api/v1/mcp

Cursor

{
  "mcpServers": {
    "deployer": {
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"deployer","type":"http","url":"https://app.thedploy.com/api/v1/mcp"}'
Streamable HTTP
https://app.thedploy.com/mcpSign-in required461 ms
OAuth sign-in

Claude Code

This server asks for sign-in. Your client opens the sign-in when it connects.

claude mcp add --transport http deployer https://app.thedploy.com/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: deployer
Remote MCP server URL: https://app.thedploy.com/mcp

Cursor

{
  "mcpServers": {
    "deployer": {
      "url": "https://app.thedploy.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"deployer","type":"http","url":"https://app.thedploy.com/mcp"}'
Streamable HTTP
npm: thedeployer-mcp 0.1.1
Package only

npm (npx)

claude mcp add deployer -- npx -y thedeployer-mcp@0.1.1

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

23 tools

Tools of The Deployer
Read-only
Idempotent
Open world
accountWho 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.NoYesYesNo
apiRuns 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.YesNoNoYes
api_catalogEvery 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.NoYesYesNo
api_readRuns 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.NoYesYesYes
api_schemaThe query and body fields of the operations at one path, for each method it has, with their types. Changes nothing.NoYesYesNo
check_repoChecks 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.NoYesNoYes
claim_fixAssigns a fix request to this agent for 15 minutes, so no other agent works on it; claiming it again extends the time.NoNoYesNo
create_projectCreates 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.NoNoNoNo
deploymentWhere 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.NoYesYesNo
diagnoseRead-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.NoYesYesNo
fixOne 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.NoYesYesNo
fix_statusWhere 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.NoYesYesNo
fixesFix 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.NoYesYesNo
guideThe 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.NoYesYesNo
launchThe 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.YesNoNoYes
logsThe 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.NoYesYesNo
plan_deployPlans 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.NoYesNoYes
projectOne 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.NoYesYesNo
redeployPuts 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.YesNoNoNo
report_fixReports 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.NoNoNoYes
request_done_for_youAsks 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.NoNoNoYes
set_envSets (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.NoNoNoNo
statusLists 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.NoYesYesNo

Details

Registry status
Active
Published
Oct 31, 2026
Updated
Oct 31, 2026
Categories (suggested)
Developer toolsCloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing