The Deployer

by thedploy.comcom.thedploy/deployerv0.3.0

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

  • Remote endpoint
  • No known advisories
  • MIT

Uptime

Checked  · every day

100%from 4 days of checks

Up without downtime on 4 of 4 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 2293 ms, slowest 5% 2604 ms for the handshake and the tool list, over 30 days.

3000 ms1500 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

23 tools at the last answer; the list changed on 1 Nov.

Every day
DayResultChecksMedian
3 Nov (today)No downtime12283 ms
2 NovNo downtime1of 12249 ms
1 NovNo downtime1of 12298 ms
31 OctNo downtime22269 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):

{
  "mcpServers": {
    "deployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server The Deployer (`com.thedploy/deployer`)

Its page: https://plug.directory/servers/com.thedploy/deployer

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://app.thedploy.com/api/v1/mcp
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http deployer https://app.thedploy.com/api/v1/mcp
```

## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "deployer": {
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "deployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "deployer": {
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## Cline

Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):

```json
{
  "mcpServers": {
    "deployer": {
      "type": "streamableHttp",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "deployer"
    type: streamable-http
    url: "https://app.thedploy.com/api/v1/mcp"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "deployer":
    type: streamable_http
    name: "deployer"
    enabled: true
    uri: "https://app.thedploy.com/api/v1/mcp"
    headers: {}
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "deployer": {
      "httpUrl": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## Codex

Run in a terminal:

```sh
codex mcp add deployer --url https://app.thedploy.com/api/v1/mcp
```

## mcp-client-cli, TUUI, BoltAI

This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "deployer": {
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "deployer": {
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## AnythingLLM

Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

```json
{
  "mcpServers": {
    "deployer": {
      "type": "streamable",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

## Augment Code

Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):

```json
{
  "mcpServers": {
    "deployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

Known advisories

None known for its packages.

Checked 2026-10-28 against OSV.dev and deps.dev.

From the publisher's entry in the Official MCP Registry (the registry entry)and from npm. Report a problem