Log inSubmit server
DigitalOcean MCP Server logo

DigitalOcean MCP Server

Manage DigitalOcean apps, infrastructure, databases, Kubernetes, registries, and account resources through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install DigitalOcean MCP Server

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "digitalocean-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@digitalocean/mcp"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 11/11/2026, 12:00:31 AM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.digitalocean.com/mcp

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

DigitalOcean MCP Server connects MCP-compatible agents to DigitalOcean through hosted HTTPS endpoints or the local @digitalocean/mcp package. It exposes operations for App Platform, Droplets, managed databases, Kubernetes, Container Registry, MicroVMs, account resources, and selected GenAI services. Hosted deployments support OAuth 2.0 or bearer-token authentication, while local installations use DIGITALOCEAN_API_TOKEN. Use it when an agent needs to inspect, deploy, modify, or troubleshoot DigitalOcean resources.

Use cases

  • Deploy and configure App Platform applications
  • Create and resize DigitalOcean Droplets
  • Provision and monitor managed database clusters
  • Inspect Kubernetes clusters and node pools
  • Investigate account, inference, or runtime resources

Key features

  • Hosted HTTPS MCP endpoints by DigitalOcean product
  • Local execution through @digitalocean/mcp
  • OAuth 2.0 authentication for supported clients
  • API-token authentication for remote and local use
  • App, infrastructure, database, registry, and GenAI management

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars137Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.

How DigitalOcean MCP Server works

What DigitalOcean MCP Server does

DigitalOcean MCP Server provides an MCP interface to the DigitalOcean API for managing cloud resources and carrying out operational tasks. It is aimed at agent workflows that need to work with DigitalOcean infrastructure rather than only retrieve documentation.

The available hosted services are split by product area. App Platform covers applications, deployments, and configuration. Other endpoints handle accounts, managed databases, Kubernetes clusters and node pools, Droplets, MicroVMs, Container Registry resources, batch inference jobs, Signals sessions, Harness Runtime configurations, and custom GenAI models. The service-oriented layout lets a client connect to one endpoint or configure several at the same time.

How it works

The project is built with the godo DigitalOcean API library and the MCP framework for Go. It can be used remotely through standalone HTTPS MCP endpoints or run locally through the @digitalocean/mcp package.

Remote connections support OAuth 2.0, which sends the user through a DigitalOcean sign-in flow, as well as API-token authentication with a bearer header. Local use authenticates with a DigitalOcean personal access token supplied through an environment variable. The hosted endpoints can be selected independently, so a client can add only the DigitalOcean product services it needs.

Setup and configuration

For the hosted deployment, add the relevant MCP endpoint to a compatible client. OAuth is the recommended authentication method for clients that support it, including recent Claude and Cursor versions. Clients without OAuth support can send a DigitalOcean API token as an Authorization: Bearer header.

For local execution, install and run the @digitalocean/mcp package and set DIGITALOCEAN_API_TOKEN in the process environment. The token is created from the DigitalOcean API Tokens page, where it can be given an expiry and selected scopes. Store it in a shell environment or a protected .env file, and exclude that file from version control. Do not place the token directly in an MCP or editor configuration file.

Tools and capabilities

The hosted service catalog includes these resource areas:

  • Manage App Platform applications, deployments, and configurations.
  • Inspect account details, billing, balances, invoices, and SSH keys.
  • Provision, manage, and monitor PostgreSQL, MySQL, Redis, and other managed database clusters.
  • Create and manage Kubernetes clusters and node pools.
  • Create, resize, snapshot, and monitor Droplets.
  • Create, pause, resume, inspect, execute commands in, and delete MicroVMs, including file operations and checkpoints.
  • Manage Container Registry repositories, tags, manifests, and garbage collection.
  • Create and monitor batch inference jobs and inspect related GenAI, Signals, Harness Runtime, and custom-model resources.

Limitations and notes

Operations are performed against the connected DigitalOcean account, so token scopes and account permissions affect what an agent can do. MCP access to an account carries security risk; protect credentials and avoid exposing them through committed configuration files. Hosted and local authentication differ, so the client must support OAuth or bearer headers for remote use, while local execution requires the environment variable.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about DigitalOcean MCP Server

DigitalOcean MCP Server is an MCP server that connects AI agents to the DigitalOcean API. Its tools manage App Platform apps, Droplets, databases, Kubernetes, Container Registry, MicroVMs, account resources, and selected GenAI services through hosted endpoints or the local package.

Use a hosted DigitalOcean MCP endpoint or run the local @digitalocean/mcp package. Remote clients connect over HTTPS, while local execution uses DIGITALOCEAN_API_TOKEN. Store the token in the environment rather than directly in an MCP or editor configuration file.

DigitalOcean MCP Server supports OAuth 2.0 and API-token authentication for hosted connections, while local execution uses DIGITALOCEAN_API_TOKEN. OAuth opens a DigitalOcean sign-in flow in supported clients; other remote clients can send a bearer token.

Yes, recent Cursor versions support the hosted server's OAuth flow. Cursor can connect to the relevant HTTPS MCP endpoint, and clients without OAuth support can use a DigitalOcean API token through bearer-token authentication.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDigitalOcean MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/digitalocean-mcp-server?style=directory)](https://allmcps.com/mcp/digitalocean-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/digitalocean-mcp-server"><img src="https://allmcps.com/api/badge/digitalocean-mcp-server?style=directory" alt="DigitalOcean MCP Server on AllMCPs" /></a>