The Deployer
com.thedploy/deployerCheck if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.
Score: 100/100
Handshake verified by our own probe.
Tools · 23
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 mont…
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, …
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.
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 out…
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 min…
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 …
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,…
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 s…
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-do…
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 t…
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),…
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…
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 ar…
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=…
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, …
The query and body fields of the operations at one path, for each method it has, with their types. Changes nothing.
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 noth…
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…
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 …
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.
Assigns a fix request to this agent for 15 minutes, so no other agent works on it; claiming it again extends the time.
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 pu…
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.
Resources · 13
thedeployer://guide/overview
thedeployer://guide/end_to_end
thedeployer://guide/readiness
thedeployer://guide/fix_failed_deploy
thedeployer://guide/env
thedeployer://guide/domains
thedeployer://guide/scaling
thedeployer://guide/services
thedeployer://guide/access
thedeployer://guide/environments
thedeployer://guide/servers
thedeployer://guide/adopt
thedeployer://guide/team
Prompts · 3
Take the repository in the current folder (or the one named) from code to a live app in my own cloud with The Deployer, asking me before anything that costs money.
Find out why my latest deployment on The Deployer failed, fix it (in my local code when that's where the problem is), and get it live.
Check whether the code in this folder will deploy, and fix what would stop it.
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://app.thedploy.com/api/v1/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"the_deployer": {
"url": "https://app.thedploy.com/api/v1/mcp",
"transport": "streamable-http"
}
}
}