by digitalocean
Easily manage, deploy, and monitor cloud resources on DigitalOcean using natural language commands for streamlined cloud
Connects AI assistants to DigitalOcean's cloud platform API for managing apps, droplets, and infrastructure through natural language commands.
DigitalOcean is an official MCP server published by digitalocean that provides AI assistants with tools and capabilities via the Model Context Protocol. Easily manage, deploy, and monitor cloud resources on DigitalOcean using natural language commands for streamlined cloud It is categorized under cloud infrastructure.
You can install DigitalOcean in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
DigitalOcean is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: DigitalOcean is the kind of server we cite when onboarding engineers to host + tool permissions.
I recommend DigitalOcean for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
DigitalOcean reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated DigitalOcean against two servers with overlapping tools; this profile had the clearer scope statement.
DigitalOcean is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Useful MCP listing: DigitalOcean is the kind of server we cite when onboarding engineers to host + tool permissions.
DigitalOcean is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated DigitalOcean against two servers with overlapping tools; this profile had the clearer scope statement.
DigitalOcean reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
DigitalOcean is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 67
⚠️ ARCHIVE NOTICE
This repository has been archived. Please use @digitalocean-labs/mcp-digitalocean
This MCP server exposes DigitalOcean App Platform functionality through standardized tools that can be used by any MCP client, including Claude Desktop and Cursor. It enables AI assistants to directly manage your DigitalOcean apps without writing code or memorizing API endpoints.
You can now do things like:
...and more!
To use the DigitalOcean MCP Server, you’ll need:
💡 You do not need to install anything—this server runs via npx, with just a one-line config added to your MCP client.
Head to DigitalOcean’s API settings and create a new Personal Access Token with App Platform permissions.
Add this JSON snippet to your client’s MCP config file:
{
"mcpServers": {
"digitalocean": {
"command": "npx",
"args": ["@digitalocean/mcp"],
"env": {
"DIGITALOCEAN_API_TOKEN": "YOUR_DO_TOKEN"
}
}
}
}
Here’s what each part of the snippet does:
npx or full path)Then follow the instructions for your specific tool:
claude_desktop_config.jsonYOUR_DO_TOKEN with your token
Setting up DigitalOcean MCP Server in Claude Desktop
~/.cursor/mcp.jsonYOUR_DO_TOKEN with your token
Setting up DigitalOcean MCP Server in Cursor
~/.codeium/windsurf/mcp_config.jsonYOUR_DO_TOKEN with your tokenSetting up DigitalOcean MCP Server in Windsurf
Once it’s configured, try asking your assistant:
“List all active apps on my account”
“Create a new app from https://github.com/do-community/do-one-click-deploy-flask with 1GB RAM in NYC3”
“Show logs for checkout-service”
“Cancel the current deployment for marketing-site”
“Delete the old `staging-env` app”
The assistant will send the request → the MCP server talks to DigitalOcean → you get structured results, ready to act on.
| Category | Commands |
|---|---|
| Apps | list_apps, create_app, get_app, update_app, delete_app, restart_app |
| Deployments | list_deployments, create_deployment, get_deployment, cancel_deployment |
| Logs | retrieve_active_deployment_logs, download_logs |
| Infra | list_app_regions, list_instance_sizes |
| Alerts | list_app_alerts, update_app_alert_destinations |
| Rollbacks | validate_app_rollback, rollback_app, commit_app_rollback, revert_app_rollback |
| Metrics | get_app_bandwidth_daily_metrics, get_all_app_bandwidth_daily_metrics |
| Validation | validate_app_spec |
You can also test the server directly by running:
npx @digitalocean/mcp
We’d love your help improving this! Bug reports, new features, and docs improvements are all welcome.
git checkout -b feature/awesome-tool)This project is licensed under the MIT License.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.