DigitalOcean MCP Server
Provides comprehensive access to 471+ DigitalOcean API endpoints for managing infrastructure including Droplets, databases, load balancers, Kubernetes clusters, block storage, CDN, DNS, firewalls, and more across all DigitalOcean services.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DigitalOcean MCP Server list my droplets and show their status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DigitalOcean MCP Server
A Model Context Protocol (MCP) server that provides comprehensive access to all DigitalOcean API endpoints, dynamically extracted from their OpenAPI specification. This server enables AI assistants to interact with your DigitalOcean resources programmatically.
Features
Complete API Coverage: Access to 471+ DigitalOcean API endpoints across all services
Dynamic Endpoint Discovery: Automatically extracts and indexes endpoints from DigitalOcean's OpenAPI spec
Intelligent Search: Find endpoints by operation ID, summary, description, or tags
Detailed Documentation: Get parameter details, descriptions, and requirements for each endpoint
Authenticated API Calls: Execute API calls through the MCP server with proper authentication
Tag-based Organization: Browse endpoints by category (Droplets, Load Balancers, Databases, etc.)
Auto-configuration: Automatically configures from
DIGITALOCEAN_API_TOKENenvironment variable
Quick Start
Installation
npm install
npm run buildEnvironment Setup
Create a .env file or set the environment variable:
export DIGITALOCEAN_API_TOKEN="your-digitalocean-api-token"Running the Server
npm startOr for development with auto-reload:
npm run devMCP Tools
The server provides these MCP tools for AI assistants:
1. configure_digitalocean_api
Set up API credentials (optional if using environment variable)
2. list_endpoints
List all available endpoints with optional filtering by tag
3. search_endpoints
Search endpoints by query string
4. get_endpoint_details
Get detailed information about a specific endpoint
5. call_digitalocean_api
Execute API calls with authentication
6. list_tags
Show all available endpoint categories
Usage Examples
Basic Droplet Management
// List all droplets
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "droplets_list"
}
}
// Create a new droplet
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "droplets_create",
"parameters": {
"name": "example-droplet",
"region": "nyc3",
"size": "s-1vcpu-1gb",
"image": "ubuntu-20-04-x64"
}
}
}Discovery and Search
// Find all droplet-related endpoints
{
"tool": "search_endpoints",
"arguments": {
"query": "droplet",
"limit": 10
}
}
// List endpoints by category
{
"tool": "list_endpoints",
"arguments": {
"tag": "Load Balancers",
"limit": 5
}
}
// Get detailed endpoint information
{
"tool": "get_endpoint_details",
"arguments": {
"operationId": "droplets_list"
}
}Architecture
extract_endpoints.py: Python script that parses the OpenAPI spec and extracts endpoint definitions
src/endpoints.ts: TypeScript module for loading and searching endpoint data
src/api-client.ts: HTTP client for making authenticated API calls
src/index.ts: Main MCP server implementation
API Coverage
The server provides access to all DigitalOcean API endpoints across categories including:
1-Click Applications
Account Management
Billing
Block Storage Volumes
CDN Endpoints
Certificates
Container Registry
Databases
Domains and DNS
Droplets
Firewalls
Floating IPs
Images
Kubernetes
Load Balancers
Monitoring
Projects
Reserved IPs
Snapshots
SSH Keys
Tags
VPCs
And more...
Development
To regenerate the endpoint data:
python extract_endpoints.pyTo rebuild the server:
npm run buildClaude Configuration
Claude Desktop
Add to your Claude Desktop MCP configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"digitalocean": {
"command": "node",
"args": ["/path/to/digitalocean-mcp/dist/index.js"],
"env": {
"DIGITALOCEAN_API_TOKEN": "your-digitalocean-api-token"
}
}
}
}Claude Code (CLI)
For Claude Code users, the server auto-configures from environment variables:
export DIGITALOCEAN_API_TOKEN="your-digitalocean-api-token"
claudeReal-World Examples
Infrastructure Management
// Check droplet status across your infrastructure
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "droplets_list"
}
}
// Scale a droplet
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "dropletActions_post",
"parameters": {
"droplet_id": "123456789",
"type": "resize",
"size": "s-2vcpu-4gb"
}
}
}Database Operations
// List database clusters
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "databases_list_clusters"
}
}
// Create database backup
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "databases_add_backup",
"parameters": {
"database_cluster_uuid": "your-cluster-uuid"
}
}
}Load Balancer Management
// List load balancers
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "load_balancers_list"
}
}
// Update load balancer configuration
{
"tool": "call_digitalocean_api",
"arguments": {
"operationId": "load_balancers_update",
"parameters": {
"lb_id": "your-lb-id",
"name": "updated-lb-name",
"algorithm": "round_robin"
}
}
}Security
API tokens are handled securely and never logged
All requests use HTTPS
Rate limiting is handled automatically
Environment variables are preferred for token storage
Contributing
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
License
MIT License - see LICENSE file for details
Support
GitHub Issues: Report bugs or request features
Documentation: See the examples above and endpoint details via the
get_endpoint_detailstoolDigitalOcean API Docs: Official API Documentation
Available Tools
6 toolscall_digitalocean_apiC
Call a DigitalOcean API endpoint
Inputs: operationId (required), parameters.
configure_digitalocean_apiB
Configure DigitalOcean API credentials. Can be auto-configured from DIGITALOCEAN_API_TOKEN environment variable.
Inputs: token (required), baseUrl.
get_endpoint_detailsC
Get detailed information about a specific endpoint
Inputs: operationId (required).
list_endpointsC
List all available DigitalOcean API endpoints
Inputs: tag, limit.
list_tagsB
List all available endpoint tags
Inputs: no named parameters.
search_endpointsC
Search for DigitalOcean API endpoints
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools have distinct purposes: call_digitalocean_api for API calls, configure_digitalocean_api for setup, and list_endpoints/search_endpoints for discovery. However, get_endpoint_details and list_endpoints could be slightly confusing as both relate to endpoint information, though descriptions clarify one is for details and the other for listing.
All tools follow a consistent verb_noun pattern with snake_case (e.g., call_digitalocean_api, list_endpoints, search_endpoints). The naming is predictable and uniform across the set, making it easy to understand each tool's function at a glance.
With 6 tools, the count is reasonable for a server focused on DigitalOcean API interaction. It covers configuration, discovery, and execution, though it might feel slightly thin if more advanced operations are expected, but it's well-scoped for its apparent purpose.
The tool set covers configuration, endpoint discovery, and API calls, but there are notable gaps. For a DigitalOcean server, it lacks direct tools for common resources like droplets, databases, or volumes, relying instead on generic API calls, which could lead to agent inefficiencies or errors in handling specific workflows.
Related MCP Connectors
Build, deploy, manage, and troubleshoot applications and infrastructure on DigitalOcean.
29 DNS, SEO, SSL, security, WHOIS & mail tools for AI agents. Pay per call (x402) or card API key.
Manage American Cloud VMs, Kubernetes, databases, storage, networks and DNS from your AI assistant.
Manage Vozora VPS servers, SSH keys, firewalls, DNS and usage from an AI agent.