DigitalOcean MCP Server

DigitalOcean's MCP server equips AI agents to manage Droplets, Kubernetes clusters, managed databases, load balancers, and cloud firewall rules on DigitalOcean. It empowers agents to provision virtual compute resources, monitor infrastructure metrics, and streamline cloud hosting for developer teams.

Start for free

Benefits with Ory + DigitalOcean MCP Server

DigitalOcean's MCP server lets your agents manage Droplets, Kubernetes clusters, managed databases, App Platform apps, and networking in your DigitalOcean account. Creating or deleting resources affects both uptime and your bill. Ory Agent Security lets monitoring agents read resource state while provisioning stays with the agents you approve, and every tool call is tied to the user behind it.

View on GitHub

Use Cases

— 01 use case

Agent IAM

Monitoring agents at Read, operations agents resizing Droplets at Write, server creation plus firewall and DNS changes at Admin, and Block set on every other agent.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the DigitalOcean MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for monitoring agents, write for operations agents that manage existing resources, admin for provisioning agents, and no access for agents with no infrastructure role.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied Droplet deletion stops before it reaches DigitalOcean, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents change resources and for whom without blocking anything, so you can apply Ory's pre-built policy for the DigitalOcean MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the DigitalOcean MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent created, resized, or removed a resource, and on whose behalf.