# DigitalOcean MCP Server [Official] [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/digitalocean-labs/mcp-digitalocean  
**GitHub Stars:** 137  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/digitalocean-mcp-server

## Description
DigitalOcean's official MCP server. Lets agents build, deploy, manage and troubleshoot apps and infrastructure on DigitalOcean, including App Platform, Droplets, databases, networking and Spaces. Use the hosted endpoint with OAuth, or run the @digitalocean/mcp package locally with an API token.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "digitalocean-mcp-server": {
    "command": "npx",
    "args": ["-y","@digitalocean/mcp"],
    "env": {
      "DIGITALOCEAN_API_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `DIGITALOCEAN_API_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/digitalocean-mcp-server/readme_