The Deployer MCP Server

by thedploy Your server? Claim it

answering

The Deployer is answering right now. Last checked 3 min ago. 82 installs a week from npm. It exposes 23 tools. Last commit 31 Oct 2026.

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

Installs per day peak 296 · avg 18 · -4% w/w

a month agotoday

Uptime history 49 days of history · worst day 93%

49 days agonow

100.0%

Uptime 24h

183 of 183 checks

Tools

read from the server

511 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 69

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

31 Oct 23 tool descriptions were rewritten25 times that day account, api, api_catalog and 20 more

31 Oct 19 tools changed the parameters they ask for20 times that day account, api, api_catalog and 16 more

31 Oct 6 tools appeared api_read, claim_fix, fix and 3 more

25 Oct 11 tools appeared account, api, api_catalog and 8 more

25 Oct 3 tools changed the parameters they ask for logs, redeploy, status

25 Oct a tool description was rewritten redeploy

25 Oct a tool changed version

15 Sep a tool description was rewritten request_done_for_you

15 Sep a tool changed the parameters it asks for request_done_for_you

and 3 more, back to 15 September 2026

The Deployer missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://app.thedploy.com/api/v1/mcp

~/.codex/config.toml

[mcp_servers.deployer]
url = "https://app.thedploy.com/api/v1/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "deployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 23

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

api

api

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.

api_catalog

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.

api_read

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.

api_schema

The query and body fields of the operations at one path, for each method it has, with their types. Changes nothing.

fix

fix

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.

fix_status

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.

project

create_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.

project

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.

account

account

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.

claim

claim_fix

Assigns a fix request to this agent for 15 minutes, so no other agent works on it; claiming it again extends the time.

deployment

deployment

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.

diagnose

diagnose

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.

env

set_env

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.

fixes

fixes

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.

guide

guide

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.

launch

launch

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.

logs

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.

plan

plan_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.

redeploy

redeploy

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.

repo

check_repo

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.

report

report_fix

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.

request

request_done_for_you

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.

status

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.

Endpoints

URL	Transport	State	Latency	Checked
https://app.thedploy.com/api/v1/mcp	streamable-http	answering	495 ms	3 min ago
https://app.thedploy.com/mcp	streamable-http	sign-in	486 ms	6 min ago

Alternatives to The Deployer

same job, measured the same way

AppScreenStudio

by appscreenstudio

Design App Store and Google Play screenshots with your AI agent in the AppScreenStudio editor.

49 tools answering

Google Cloud Run

by googleapis-run

Deploy applications to Cloud Run

5 tools answering

Google Ads

by b77

Read and manage your Google Ads account in chat.

answering

Dualtran MCP

by seigwen

Translate text with Google or your own AI model (BYOK, 20+ providers) from any MCP client.

77 installs/wk local only

AIdata

by aidata

Google Analytics, Search Console, Ads, CRM, Cloudflare and more for your sites, from your own AI.

answering

shotfleet

by shotfleet

Capture and check localized App Store and Google Play screenshots from your AI agent.

local only

Searlo

by searlo

Google SERP, Maps, Shopping, News and AI-answer data for AI agents, from the Searlo search API.

answering

Adside

by adside

AI agents that manage paid ads on Meta, LinkedIn, and Google Ads from any MCP client.

answering

The Deployer — questions

Answers built from our own checks of this server.

What can The Deployer do?

It exposes 23 tools, read directly from the server on our last check. Among them: account, api, api_catalog, api_read, api_schema, check_repo and 17 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is The Deployer mostly used for?

Its tools cluster around api, project and fix. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is The Deployer working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 183 of 183 checks got a reply (100.0%), average response time 511 ms. The bar chart above shows every period we have measured.

How do I connect The Deployer?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to The Deployer?

No API key is involved. The Deployer answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is The Deployer?

It answers our handshake in 511 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use The Deployer?

The npm package thedeployer-mcp was installed 82 times in the last week. Week over week that is -4%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is The Deployer open source?

The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at app.thedploy.com, which runs on its operator's own terms.