⚠️ ARCHIVE NOTICE
This repository has been archived. Please use @digitalocean-labs/mcp-digitalocean

This MCP server exposes DigitalOcean App Platform functionality through standardized tools that can be used by any MCP client, including Claude Desktop and Cursor. It enables AI assistants to directly manage your DigitalOcean apps without writing code or memorizing API endpoints.

• 🚀 What Can You Do With It?

• 🧰 Prerequisites

• ⚙️ Setting up your DigitalOcean MCP Server

  • Generate Your API Token
  • Add the Server to Your MCP Client
  • Claude Desktop
  • Cursor
  • Windsurf Setup

• 💬 Example Prompts

• 🛠 Available Tools

• 🧯 Troubleshooting

• 🤝 Contributing

• 📄 License

You can now do things like:

• Deploy a new app from a GitHub repo
• Quickly redeploy an existing app with the latest changes
• See logs, restart components, or delete old environments
• Check available regions and create apps based on what’s supported
• Build and deploy an app from scratch, entirely through your assistant

...and more!

To use the DigitalOcean MCP Server, you’ll need:

• Node.js (≥ 12) & npm
• A DigitalOcean Personal Access Token with App Platform scopes
• A supported MCP client:
  • Claude Desktop (v1.9+)
  • Claude Code
  • Cursor
  • Windsurf
• (Optional but helpful): GitHub CLI (gh) - useful for cloning repos, creating projects, and working with GitHub-based apps.

💡 You do not need to install anything—this server runs via npx, with just a one-line config added to your MCP client.

Head to DigitalOcean’s API settings and create a new Personal Access Token with App Platform permissions.

Add this JSON snippet to your client’s MCP config file:

{
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": ["@digitalocean/mcp"],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "YOUR_DO_TOKEN"
      }
    }
  }
}

Here’s what each part of the snippet does:

• • command: how to launch the server (npx or full path)
• • args: the package name
• • env: insert your DO token here

Then follow the instructions for your specific tool:

1. Go to Settings → Developer → Edit Config
2. Add the snippet above to claude_desktop_config.json
3. Replace YOUR_DO_TOKEN with your token
4. Save and restart Claude Desktop
5. You'll see “digitalocean” listed as an available server

Setting up DigitalOcean MCP Server in Claude Desktop

1. Go to Settings → Cursor Settings → MCP → Add a new global MCP server
2. Cursor will open ~/.cursor/mcp.json
3. Add the snippet above to this json file
4. Replace YOUR_DO_TOKEN with your token
5. Save, and return to MCP Settings.
6. You should now see “digitalocean” in Cursor’s MCP settings

Setting up DigitalOcean MCP Server in Cursor

1. In Windsurf: Settings → Windsurf Settings → Cascade → MCP → Add Server → Add custom server
2. Windsurf will open ~/.codeium/windsurf/mcp_config.json
3. Add the snippet above to this json file
4. Replace YOUR_DO_TOKEN with your token
5. Save, and return to MCP Settings.
6. You should now see “digitalocean” in Windsurf's MCP settings

Setting up DigitalOcean MCP Server in Windsurf

Once it’s configured, try asking your assistant:

“List all active apps on my account”
“Create a new app from https://github.com/do-community/do-one-click-deploy-flask with 1GB RAM in NYC3”
“Show logs for checkout-service”
“Cancel the current deployment for marketing-site”
“Delete the old `staging-env` app”

The assistant will send the request → the MCP server talks to DigitalOcean → you get structured results, ready to act on.

• Make sure your JSON config is saved and valid
• Restart your MCP client (Claude, Cursor, Windsurf)

• Check that it has App Platform access
• Try generating a fresh one

• No trailing commas
• No comments allowed in JSON

You can also test the server directly by running:

npx @digitalocean/mcp

We’d love your help improving this! Bug reports, new features, and docs improvements are all welcome.

1. Fork this repo
2. Create a branch (git checkout -b feature/awesome-tool)
3. Open a PR

This project is licensed under the MIT License.