DigitalOcean MCP Server for Claude

Overview

The DigitalOcean MCP Server is DigitalOcean's official Model Context Protocol server. It gives Claude structured access to the DigitalOcean API so you can manage Apps, Droplets, managed Databases, Kubernetes (DOKS), Container Registry, networking, Functions, Spaces, and more — in natural language. It runs locally via npx @digitalocean/mcp (or a hosted remote endpoint) and is licensed under MIT.

Key capabilities

The server exposes tools grouped by service area, selected with the --services flag:

• Apps (App Platform) — list, create, get, update, delete, restart, and deploy apps; tail logs.
• Droplets — manage Droplets, regions, and instance sizes.
• Managed Databases — inspect and manage database clusters.
• Kubernetes (DOKS) & Container Registry (DOCR) — manage clusters and images.
• Networking, Functions, Spaces, Volumes — manage supporting infrastructure.
• Insights & Marketplace — metrics, alerts, and Marketplace resources.

How it compares

Several cloud-platform MCP servers let Claude manage deployments; they differ by platform scope:

Use the DigitalOcean server when your infrastructure runs on DigitalOcean; the Cloudflare and Netlify servers cover their own platforms' primitives.

Installation

Claude Code

claude mcp add digitalocean -e DIGITALOCEAN_API_TOKEN=<your-token> -- \
  npx -y @digitalocean/mcp --services apps,droplets,databases

Claude Desktop

{
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": ["-y", "@digitalocean/mcp", "--services", "apps,droplets,databases"],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "<your-token>"
      }
    }
  }
}

DigitalOcean also offers hosted remote MCP endpoints (for example https://apps.mcp.digitalocean.com/mcp) if you prefer not to run the server locally.

Requirements

• A DigitalOcean account and an API token with appropriate scopes.
• Node.js (for npx), or use a hosted remote endpoint.
• An MCP client (Claude Code or Claude Desktop).

Security

• Scope the DIGITALOCEAN_API_TOKEN to least privilege and enable only the --services you need.
• Tools can create and delete production infrastructure — review destructive actions before running.
• Treat the API token as a secret; keep it in the client config or environment.

Source Verification Notes

Verified on 2026-06-17:

• The official repository github.com/digitalocean-labs/mcp-digitalocean (MIT) documents npx @digitalocean/mcp, the --services selection, the DIGITALOCEAN_API_TOKEN requirement, the hosted remote endpoints, and the service areas listed above.
• DigitalOcean's product documentation describes the underlying App Platform, Droplet, Database, and Kubernetes services.
• Claude Code's MCP documentation describes the connector setup pattern used here.