DigitalOcean MCP server: scoped DigitalOcean access for every agent

Begin with account identity and a resource ID. A Droplet name can repeat across environments; the agent should show the selected account and Droplet before explaining a problem. Read the resource details and action history instead of inferring state from an old deployment note.

Documentation tools help match a symptom to the relevant service guidance. Ask for a linked page and the observed account state, then separate a proposed fix from any action. A finding such as “the backup policy is disabled” does not itself authorize changing infrastructure.

Billing context can be retrieved separately from resource administration. An analyst may need balance, invoices and billing history, while an infrastructure investigator needs Droplet details. Neither needs every service group enabled just because the provider offers it.

DigitalOcean MCP server: direct and gateway routes

The DigitalOcean MCP reference documents the family of remote servers and selections. The official repository is a related implementation route, not an independent competing cloud service.

Direct access is simpler when one client only needs DigitalOcean. AIPx is useful for joining cloud context with GitHub code, Sentry errors or Linear acceptance criteria. It does not replace the provider’s service configuration or API limits.

Connect DigitalOcean to Claude, Claude Code, Cursor or Codex

Complete DigitalOcean OAuth and choose the needed services and tool_groups. The connection uses the vendor’s read/write alias scopes; select the smallest useful surface.

1. Open the AIPx dashboard, choose DigitalOcean under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting DigitalOcean; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to DigitalOcean

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when DigitalOcean is the only service you need.

DigitalOcean MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Run /mcp and authorize, then inspect account information and one Droplet by ID. Keep resource mutations hidden while diagnosing. Claude Code MCP setup explains registration scope and OAuth.

DigitalOcean MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

After Cursor login, check the selected DigitalOcean services and tool groups. Read resource and action details before proposing infrastructure changes. See Cursor MCP configuration for discovery troubleshooting.

DigitalOcean MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the DigitalOcean credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

A supported ChatGPT custom MCP account can inspect the selected DigitalOcean tools through this endpoint. Cloud access and service selection remain separate constraints. ChatGPT MCP setup describes current plan and administration requirements.

Scope DigitalOcean per agent

For billing analysis, allow invoice, balance and billing-history reads and hide resource mutation tools. For a Droplet investigator, enable details, action reads, backup-policy reads and relevant documentation. Keep unused service groups out of the connection where possible, then use Hide for irrelevant discovered tools.

The general defaults are Allow for reads and Confirm for writes. Confirm depends on the client honoring the approval hint; Hide is the restriction when an operation must be unavailable. See MCP access control for the tool boundary.

Cloudflare and Supabase can supply context from other infrastructure providers. PostHog can help distinguish a deployment symptom from a product behavior change. Keep provider accounts and environments explicit throughout the diagnosis.

Service selection and cloud-operation limits

The default selection is not the whole DigitalOcean catalog. If a Kubernetes or other service tool is missing, inspect the configured services and groups before assuming it is included. OAuth read/write permissions and the user’s cloud access remain upstream constraints.

Resource changes can incur cost or interrupt a service. A proposed action should include the resource ID, environment and expected effect. Infrastructure configuration in version control can be a better output for repeatable changes than an interactive operation with no repository diff.

Browse all MCP integrations to choose another connection for this agent.

The DigitalOcean connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.