Skip to content
Agentmart
Submit a tool

The Deployer

Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.

Connector by thedploy.com · Domain verified by the MCP Registry

IndexedMITLocal (stdio)Remote (HTTP)
Write a review

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/thedploy-com-deployer

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://app.thedploy.com/api/v1/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
11 read · 2 write · 4 delete
Secrets
2 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 17

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 11 · Look things up without changing anything.

  • account
  • api_catalog
  • api_schema
  • check_repo
  • deployment
  • diagnose
  • guide
  • logs
  • plan_deploy
  • project
  • status

Write 2 · Create, change, send or run things.

  • create_project
  • request_done_for_you

Delete 4 · Delete, drop, revoke or wipe things.

  • api
  • launch
  • redeploy
  • set_env

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • Authorization
  • THEDEPLOYER_API_KEY

Network hosts it talks to 1

  • app.thedploy.com · found in remote endpoint, install command

Files it touches

  • Any path the agent passes to its tools

Tools (17)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • accountAccount and connectionsread-only

    Who this key acts for, what it may do (Operate or Limited), the connected cloud accounts and code hosts (with their ids, for create_project), the workspaces the person is a member of, and how many projects they can see. Changes nothing.

  • apiRun an operationcan change or delete data

    Runs one operation from api_catalog as the person, with the same permission checks The Deployer's 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. Reads work with any key; changes need a key with Operate access, and ones that cost money or change a live app need the person's yes first. Secrets are never returned.

  • api_catalogList the operationsread-only

    Every other operation agents can run with api, grouped: account, connections, projects, env, build, code, architecture, deploy, domains, scaling, access, services, environments, blueprints, servers, adopt, team. Each says whether it only reads or changes something. No API key needed.

  • api_schemaDescribe an operationread-only

    The query and body fields of one operation from api_catalog, with their types. Changes nothing.

  • check_repoCheck a repositoryread-only

    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. No API key needed. A check can take up to a minute; if it's still running, call again with the check_id it returned.

  • create_projectCreate 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 you don't need to name it; otherwise pass cloud (a provider) or cloud_connection_id (from account). Then follow project's next_steps. Needs a key with Operate access.

  • deploymentDeployment progress and failure guidanceread-only

    Where a deployment is (every step), what it waits on (a health-check proposal or a manual step, and the call that answers it), and for a failed one: the kind of failure, what to do, and the last error lines. Defaults to the project's latest deployment. Changes nothing.

  • diagnoseCheck a live serverread-only

    Read-only checks on a live project, for when an app misbehaves after deploying: url (request the project's own live addresses from The Deployer's side, for when you can't reach them yourself), containers (what runs and its state), app_logs (the app's own recent output, secrets removed; container picks one), resources (load, memory, disk) or web_server (the HTTPS proxy's log). Fixed commands only, nothing changes. Everything but url needs a server (not managed services). Needs Deploy on the project.

  • guideHow to use The Deployerread-only

    The playbooks for agents: what The Deployer does, which tool fits which job, the order of an end-to-end deploy, what code needs to deploy and how to fix it locally, how to fix a failed deployment, and domains, scaling, env, databases, access, environments, servers, adoption and teams. Read topic overview first, and end_to_end before a first deploy. No API key needed.

  • launchLaunch a projectcan change or delete data

    The first (or a full) deployment of a project into the person's cloud, once a hosting plan is selected. Without confirm it changes nothing and answers with the plan and its monthly cost: tell the person and wait for their yes. Then call again with confirm=true. It creates resources their cloud provider bills them for. Takes 5 to 20 minutes; follow it with deployment. Needs a key with Operate access.

  • logsDeployment logsread-only

    Shows the log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed. Set errors_only to see only errors and warnings. The lines are the build's and the app's own output. Changes nothing. Needs an API key.

  • plan_deployPlan a deployread-only

    Plans deploying a repository with the user's account on The Deployer: checks the repository like check_repo, then adds the user's connected cloud and git accounts, any project they already have for it, and the next steps, with links. Changes nothing. Needs an API key.

  • projectProject in depth, with the next stepread-only

    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: the exact next call to make. Call it after every step of a deploy. Changes nothing.

  • redeployRedeploy a live projectcan change or delete data

    Puts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer. It changes a live app, so confirm with the user first. Only for a project that's already live; a project's first deployment is launch. Takes a few minutes; follow it with deployment. Works with any API key.

  • request_done_for_youRequest 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. Needs an API key.

Show 2 more tools
  • set_envSet env variables

    Sets (or deletes) env variable values for the service a project deploys. Values are stored encrypted and never shown back to any agent. Other values are kept. On a live project the services whose env changed are redeployed (so confirm first); otherwise they apply on the next deployment. Read values from the person's local .env only with their OK; never invent secrets. Multi-line values are credential files (guide topic env). Needs a key with Operate access.

  • statusProject statusread-only

    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. Needs an API key.

Signals

Stars
0
Forks
0
Open issues
0
Last commit
Sep 16, 2026 (1 month ago)
Last release
Sep 14, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
com.thedploy/deployer
Version
0.1.1
Auth
Bearer token, API key
Packages
npm thedeployer-mcp
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

The Deployer MCP server. Agent Mart. https://agentmart.dev/connectors/thedploy-com-deployer (last updated 2026-10-24)