home / mcp / digitalocean mcp server

DigitalOcean MCP Server

Provides an MCP interface to manage DigitalOcean resources and perform actions via the DigitalOcean API.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "digitalocean-labs-mcp-digitalocean": {
      "url": "https://apps.mcp.digitalocean.com/mcp",
      "headers": {
        "DIGITALOCEAN_API_TOKEN": "YOUR_DO_API_TOKEN"
      }
    }
  }
}

This MCP server provides a unified interface to manage DigitalOcean resources and perform actions via the DigitalOcean API. Use remote MCP endpoints for quick, hosted access or run a local MCP server to customize your workflow and keep tokens securely in your environment. Connect to multiple MCP endpoints to manage apps, databases, droplets, networking, and more from a single client.

How to use

You can connect to multiple remote MCP endpoints to manage your DigitalOcean resources from a single client. Use the remote service URLs to access specific areas such as apps, databases, droplets, and more. If you prefer running locally, you can start an MCP server on your machine and enable only the services you need.

Common usage patterns include listing resources across services, creating new resources, updating configurations, and watching for changes. Environments that expose an API token or Bearer token will apply it to requests, so keep tokens secure and do not expose them in shared configurations.

How to install

Prerequisites you need before installing the MCP server locally are Node.js version 18 or later and npm version 8 or later.

Install locally to run an MCP server that you control. You enable services by passing a list via the --services flag.

Step-by-step local installation and quick test:

# Prerequisites check
node --version
npm --version

# Install and run the MCP server with desired services
npx @digitalocean/mcp --services apps,databases

Configuration and usage notes

You can connect to hosted MCP endpoints or run a local server. When using hosted endpoints, you typically pass an Authorization header with a Bearer token. For local runs, you provide the DigitalOcean API token via an environment variable.

Remote MCP endpoints and local alternatives

Remote MCP endpoints let you manage DigitalOcean resources without running a local server. Each service is exposed at a dedicated URL and can be added to your MCP client.

Examples of remote endpoints you can connect to include apps, databases, and droplets.

Security and troubleshooting

Ensure your API token or Bearer token is kept secure. If you encounter authentication errors, verify token scope and expiry. Check that the correct token is used in your client configuration.

If you run into connectivity issues, verify network access to the remote MCP URL or ensure your local environment can access the DigitalOcean API.

Tools and capabilities overview

This MCP server exposes tools to deploy apps, manage droplets, configure domains, create databases, and perform many other actions across DigitalOcean services.

Examples of common tool names you might use include app-create, app-list, app-delete, droplet-resize, key-create, domain-create, and cdn-flush-cache.

Available tools

app-create

Create a new DigitalOcean App from a source repository or definition.

app-list

List all Apps in the account or based on filters.

app-delete

Delete an App by ID or name.

droplet-resize

Resize an existing Droplet to a new plan or size.

key-create

Add a new SSH key to the account.

domain-create

Create a new DNS domain entry.

cdn-flush-cache

Flush CDN cache for a domain or resource.

vpc-peering-create

Create a VPC peering connection between resources.

vpc-peering-delete

Delete a VPC peering connection.