# DigitalOcean

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

[Canonical HTML page](https://top-mcps.com/mcp/digitalocean) · [server.json](https://top-mcps.com/mcp/digitalocean.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

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

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

### Claude Code — `CLI or .mcp.json`

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

```shell
# export DIGITALOCEAN_API_TOKEN=your_do_api_token
claude mcp add digitalocean -- npx @digitalocean/mcp --services apps
```

### Cursor — `.cursor/mcp.json`

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

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

### VS Code — `.vscode/mcp.json`

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

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

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

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

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

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

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

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

### Codex CLI — `~/.codex/config.toml`

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

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

### Zed — `~/.config/zed/settings.json`

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

```jsonc
{
  "context_servers": {
    "digitalocean": {
      "command": {
        "path": "npx",
        "args": [
          "@digitalocean/mcp",
          "--services",
          "apps"
        ]
      },
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors (remote URL)`

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.

```json
{
  "name": "DigitalOcean",
  "transport": "http",
  "url": "https://apps.mcp.digitalocean.com/mcp"
}
```

## At a glance

- **Maintainer:** DigitalOcean
- **Transport:** Streamable HTTP, stdio
- **Auth model:** API key
- **Required secrets:** DIGITALOCEAN_API_TOKEN
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, DigitalOcean accounts
- **License:** MIT
- **Language:** Go
- **Latest version:** latest
- **Last verified:** 2026-05-27
- **GitHub stars:** 108 (fetched 2026-06-02T11:55:52.222Z)
- **Score:** 81/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/digitalocean-labs/mcp-digitalocean

## 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
- Networking, Functions, Inference services

**Not for:**
- Single-purpose workflows where per-service scoping matters
- Production ops without a confirmation gate
- Customers using cloud providers outside DigitalOcean

## Description

The official DigitalOcean MCP covers 16 services — Apps, Droplets, DOKS Kubernetes, Spaces, Databases, Networking, and more. Available as a remote MCP at mcp.digitalocean.com (per-service URLs) or as a local npx install.

## Why it matters

DigitalOcean is the default cloud for many small-to-mid SaaS teams. One MCP covering 16 services lets a single install handle deploy, infra, storage, and networking.

## Key features

- Remote MCP per service (e.g. apps.mcp.digitalocean.com/mcp)
- Local stdio install via @digitalocean/mcp
- 16 services covered — Apps, Droplets, DOKS, Spaces, more
- Bearer-token auth
- MIT, Go

## FAQ

### Are services scoped independently?

Yes — each service has its own remote MCP URL (apps.mcp..., droplets.mcp...) and the local install takes a `--services` flag.

### How are tokens scoped?

Bearer token via `DIGITALOCEAN_API_TOKEN`. Issue a least-privilege token from cloud.digitalocean.com/account/api/tokens.

### Open source?

Yes — MIT-licensed at github.com/digitalocean-labs/mcp-digitalocean.

## Changelog

- **2026-05-27** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-10-15** — Initial directory listing.