The Deployer

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

¿Debería usar esto?

Calidad y seguridad

B
Calidad de la descripción
100%
Integridad del esquema
92%
Calidad de los nombres
83%
Riesgo de envenenamiento
40%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (4)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainen api_read
  • MEDIUMTool description contains URL to non-standard domainen api
  • LOWTool description contains role marker that could confuse chat modelsen request_done_for_you

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~4,086Tokens (definiciones de herramientas)
~942 BTamaño de respuesta típico
Impacto significativo en la atención (3.19% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "deployer": {
      "command": "npx",
      "args": [
        "thedeployer-mcp"
      ]
    }
  }
}

Paquetes ejecutables

npmthedeployer-mcp0.1.1stdio

Puntos de conexión remotos

https://app.thedploy.com/api/v1/mcpstreamable-http
https://app.thedploy.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (23)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢check_repo(repo, check_id)

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.

Esquema de entrada

{
  "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"
    }
  }
}
🟢plan_deploy(repo, cloud)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "owner/name, or the repository's URL"
    },
    "cloud": {
      "type": "string",
      "enum": [
        "digitalocean",
        "aws",
        "gcp",
        "azure"
      ],
      "description": "The cloud to plan for. Optional."
    }
  },
  "required": [
    "repo"
  ]
}
🟢status(project, workspace)

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.

Esquema de entrada

{
  "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."
    }
  }
}
🟢logs(project, deployment_id, lines, errors_only, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository. Optional with one project."
    },
    "deployment_id": {
      "type": "integer",
      "description": "A specific deployment, instead of the latest"
    },
    "lines": {
      "type": "integer",
      "minimum": 1,
      "maximum": 400,
      "description": "How many lines, newest last. Default 80."
    },
    "errors_only": {
      "type": "boolean",
      "description": "Only errors and warnings"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
🔴redeploy(project, workspace)

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.

Esquema de entrada

{
  "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."
    }
  }
}
⚪request_done_for_you(offer, repo, note)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "offer": {
      "type": "string",
      "enum": [
        "launch",
        "launch_secure",
        "move"
      ]
    },
    "repo": {
      "type": "string",
      "description": "The repository, if there is one"
    },
    "note": {
      "type": "string",
      "description": "Anything the team should know, such as the current host or a deadline"
    }
  },
  "required": [
    "offer"
  ]
}
🟢guide(topic)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "enum": [
        "overview",
        "end_to_end",
        "readiness",
        "fix_failed_deploy",
        "env",
        "domains",
        "scaling",
        "services",
        "access",
        "environments",
        "servers",
        "adopt",
        "team"
      ],
      "description": "Default overview"
    }
  }
}
🟢account(workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
🟢project(project, workspace)

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.

Esquema de entrada

{
  "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."
    }
  }
}
🟢deployment(project, deployment_id, wait_seconds, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository. Optional with one project."
    },
    "deployment_id": {
      "type": "integer",
      "description": "A specific deployment, instead of the latest"
    },
    "wait_seconds": {
      "type": "integer",
      "minimum": 0,
      "maximum": 120,
      "description": "Seconds to wait for the status or step to change"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  }
}
🟢diagnose(project, check, container, node, lines, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "check": {
      "type": "string",
      "enum": [
        "url",
        "containers",
        "resources",
        "web_server",
        "app_logs"
      ]
    },
    "container": {
      "type": "string",
      "description": "For app_logs: one container's name"
    },
    "node": {
      "type": "string",
      "description": "The server, default app-1"
    },
    "lines": {
      "type": "integer",
      "minimum": 10,
      "maximum": 400
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "project"
  ]
}
🟡create_project(repo, branch, name, cloud, cloud_connection_id, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "owner/name, or the repository's URL"
    },
    "branch": {
      "type": "string",
      "description": "The branch to deploy. Default: the repository's default"
    },
    "name": {
      "type": "string",
      "description": "The project's name. Default: the repository's name"
    },
    "cloud": {
      "type": "string",
      "enum": [
        "digitalocean",
        "aws",
        "gcp",
        "azure"
      ]
    },
    "cloud_connection_id": {
      "type": "integer"
    },
    "git_connection_id": {
      "type": "integer"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "repo"
  ]
}
🟡set_env(project, values, delete, service, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The project's id, name or repository (owner/name)."
    },
    "values": {
      "type": "object",
      "additionalProperties": {
        "type": "string"
      },
      "description": "Names to values, e.g. {\"API_URL\": \"https://...\"}"
    },
    "delete": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Names to remove"
    },
    "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."
    }
  },
  "required": [
    "project"
  ]
}
🔴launch(project, confirm, confirm_cost, workspace)

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.

Esquema de entrada

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

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "group": {
      "type": "string",
      "enum": [
        "account",
        "connections",
        "projects",
        "env",
        "build",
        "code",
        "architecture",
        "deploy",
        "fixes",
        "domains",
        "scaling",
        "access",
        "services",
        "environments",
        "blueprints",
        "servers",
        "adopt",
        "team"
      ]
    }
  }
}
🟢api_schema(path)

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

Esquema de entrada

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "description": "e.g. /projects/12/scaling"
    }
  },
  "required": [
    "path"
  ]
}
🟢api_read(path, query, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "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."
    }
  },
  "required": [
    "path"
  ]
}
🔴api(method, path, query, body, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "method": {
      "type": "string",
      "enum": [
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
      ]
    },
    "path": {
      "type": "string",
      "description": "The operation's path with ids filled in, e.g. /projects/12/scaling"
    },
    "query": {
      "type": "object",
      "description": "Query parameters"
    },
    "body": {
      "type": "object",
      "description": "The JSON body, for POST, PUT and PATCH"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "method",
    "path"
  ]
}
🟢fixes(project, workspace)

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.

Esquema de entrada

{
  "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."
    }
  }
}
🟢fix(id, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The fix request's id, fr_..."
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "id"
  ]
}
⚪claim_fix(id, workspace)

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

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "id"
  ]
}
🟡report_fix(id, branch, sha, note, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "branch": {
      "type": "string",
      "description": "The branch the fix was pushed to"
    },
    "sha": {
      "type": "string",
      "description": "The pushed commit's sha"
    },
    "note": {
      "type": "string",
      "description": "What changed, in a sentence or two"
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "id",
    "branch",
    "sha"
  ]
}
🟢fix_status(id, wait_seconds, workspace)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "wait_seconds": {
      "type": "integer",
      "minimum": 0,
      "maximum": 120
    },
    "workspace": {
      "type": "string",
      "description": "A teammate's workspace id. Default: your own."
    }
  },
  "required": [
    "id"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada23 herramientas
verificadoversión no registrada17 herramientas
verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas