DigitalOcean

MCP DigitalOcean Integration

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"

Quick start: connect your MCP client to the DigitalOcean MCP Router at https://mcp.digitalocean.com/mcp and sign in with your DigitalOcean account. One endpoint gives you tools for Droplets, App Platform, Kubernetes, managed databases, networking, Spaces, GenAI, and more.

---

Authentication

The hosted (remote) MCP servers support two ways to authenticate:

• OAuth 2.0 (recommended). Just add the server URL — no Authorization header. Your client opens a browser to sign in to DigitalOcean on first use, so there's no token to create, store, or rotate. Supported clients (e.g. recent Claude and Cursor) handle this automatically, and you can skip Steps 1–2 below.
• API token. For local installs or clients without OAuth support, use a DigitalOcean personal access token via an Authorization: Bearer header (remote) or the DIGITALOCEAN_API_TOKEN environment variable (local). See Steps 1–2 below.

---

Security: Never Hardcode Your API Token

WARNING: Do NOT paste your DigitalOcean API token directly into any config file (e.g., claude_desktop_config.json, ~/.cursor/config.json, VS Code settings). If you commit these files to GitHub, your token will be exposed and GitHub will automatically block or revoke it to protect your account.

The safe approach is to store your token in an environment variable on your machine and reference it from your config file. Follow the steps below for your operating system before proceeding with any client installation.

---

Step 1: Set Up Your API Token as an Environment Variable

macOS / Linux

Option A: Set it in your shell profile (Recommended — persists across reboots)

1. Open a terminal.

1. Determine which shell you are using:

   echo $SHELL

• If it outputs /bin/zsh → edit ~/.zshrc
• If it outputs /bin/bash → edit ~/.bashrc or ~/.bash_profile

1. Open the file in a text editor:

   # For zsh (default on macOS Monterey and later)

nano ~/.zshrc

For bash

nano ~/.bashrc

1. Add the following line at the bottom of the file:

   export DIGITALOCEAN_API_TOKEN="your_actual_token_here"

Replace your_actual_token_here with your real token from the DigitalOcean API Tokens page.

1. Save and exit:

• In nano: press Ctrl + O, then Enter to save, then Ctrl + X to exit.

1. Reload your shell to apply the change:

   source ~/.zshrc    # or source ~/.bashrc

1. Verify it is set correctly:

   echo $DIGITALOCEAN_API_TOKEN

You should see your token printed in the terminal.

Option B: Use a .env file (for project-level isolation)

1. In your project root folder, create a .env file:

   touch .env

1. Open it and add:

   DIGITALOCEAN_API_TOKEN=your_actual_token_here

1. Immediately add .env to your .gitignore so it is never committed:

   echo ".env" >> .gitignore

1. To load the .env file into your current terminal session:

   export $(grep -v '^#' .env | xargs)

1. Verify:

   echo $DIGITALOCEAN_API_TOKEN

Note: Option B only sets the variable for the current terminal session. You need to run step 4 each time you open a new terminal. For a permanent solution, use Option A.

---

Windows

Option A: Set it as a System Environment Variable (Recommended — persists across reboots)

1. Open Start Menu and search for "Environment Variables".
2. Click "Edit the system environment variables".
3. In the System Properties dialog, click the "Environment Variables..." button.
4. Under "User variables", click "New...".
5. Fill in:

• Variable name: DIGITALOCEAN_API_TOKEN
• Variable value: your_actual_token_here

1. Click OK on all dialogs to save.
2. Restart your terminal (Command Prompt or PowerShell) for the change to take effect.
3. Verify in PowerShell:

   echo $env:DIGITALOCEAN_API_TOKEN

Or in Command Prompt:

   echo %DIGITALOCEAN_API_TOKEN%

Option B: Set it temporarily in PowerShell (current session only)

$env:DIGITALOCEAN_API_TOKEN = "your_actual_token_here"

Option C: Use a .env file on Windows

1. In your project folder, create a file named .env (no extension) with this content:

   DIGITALOCEAN_API_TOKEN=your_actual_token_here

1. Add .env to your .gitignore:

   .env

1. To load it in PowerShell:

   Get-Content .env | ForEach-Object {

if ($_ -match "^\s*(^#*)=(.*)$") { [System.Environment]::SetEnvironmentVariable($matches[1].Trim(), $matches[2].Trim(), "Process") } }

1. Verify:

   echo $env:DIGITALOCEAN_API_TOKEN

---

Step 2: Get Your DigitalOcean API Token

1. Log in to your DigitalOcean account.
2. Navigate to API → Tokens in the left sidebar, or go directly to: https://cloud.digitalocean.com/account/api/tokens
3. Click "Generate New Token".
4. Give it a name (e.g., mcp-local-dev), set expiry, and choose the required scopes.
5. Copy the token immediately — it will only be shown once.
6. Store it using one of the methods described in Step 1 above.

---

Installation

Remote MCP (Recommended)

The easiest way to get started is to use DigitalOcean's hosted MCP services, so you don't need to run a local server. You can connect in two ways:

• The MCP Router (recommended) — a single endpoint that fronts all of DigitalOcean's first-party MCP services.
• Individual service endpoints — one per service, added only for the services you need. See Available Services.

These servers support OAuth 2.0 (recommended) and API-token auth — see Authentication. Each client section below shows both options.

MCP Router (single endpoint)

Connect once to https://mcp.digitalocean.com/mcp and your MCP client can discover and run tools across every service in the Available Services table. The router forwards your credentials to the service that owns each tool, so you authenticate only once.

The router exposes three tools that work together:

Option A — OAuth (recommended). Add just the URL; your client opens a browser to sign in to DigitalOcean on first use:

{

"mcpServers": { "digitalocean": { "url": "https://mcp.digitalocean.com/mcp" } } }

Option B — API token. Send a DigitalOcean personal access token as a Bearer header. Use your client's variable substitution to keep the token out of the file (see Security):

{

"mcpServers": { "digitalocean": { "url": "https://mcp.digitalocean.com/mcp", "headers": { "Authorization": "Bearer ${DIGITALOCEAN_API_TOKEN}" } } } }

In Claude Code:

claude mcp add --transport http digitalocean --scope user https://mcp.digitalocean.com/mcp

Then run /mcp, select digitalocean, and sign in.

Once connected, ask your assistant things like:

• "List my Droplets in nyc3 and show which ones are powered off."
• "Deploy this repo to App Platform and tell me when the deployment is live."
• "Create a 3-node Kubernetes cluster in sfo3 and give me the kubeconfig."
• "Show the configuration of my managed Postgres cluster and list its recent backups."

Available Services

| genai-inferencerouter | https://genai-infer