DigitalOcean

Provides comprehensive access to DigitalOcean API endpoints via MCP with dynamic discovery and authenticated calls.
  • typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You run a Model Context Protocol (MCP) server that gives you programmatic access to DigitalOcean resources. It dynamically discovers all DigitalOcean API endpoints, organizes them by category, and lets you perform authenticated calls through a simple MCP client workflow.

How to use

Connect with an MCP client to explore endpoints, search by keywords or tags, and execute authenticated API calls against DigitalOcean resources. You can list endpoints by category, inspect endpoint details, and run operations such as listing droplets, creating resources, or retrieving cluster information. All activity uses secure HTTPS and relies on your configured credentials.

How to install

npm install
npm run build

Additional setup and usage notes

Prerequisites: you need Node.js and npm installed on your machine.

Environment variable for authentication is DIGITALOCEAN_API_TOKEN. You can set it in your shell session or in a .env file before starting the MCP server.

Start options include a production start or development with auto-reload. Use the appropriate script to run the server.

Configuration and usage examples

Configure the MCP server in your environment and via the provided tooling to enable authenticated requests against DigitalOcean endpoints.

// Claude Desktop example configuration (mcpServers entry)
{
  "mcpServers": {
    "digitalocean": {
      "command": "node",
      "args": ["/path/to/digitalocean-mcp/dist/index.js"],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "your-digitalocean-api-token"
      }
    }
  }
}

Security and expectations

API tokens are handled securely and never logged. All requests use HTTPS. Token storage is best done via environment variables.

Troubleshooting tips

If you cannot connect, verify that DIGITALOCEAN_API_TOKEN is set correctly and that the MCP server has started without errors. Check that the server can reach DigitalOcean's API endpoints and that you are using the correct operation IDs when calling endpoints.

Notes

The MCP server exposes endpoints across multiple DigitalOcean services, including Droplets, Load Balancers, Databases, and more, with dynamic endpoint discovery and tag-based browsing.

Available tools

configure_digitalocean_api

Set up API credentials and environment integration if you are using environment-variable based setup.

list_endpoints

List all available endpoints with optional filtering by tag to help you discover relevant API operations.

search_endpoints

Search endpoints by a text query to quickly find operations by name, description, or tags.

get_endpoint_details

Retrieve detailed information about a specific endpoint, including parameters and requirements.

call_digitalocean_api

Execute an authenticated API call against a selected endpoint using its operationId and provided parameters.

list_tags

Show all available endpoint categories for easy navigation.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational