How to Connect DigitalOcean to Cursor via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → DigitalOcean, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

DigitalOcean + Cursor

Let your AI keep an eye on DigitalOcean: Droplets with CPU and bandwidth metrics, App Platform deployments and logs, managed databases, Kubernetes clusters, volumes, DNS, firewalls, load balancers, balance and invoices. It can power Droplets on or off, take snapshots, redeploy apps and edit DNS records after confirming with you.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

DIGITALOCEAN_TOKEN

Step 1 — Get credentials

1. In the DigitalOcean control panel open API → Tokens (https://cloud.digitalocean.com/account/api/tokens) and click Generate New Token. The token belongs to the team selected at the top of the control panel.
2. Pick an expiry and the scopes. Custom Scopes is the safest choice: read access for account, billing, droplet, app, database, kubernetes, block_storage, domain, firewall, load_balancer, monitoring, snapshot and actions; add droplet update for power actions and snapshots, app update for redeploys, and domain create and update for DNS changes. Read Only covers every read and refuses all changes. Avoid Full Access: it could also destroy resources.
3. Copy the token (it starts with dop_v1_ and is shown once) into DIGITALOCEAN_TOKEN without the word Bearer and install the connector.
4. Check the setup with digitalocean_get_account.

What it does: account, balance and invoices; Droplets with their snapshots and CPU and bandwidth metrics; App Platform apps with their deployments, the steps that failed and links to the logs; managed databases and their replicas; Kubernetes clusters with their node pools; volumes; DNS domains and records; firewalls and load balancers.

Changes ask first: powering a Droplet on or off or rebooting it (digitalocean_power_droplet), taking a snapshot (digitalocean_snapshot_droplet, billed per GB per month), redeploying an app (digitalocean_create_app_deployment) and adding or changing DNS records (digitalocean_create_domain_record, digitalocean_update_domain_record) all touch things people rely on. Before each one the AI shows you the resource and the change and waits for your yes, then follows the action with digitalocean_get_action until it is done.

Nothing destroys resources: deleting Droplets, apps, databases, clusters or volumes is not offered at all. digitalocean_delete_domain_record is switched off at install; an admin turns it on deliberately.

Secrets stay in DigitalOcean: database tools return host and port but never passwords, connection strings or certificates; app tools leave out environment variables; Kubernetes tools return no kubeconfig. The log links from digitalocean_get_app_logs_url are temporary, but anyone who has them can read the logs.

Metrics: CPU and bandwidth metrics need the monitoring agent on the Droplet. CPU values are cumulative seconds per mode, so the AI works out how busy the Droplet was from the change between two points.

Common errors: 401 Unable to authenticate you: the token is wrong, expired or revoked. 403: the token lacks the scope for this call (for example billing:read for the balance, or an update scope for a change); generate a token with that scope. 404: no such resource in this team. 422: a value is invalid, for example a Droplet that is already off or a DNS record that clashes with another. 429: more than 5,000 requests per hour or 250 per minute; wait.

The connector does not create, resize or destroy Droplets, apps, databases, clusters, volumes, firewalls or load balancers, does not change app settings, environment variables or database users, and does not cover Spaces, the container registry, Functions, GenAI or reserved IPs.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Cursor

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:

{
  "mcpServers": {
    "anythingmcp": {
      "url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart Cursor.
3. Open Cursor → Settings → MCP and check that anythingmcp is listed and connected.
4. Start chatting: the agent can now call the DigitalOcean tools.

Available tools

Example prompts

• "List my Droplets with region, size and status, and tell me which ones are switched off but still billed."
• "Why did the last deployment of my App Platform app fail? Show me the failed step and the reason."
• "How busy was the CPU of web-01 over the last 24 hours, and how much bandwidth did it send out?"
• "What is my DigitalOcean balance this month, and how do the last three invoices compare?"
• "Point the A record of staging.example.com to 203.0.113.10. Show me the record now and the new value before you change it."

FAQ

Does Cursor support custom MCP servers on the free tier? Yes, MCP is available on Hobby, Pro and Business plans.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT