topmcps
Browse MCPs
DigitalOcean

DigitalOcean

Official

Manage Droplets, App Platform, Kubernetes, and Spaces from an AI agent.

Score 81(?)DigitalOceanMIT108Verified Top MCPs for Web Hosting →
InstallView on GitHub

Quick answer

What it does

Exposes DigitalOcean Apps, Droplets, Kubernetes, Spaces, Databases, Networking, Functions, and inference services as MCP tools via remote HTTP or local stdio.

Best for

  • App Platform deploys
  • Droplet provisioning and ops
  • Kubernetes (DOKS) management
  • Spaces (S3-compatible) ops

Not for

  • Single-purpose workflows where per-service scoping matters
  • Production ops without a confirmation gate

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export DIGITALOCEAN_API_TOKEN=your_do_api_token
claude mcp add digitalocean -- npx @digitalocean/mcp --services apps

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "@digitalocean/mcp",
            "--services",
            "apps"
          ],
          "env": {
            "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.digitalocean]
command = "npx"
args = [
  "@digitalocean/mcp",
  "--services",
  "apps",
]
env = { DIGITALOCEAN_API_TOKEN = "${DIGITALOCEAN_API_TOKEN}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "digitalocean": {
      "command": {
        "path": "npx",
        "args": [
          "@digitalocean/mcp",
          "--services",
          "apps"
        ]
      },
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Settings → Connectors (remote URL)
    {
  "name": "DigitalOcean",
  "transport": "http",
  "url": "https://apps.mcp.digitalocean.com/mcp"
}

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

  2. 2

    Set required secrets

    Set DIGITALOCEAN_API_TOKEN in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. web hosting work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-hosting
Compare DigitalOcean against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare DigitalOcean MCP vs [Fly.io MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/digitalocean
- top-mcps.com listing for Fly.io
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the DigitalOcean MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/digitalocean (fetch https://top-mcps.com/mcp/digitalocean.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (DIGITALOCEAN_API_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Web Hosting MCPs

Other tools in the same category worth evaluating.

Cloudflare
Official

Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.

cloudflare, edge, workers, dns
10 minMedium
Railway
Official

Spin up Railway projects, services, and deploys via remote MCP with OAuth.

railway, hosting, deployment, paas
2 minLow
Fly.io
Official

Run `fly mcp server` to expose flyctl operations to AI agents.

fly-io, hosting, flyctl, edge
5 minMedium

Compared with DigitalOcean

Side-by-side breakdowns for the choices people most often weigh against this MCP.

DigitalOceanvsCloudflareDigitalOceanvsHerokuDigitalOceanvsFly.ioDigitalOceanvsNetlify

Exploring Top MCPs for Web Hosting? See all Web Hosting MCPs →