MCP Directory

DigitalOcean MCP

Official

DigitalOcean's App Platform MCP: deploy apps, tail logs, roll back. Archived — superseded by mcp-digitalocean.

Unverified
stdio (local)
API key
Stale
TypeScript
View repo 80 npm

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run
npx @digitalocean/mcp

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

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

About DigitalOcean MCP

The server wraps DigitalOcean's App Platform API in MCP tools so an assistant can ship and operate apps without the dashboard or doctl. You generate a Personal Access Token with App Platform scopes at cloud.digitalocean.com/account/api/tokens, drop the three-line npx config into Claude Desktop (v1.9+), Claude Code, Cursor or Windsurf, and prompts like 'create a new app from this GitHub repo with 1GB RAM in NYC3' become API calls.

The tool set covers the full app lifecycle: apps (list/create/get/update/delete/restart), deployments (list/create/get/cancel), logs (active deployment logs plus downloadable archives), infrastructure discovery (regions, instance sizes), alert destinations, bandwidth metrics, and app spec validation. Rollbacks are a proper four-step flow — validate, rollback, commit, revert — rather than a single destructive call.

The important caveat is lifecycle status: DigitalOcean archived this repo and consolidated MCP work into digitalocean-labs/mcp-digitalocean, which extends coverage beyond App Platform. The archived package keeps working for App Platform tasks and its narrow surface is easy to audit, but new integrations should start on the successor.

Practical notes: Node.js ≥ 12 is the only local requirement, npx @digitalocean/mcp run directly in a terminal is the quickest smoke test, and the GitHub CLI is handy alongside it for repo-based deploy flows.

Tools & capabilities (23)

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.

get_deployment

Get details of a deployment.

cancel_deployment

Cancel an in-progress deployment.

retrieve_active_deployment_logs

Fetch logs from the active deployment.

download_logs

Download log archives.

list_app_regions

List available App Platform regions.

list_instance_sizes

List available instance sizes.

list_app_alerts

List configured alerts for an app.

update_app_alert_destinations

Update alert destinations.

validate_app_rollback

Check whether a rollback is possible.

rollback_app

Roll an app back to a previous deployment.

commit_app_rollback

Commit a rollback permanently.

revert_app_rollback

Revert a rollback.

get_app_bandwidth_daily_metrics

Daily bandwidth metrics for one app.

get_all_app_bandwidth_daily_metrics

Daily bandwidth metrics across all apps.

validate_app_spec

Validate an app spec before deploying.

What this server can do

DigitalOcean MCP provides tools for these capabilities — tap one to see every MCP server that does the same:

Manage Git reposDeploy & manage cloud infra

When to use it

  • Deploy a new App Platform app straight from a GitHub repo by prompt
  • Tail active deployment logs and restart a misbehaving component
  • Validate and execute a rollback when a deploy goes bad
  • Audit regions, instance sizes and bandwidth metrics across your apps

Quick setup

  1. 1Create a Personal Access Token with App Platform scopes at cloud.digitalocean.com/account/api/tokens
  2. 2Add the npx @digitalocean/mcp config block with DIGITALOCEAN_API_TOKEN to claude_desktop_config.json or ~/.cursor/mcp.json
  3. 3Restart the client and confirm digitalocean appears in the MCP server list
  4. 4Smoke-test with: List all active apps on my account
  5. 5For new projects, evaluate the successor @digitalocean-labs/mcp-digitalocean first

Security notes

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 FAQ

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.

#digitalocean#official#archived#app-platform#deployment

Alternatives to DigitalOcean MCP

Compare all alternatives →
GitHub MCP Server
DevOps & Cloud
31k

GitHub's official server for repos, issues, PRs, and Actions — local Docker or hosted remote.

Featured
Verified
stdio (local)
API key
Go
7 tools
Updated 20 days agoRepo
AWS API MCP Server
DevOps & Cloud
9.3k

Official AWS Labs server that lets agents call any AWS API via the AWS CLI surface.

Verified
stdio (local)
API key
Python
3 tools
Updated 22 days agoRepo
kubefwd
DevOps & Cloud
4.1k

Bulk Kubernetes port forwarding with an MCP server that lets AI assistants forward services, inspect pods, and monitor traffic.

Unverified
stdio (local)
No auth
Go
28 tools
Updated 14 days agoRepo

Compare DigitalOcean MCP with:

vs GitHub MCP Servervs AWS API MCP Servervs kubefwdvs Radar