_ registry / mcp streamable-http · checked 1h ago

thedeployer

https://app.thedploy.com

Registry code: 60b1bcf3532c77e4

api record

The Deployer puts apps online in the user's own cloud account (DigitalOcean, AWS, Google Cloud or Azure) or on their own servers, and keeps them running. With these tools you can take a repository all the way to a live app and operate it: check the code, create the project, set env, choose a hosting plan, launch, follow and fix deployments, then domains, scaling, databases, access, environments and more.

How to work: start with guide (topic overview, then end_to_end before a first deploy). account gives the ids create_project takes. After each step of a deploy, call project and follow its…

endpoint
https://app.thedploy.com/api/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is thedeployer live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is thedeployer free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does thedeployer have?
23 tools: check_repo, plan_deploy, set_env, redeploy, request_done_for_you, deployment, create_project, launch, ….
Is thedeployer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.8%

90 days 99.2%· all time 99.2%

latency
483ms

last good check

priced tools
0

of 23 tools

_ answered our checks, 90 days 369 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
infrastructure & devops ci & deployment
used for
  • check if a repo will deploy
  • plan a deployment to my cloud
  • redeploy a live project
  • read deployment logs
  • request done-for-you deployment
takes → gives
text → data
tools
4 reads1 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 23 tools
2 open10 auth-required 11 never probed 12 of 23 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • api_catalog open 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "group": {
      "enum": [
        "account",
        "connections",
        "projects",
        "env",
        "build",
        "code",
        "architecture",
        "deploy",
        "fixes",
        "domains",
        "scaling",
        "access",
        "services",
        "environments",
        "blueprints",
        "servers",
        "adopt",
        "team"
      ],
      "type": "string"
    }
  }
}
    arguments 28 lines
  • guide open 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "topic": {
      "enum": [
        "overview",
        "end_to_end",
        "readiness",
        "fix_failed_deploy",
        "env",
        "domains",
        "scaling",
        "services",
        "access",
        "environments",
        "servers",
        "adopt",
        "team"
      ],
      "type": "string",
      "description": "Default overview"
    }
  }
}
    arguments 24 lines
  • fix_status auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    },
    "wait_seconds": {
      "type": "integer",
      "maximum": 120,
      "minimum": 0
    }
  }
}
    arguments 20 lines
  • logs reads auth-required 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lines": {
      "type": "integer",
      "maximum": 400,
      "minimum": 1,
      "description": "How many lines, newest last. Default 80."
    },
    "project": {
      "type": "string",
      "description": "The project's id, name or repository. Optional with one project."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    },
    "errors_only": {
      "type": "boolean",
      "description": "Only errors and warnings"
    },
    "deployment_id": {
      "type": "integer",
      "description": "A specific deployment, instead of the latest"
    }
  }
}
    arguments 27 lines
  • status reads auth-required 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "A project's id, name or repository. Leave out to list them all."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 13 lines
  • fix auth-required 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The fix request's id, fr_..."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 16 lines
  • fixes auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 13 lines
  • api_schema auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "e.g. /projects/12/scaling"
    }
  }
}
    arguments 12 lines
  • account auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 9 lines
  • project auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 13 lines
  • api_read auth-required 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "The operation's path with ids filled in, e.g. /projects/12/scaling"
    },
    "query": {
      "type": "object",
      "description": "Query parameters"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 20 lines
  • diagnose auth-required 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project"
  ],
  "properties": {
    "node": {
      "type": "string",
      "description": "The server, default app-1"
    },
    "check": {
      "enum": [
        "url",
        "containers",
        "resources",
        "web_server",
        "app_logs"
      ],
      "type": "string"
    },
    "lines": {
      "type": "integer",
      "maximum": 400,
      "minimum": 10
    },
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "container": {
      "type": "string",
      "description": "For app_logs: one container's name"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 39 lines
  • check_repo reads unknown 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "owner/name, or the repository's URL"
    },
    "check_id": {
      "type": "string",
      "description": "The check_id of an earlier check, to get its result"
    }
  }
}
    arguments 13 lines
  • plan_deploy reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "repo"
  ],
  "properties": {
    "repo": {
      "type": "string",
      "description": "owner/name, or the repository's URL"
    },
    "cloud": {
      "enum": [
        "digitalocean",
        "aws",
        "gcp",
        "azure"
      ],
      "type": "string",
      "description": "The cloud to plan for. Optional."
    }
  }
}
    arguments 22 lines
  • set_env unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project"
  ],
  "properties": {
    "delete": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Names to remove"
    },
    "values": {
      "type": "object",
      "description": "Names to values, e.g. {\"API_URL\": \"https://...\"}",
      "additionalProperties": {
        "type": "string"
      }
    },
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "service": {
      "type": "string",
      "description": "Service id or name, when the project has several"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 34 lines
  • redeploy changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The live project's id, name or repository. Optional with one project."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 13 lines
  • request_done_for_you sends messages unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "offer"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "Anything the team should know, such as the current host or a deadline"
    },
    "repo": {
      "type": "string",
      "description": "The repository, if there is one"
    },
    "offer": {
      "enum": [
        "launch",
        "launch_secure",
        "move"
      ],
      "type": "string"
    }
  }
}
    arguments 24 lines
  • deployment unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository. Optional with one project."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    },
    "wait_seconds": {
      "type": "integer",
      "maximum": 120,
      "minimum": 0,
      "description": "Seconds to wait for the status or step to change"
    },
    "deployment_id": {
      "type": "integer",
      "description": "A specific deployment, instead of the latest"
    }
  }
}
    arguments 23 lines
  • create_project unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "repo"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "The project's name. Default: the repository's name"
    },
    "repo": {
      "type": "string",
      "description": "owner/name, or the repository's URL"
    },
    "cloud": {
      "enum": [
        "digitalocean",
        "aws",
        "gcp",
        "azure"
      ],
      "type": "string"
    },
    "branch": {
      "type": "string",
      "description": "The branch to deploy. Default: the repository's default"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    },
    "git_connection_id": {
      "type": "integer"
    },
    "cloud_connection_id": {
      "type": "integer"
    }
  }
}
    arguments 39 lines
  • launch unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project"
  ],
  "properties": {
    "confirm": {
      "type": "boolean",
      "description": "true deploys; without it nothing is created"
    },
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    },
    "confirm_cost": {
      "type": "boolean",
      "description": "true allows a plan above the account's cost ceiling"
    }
  }
}
    arguments 24 lines
  • api unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "method",
    "path"
  ],
  "properties": {
    "body": {
      "type": "object",
      "description": "The JSON body, for POST, PUT and PATCH"
    },
    "path": {
      "type": "string",
      "description": "The operation's path with ids filled in, e.g. /projects/12/scaling"
    },
    "query": {
      "type": "object",
      "description": "Query parameters"
    },
    "method": {
      "enum": [
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
      ],
      "type": "string"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 34 lines
  • claim_fix unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 15 lines
  • report_fix unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "branch",
    "sha"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "sha": {
      "type": "string",
      "description": "The pushed commit's sha"
    },
    "note": {
      "type": "string",
      "description": "What changed, in a sentence or two"
    },
    "branch": {
      "type": "string",
      "description": "The branch the fix was pushed to"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 60b1bcf3532c77e4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/60b1bcf3532c77e4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/60b1bcf3532c77e4/badge.svg)](https://brick.blue/agent/60b1bcf3532c77e4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.