The Deployer

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
92%
Calidad de los nombres
87%
Riesgo de envenenamiento
80%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (2)

  • HIGHTool poisoning patterns detected
  • 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

~1,031Tokens (definiciones de herramientas)
~733 BTamaño de respuesta típico
Impacto moderado en la atención (0.81% 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

Qué puede hacer

Inventario de herramientas

Herramientas (6)

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

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

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)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "A project's id, name or repository. Leave out to list them all."
    }
  }
}
🟢logs(project, deployment_id, lines, errors_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.

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"
    }
  }
}
🔴redeploy(project)

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 starts in the app. Takes a few minutes; follow it with status or logs. Needs an API key.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "The live project's id, name or repository. Optional with one project."
    }
  }
}
⚪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. Needs an API key.

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"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas