Skip to main content
Glama
DigitalOcean MCP Server

DigitalOcean MCP Server

by amranu

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_TOKEN environment variable

Related MCP server: Semantic API

Quick Start

Installation

npm install
npm run build

Environment Setup

Create a .env file or set the environment variable:

export DIGITALOCEAN_API_TOKEN="your-digitalocean-api-token"

Running the Server

npm start

Or for development with auto-reload:

npm run dev

MCP 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"
    }
  }
}
// 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.py

To rebuild the server:

npm run build

Claude 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"
claude

Real-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

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests if applicable

  5. Submit a pull request

License

MIT License - see LICENSE file for details

Support

Available Tools

6 tools
call_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: limit, tag.

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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation3/5

    The tools have some clear distinctions, such as list_endpoints vs. search_endpoints, but there is significant overlap and ambiguity. For example, call_digitalocean_api and get_endpoint_details both relate to endpoint interactions, and configure_digitalocean_api is a setup tool that might be confused with the others in practice. The descriptions help clarify, but the boundaries between endpoint-related tools are not sharply defined.

    Naming Consistency4/5

    The tool names follow a mostly consistent verb_noun pattern, such as list_endpoints, get_endpoint_details, and search_endpoints. However, there are minor deviations like call_digitalocean_api (which uses 'call' instead of a more specific verb) and configure_digitalocean_api (which is more of a setup action). Overall, the naming is readable and predictable with only slight inconsistencies.

    Tool Count4/5

    With 6 tools, the count is reasonable for a server focused on DigitalOcean API interactions. It covers configuration, listing, searching, and calling endpoints, which aligns well with the apparent scope. However, it might be slightly thin if more granular operations (e.g., specific resource management) are expected, but it's well-scoped for its purpose.

    Completeness3/5

    The tool set provides basic coverage for exploring and using DigitalOcean APIs, including configuration, listing, searching, and calling endpoints. However, there are notable gaps: it lacks direct CRUD operations for DigitalOcean resources (e.g., droplets, volumes, databases), which are core to the domain. This makes the surface incomplete for full agent workflows, as users might need to rely heavily on generic API calls instead of dedicated tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides programmatic access to DigitalOcean's API. This server exposes tools for managing droplets, Kubernetes clusters, and container registries through the MCP interface.
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Natural language API discovery MCP server. Search 700+ API capabilities across 163 current providers, get, exact endpoints, auth setup, and code snippets. Supports auto-discovery of new APIs.
      3
      24 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Transforms OpenAPI specs into an MCP server, enabling dynamic API interaction through natural language with automatic authentication and endpoint discovery.
      131 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server that enables AI assistants to explore and generate code for type-safe OpenAPI clients from various cloud APIs like DigitalOcean, Hetzner Cloud, and Ory.
      7
      7 npm
      19
      MIT