MCP Directory

How to add DigitalOcean MCP to Claude Desktop

DigitalOcean's App Platform MCP: deploy apps, tail logs, roll back. Archived — superseded by mcp-digitalocean. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 80★ · stdio · apikey · official

Claude Desktop config for DigitalOcean MCP

npx @digitalocean/mcp
{
  "mcpServers": {
    "digitalocean-mcp": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "<your-do-token>"
      }
    }
  }
}

Setup steps

  1. 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
  2. 2Paste the DigitalOcean MCP config below under the top-level "mcpServers" key.
  3. 3Fill in any placeholder secrets (API keys, paths) in the snippet.
  4. 4Save the file, then fully quit and reopen Claude Desktop.
  5. 5Open a chat and confirm DigitalOcean MCP's tools appear under the 🔌 tools menu.

Before you start

  • Node.js 12+ with npm/npx
  • DigitalOcean Personal Access Token with App Platform scopes (cloud.digitalocean.com/account/api/tokens)
  • An MCP client: Claude Desktop v1.9+, Claude Code, Cursor or Windsurf

What DigitalOcean MCP can do in Claude Desktop

list_apps

List all App Platform apps on the account.

create_app

Create a new app, e.g. from a GitHub repo.

get_app

Get details of an app.

update_app

Update an app's spec or settings.

delete_app

Delete an app.

restart_app

Restart an app or its components.

list_deployments

List deployments for an app.

create_deployment

Trigger a new deployment.

Security

This repo is archived: it still runs via npx but receives no updates or security fixes — DigitalOcean's notice points to @digitalocean-labs/mcp-digitalocean as the successor. The DIGITALOCEAN_API_TOKEN you supply can create and delete real apps and deployments, so scope it to App Platform permissions only and rotate it regularly.

DigitalOcean MCP + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the DigitalOcean MCP config there under the "mcpServers" key and restart the client.

Is DigitalOcean MCP safe to use with Claude Desktop?

This repo is archived: it still runs via npx but receives no updates or security fixes — DigitalOcean's notice points to @digitalocean-labs/mcp-digitalocean as the successor. The DIGITALOCEAN_API_TOKEN you supply can create and delete real apps and deployments, so scope it to App Platform permissions only and rotate it regularly.

Is the DigitalOcean MCP server still maintained?

No — the repository is archived. DigitalOcean's archive notice points to digitalocean-labs/mcp-digitalocean as the replacement. The @digitalocean/mcp npm package still runs, but it is frozen: no new features and no security fixes.

Can it manage Droplets or managed databases?

No. This server covers App Platform only: apps, deployments, logs, alerts, rollbacks and bandwidth metrics. For broader DigitalOcean coverage, use the successor project mcp-digitalocean.

Is it safe to keep using an archived server with my DO token?

It works, with a shrinking safety margin: the code runs locally via npx and talks only to DigitalOcean's API, but unpatched issues stay unpatched. Use a token scoped strictly to App Platform, rotate it regularly, and plan a migration to the successor.

View repo Full DigitalOcean MCP page