MCP DigitalOcean Integration is an open-source project that provides a comprehensive interface for managing DigitalOcean resources and performing actions using the DigitalOcean API. Built on top of the godo library and the MCP framework, this project exposes a wide range of tools to simplify cloud infrastructure management.

DISCLAIMER: "Use of MCP technology to interact with your DigitalOcean account can come with risks"

• Node.js (v18 or later)
• NPM (v8 or later)

You can find installation guides at https://nodejs.org/en/download

Verify your installation:

node --version
npm --version

To verify the MCP server works correctly, you can test it directly from the command line:

npx @digitalocean/mcp --services apps

To add the DigitalOcean MCP server to Claude Code, run the following command in your terminal:

claude mcp add digitalocean-mcp \
  -e DIGITALOCEAN_API_TOKEN=YOUR_DO_API_TOKEN \
  -- npx @digitalocean/mcp --services apps,databases

This will:

• Add the MCP server under the default (local) scope — meaning it's only available inside the current folder.
• Register it with the name digitalocean-mcp.
• Enable the apps and databases services.
• Pass your DigitalOcean API token securely to the server.
• Store the configuration in your global Claude config at ~/.claude.json, scoped to the current folder.

To confirm it's been added:

claude mcp list

To inspect details:

claude mcp get digitalocean-mcp

To remove it:

claude mcp remove digitalocean-mcp

Alternatively, add the following to your claude_desktop_config.json file.

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

Local scope is great when you're testing or only using the server in one project. User scope is better if you want it available everywhere.

If you'd like to make the server available globally (so you don't have to re-add it in each project), you can use the user scope:

claude mcp add -s user digitalocean-mcp-user-scope \
  -e DIGITALOCEAN_API_TOKEN=YOUR_DO_API_TOKEN \
  -- npx @digitalocean/mcp --services apps,databases

This will:

• Make the server available in all folders, not just the one you're in
• Scope it to your user account
• Store it in your global Claude config at ~/.claude.json

To remove it:

claude mcp remove -s user digitalocean-mcp-user-scope

Add the following to your Cursor settings file located at ~/.cursor/config.json:

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

1. Open Cursor and open Command Pallet ( Shift + ⌘ + P on Mac or Ctrl+ Shift + P on Windows/Linux )
2. Search for "MCP" in the command pallet search bar
3. Select "View: Open MCP Settings"
4. Select "Tools & Integrations" from the left sidebar
5. You should see "digitalocean" listed under Available MCP Servers
6. Click on "N tools enabled" (N is the number of tools currently enabled).

To check MCP server logs and debug issues:

1. Open the Command Palette (⌘+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux)
2. Type "Developer: Toggle Developer Tools" and press Enter
3. Navigate to the Console tab to view MCP server logs
4. You'll find MCP related logs as you interact with the MCP server

In Cursor's chat, try asking: "List all my DigitalOcean apps" - this should trigger the MCP server to fetch your apps if properly configured. If you are getting an 401 error or authentication related errors, it is likely due to misconfiguring your access token.

Add the following to your VS Code MCP configuration file:

{
  "mcp": {
    "inputs": [],
    "servers": {
      "mcpDigitalOcean": {
        "command": "npx",
        "args": [
          "@digitalocean/mcp",
          "--services",
          "apps"
        ],
        "env": {
          "DIGITALOCEAN_API_TOKEN": "YOUR_API_TOKEN"
        }
      }
    }
  }
}

1. Open Cursor and open Command Pallet ( Shift + ⌘ + P on Mac or Ctrl+ Shift + P on Windows/Linux )
2. Search for "MCP" in the command pallet search bar
3. Select "MCP: List Servers"
4. Verify that "mcpDigitalOcean" appears in the list of configured servers

To see what tools are available from the MCP server:

1. Open the Command Palette (⌘+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux)
2. Select "Agent" mode in the chatbox,
3. Click "Configure tools" on the right, and check for digitalocean related tools under MCP Server: mcpDigitalocean. You should be able to list available tools like app-create, app-list, app-delete, etc.

To troubleshoot MCP connections:

1. Open the Command Palette (⌘+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux)
2. Type "Developer: Toggle Developer Tools" and press Enter
3. Navigate to the Console tab to view MCP server logs
4. Check for connection status and error messages

If you are getting an 401 error or authentication related errors, it is likely due to misconfiguring your access token.

To configure tools, you use the --services flag to specify which service you want to enable. It is highly recommended to only enable the services you need to reduce context size and improve accuracy. See list of supported services below.

npx @digitalocean/mcp --services apps,droplets

The MCP DigitalOcean Integration supports the following services, allowing users to manage their DigitalOcean infrastructure effectively

Each service provides a detailed README describing all available tools, resources, arguments, and example queries. See the following files for full documentation:

• Apps Service
• Droplet Service
• Account Service
• Networking Service
• Databases Service
• Insights Service
• Spaces Service
• Marketplace Service
• DOKS Service

• Deploy an app from a GitHub repo: create-app-from-spec
• Resize a droplet: droplet-resize
• Add a new SSH key: key-create
• Create a new domain: domain-create
• Enable backups on a droplet: droplet-enable-backups
• Flush a CDN cache: cdn-flush-cache
• Create a VPC peering connection: vpc-peering-create
• Delete a VPC peering connection: vpc-peering-delete

Contributions are welcome! If you encounter any issues or have ideas for improvements, feel free to open an issue or submit a pull request.

1. Fork the repository.
2. Create a new branch for your feature or bug fix.
3. Submit a pull request with a clear description of your changes.

This project is licensed under the MIT License. See the LICENSE file for details.