Name: DigitalOcean Per-Service Endpoints
Author: DigitalOcean

LABSCO SUMMARY

Per-service endpoints are how you give an agent droplets without also giving it your databases.

One endpoint for a whole cloud account is a large grant. Splitting by service means the decision is made in the client config, visibly, one line per service — and a client that was never given the databases endpoint cannot reach databases whatever it is asked to do.

What it is

DigitalOcean publishes an endpoint per service rather than one for everything: the host contains the service name. You add only the ones you want a client to reach.

What you get

App Platform, Kubernetes (DOKS), Droplets, managed databases, Spaces object storage
Networking, AI inference and the other services in their reference
A Documentation endpoint for searching DigitalOcean's docs, quickstarts and troubleshooting pages

Requirements

A DigitalOcean account.
DigitalOcean recommends OAuth: add an endpoint without an Authorization header and your client opens a browser sign-in, so no long-lived token sits in your config.
A DigitalOcean API token sent as a Bearer header works too.
The Documentation endpoint needs no API token, but still asks you to sign in.

Setup effort

Paste a URL, then authorize — add the servers you want to your client, then approve the OAuth consent screen

See installation options

USE CASES

Shipping an app to App Platform

With only the App Platform endpoint connected, point it at a GitHub, GitLab or Bitbucket repo and branch, create the app from a spec, then check how the deployment went.

apps-create-app-from-specapps-get-deployment-statusapps-list

Changing a running app's configuration

Read the app's current spec, change what needs changing, such as environment variables or scaling, and send it back as an update that redeploys the app.

apps-get-infoapps-updateapps-get-deployment-status

Answering a DigitalOcean question from its docs

Search DigitalOcean's documentation, pull the quickstart for a service, or paste an error message and get the matching troubleshooting page back.

docs-searchdocs-get-quickstartdocs-troubleshoot

Routine droplet upkeep

Check which sizes are available, resize a droplet that has run out of headroom, and turn on backups for one that never had them, all through the Droplets endpoint.

size-listresize-dropletenable-backups-droplet

Putting a new service on a domain

Create the domain and its DNS records through the Networking endpoint instead of the control panel.

domain-createdomain-record-create

Picking a model to serve

Search the inference model catalog by name and open the full card for the likely candidates before you set up a dedicated inference instance.

inference-model-catalog-searchinference-model-catalog-get-card

336 tools

Listed in project docs. Your client may show a different list.

action-get

action-list

balance-get

billing-history-list

invoice-list

key-create

key-delete

key-get

key-list

account-get-information

apps-create-app-from-spec

apps-update

apps-delete

apps-get-info

apps-get-deployment-status

INSTALLATION

Connect your client

DigitalOcean hosts 22 servers, each with its own URL.

Server setup

ENDPOINT URLS

https://apps.mcp.digitalocean.com/mcp
https://databases.mcp.digitalocean.com/mcp
https://doks.mcp.digitalocean.com/mcp
https://droplets.mcp.digitalocean.com/mcp
https://functions.mcp.digitalocean.com/mcp
https://dedicated-inference.mcp.digitalocean.com/mcp
https://inference-modelcatalog.mcp.digitalocean.com/mcp
https://kbaas.do-ai.run/v1/mcp
https://spaces.mcp.digitalocean.com/mcp
https://networking.mcp.digitalocean.com/mcp
https://nfs.mcp.digitalocean.com/mcp
https://accounts.mcp.digitalocean.com/mcp
https://insights.mcp.digitalocean.com/mcp
https://genai-evaluation.mcp.digitalocean.com/mcp
https://genai-batchinference.mcp.digitalocean.com/mcp
https://genai-custom-models.mcp.digitalocean.com/mcp
https://genai-inferencerouter.mcp.digitalocean.com/mcp
https://vector-databases.mcp.digitalocean.com/mcp
https://docr.mcp.digitalocean.com/mcp
https://docs.mcp.digitalocean.com/mcp
https://marketplace.mcp.digitalocean.com/mcp
https://volumes.mcp.digitalocean.com/mcp

Requirements

OAuth sign-in to DigitalOcean in clients that support it (recommended by DigitalOcean), or a DigitalOcean API token as a bearer header; the documentation endpoint needs no API token (leave out the Authorization header), and your client will ask you to sign in to DigitalOcean

MCP Clients

Any MCP client

ANY MCP CLIENT · JSON

{
  "mcpServers": {
    "apps": {
      "url": "https://apps.mcp.digitalocean.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_DIGITALOCEAN_API_TOKEN>"
      }
    },
    "databases": {
      "url": "https://databases.mcp.digitalocean.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_DIGITALOCEAN_API_TOKEN>"
      }
    }
  }
}

This example connects App Platform and Databases. <YOUR_DIGITALOCEAN_API_TOKEN> is your DigitalOcean API token. Add one entry per service you want the client to reach, each with the same Authorization header:

App Platform — https://apps.mcp.digitalocean.com/mcp

Kubernetes — https://doks.mcp.digitalocean.com/mcp

Droplets — https://droplets.mcp.digitalocean.com/mcp

Functions — https://functions.mcp.digitalocean.com/mcp

Databases — https://databases.mcp.digitalocean.com/mcp

Dedicated Inference — https://dedicated-inference.mcp.digitalocean.com/mcp

Model Catalog — https://inference-modelcatalog.mcp.digitalocean.com/mcp

Knowledge Bases — https://kbaas.do-ai.run/v1/mcp

Spaces — https://spaces.mcp.digitalocean.com/mcp

Networking — https://networking.mcp.digitalocean.com/mcp

Network File Storage — https://nfs.mcp.digitalocean.com/mcp

Accounts — https://accounts.mcp.digitalocean.com/mcp

Insights — https://insights.mcp.digitalocean.com/mcp

Evaluations — https://genai-evaluation.mcp.digitalocean.com/mcp

Batch Inference — https://genai-batchinference.mcp.digitalocean.com/mcp

Custom Models — https://genai-custom-models.mcp.digitalocean.com/mcp

Inference Router — https://genai-inferencerouter.mcp.digitalocean.com/mcp

Vector Database — https://vector-databases.mcp.digitalocean.com/mcp

Container Registry — https://docr.mcp.digitalocean.com/mcp

Documentation — https://docs.mcp.digitalocean.com/mcp

Marketplace — https://marketplace.mcp.digitalocean.com/mcp

Volumes Block Storage — https://volumes.mcp.digitalocean.com/mcp

The Documentation endpoint needs no API token, so leave its headers out; your client asks you to sign in to DigitalOcean instead.

Any MCP client — OAuth

To use OAuth, add the server’s URL to your client’s configuration without an Authorization header:

ANY MCP CLIENT — OAUTH · JSON

{
  "mcpServers": {
    "apps": {
      "url": "https://apps.mcp.digitalocean.com/mcp"
    }
  }
}

Your client obtains a short-lived access token through a browser-based sign-in, so you don’t store a long-lived token in your configuration. All remote MCP servers that require authentication support OAuth.

VS Code — Remote

The VS Code MCP config file is located at .vscode/mcp.json in your workspace root.

VS CODE — REMOTE · JSON

{
  "inputs": [
    {
      "id": "digitalocean-token",
      "type": "promptString",
      "description": "DigitalOcean API Token",
      "password": true
    }
  ],
  "servers": {
    "digitalocean-apps": {
      "url": "https://apps.mcp.digitalocean.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:digitalocean-token}"
      }
    },
    "digitalocean-databases": {
      "url": "https://databases.mcp.digitalocean.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:digitalocean-token}"
      }
    }
  }
}

The inputs block defines a named input (digitalocean-token) that VS Code will prompt you to enter securely the first time you use the server.

Any MCP client — Local

To use the local MCP server, you need Node.js v18 or later and npm v8 or later. The following example configures the DigitalOcean MCP server with <YOUR_DIGITALOCEAN_API_TOKEN> and enables access to only the App Platform (apps) service.

ANY MCP CLIENT — LOCAL · JSON

{
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "-y",
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "<YOUR_DIGITALOCEAN_API_TOKEN>"
      }
    }
  }
}

<YOUR_DIGITALOCEAN_API_TOKEN> is your DigitalOcean API token, or use the client-specific method of variable substitution (if available) to keep your token out of the configuration file.

Claude Code — Local

CLAUDE CODE — LOCAL · TERMINAL

claude mcp add digitalocean \
  --env DIGITALOCEAN_API_TOKEN=${DIGITALOCEAN_API_TOKEN} \
  -- npx -y "@digitalocean/mcp"

Set the DIGITALOCEAN_API_TOKEN environment variable to your DigitalOcean API token before running this command. As written it loads every service; to limit it, add --services with a comma-separated list after "@digitalocean/mcp".

Claude Desktop — Local

CLAUDE DESKTOP — LOCAL · JSON

{
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "<YOUR_DIGITALOCEAN_API_TOKEN>"
      }
    }
  }
}

Add services to --services as a comma-separated list, then restart Claude Desktop.

Cursor — Local

CURSOR — LOCAL · JSON

{
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${DIGITALOCEAN_API_TOKEN}"
      }
    }
  }
}

Set DIGITALOCEAN_API_TOKEN in your shell profile before starting Cursor; the block reads it from there. Add services to --services as a comma-separated list.

VS Code — Local

VS CODE — LOCAL · JSON

{
  "inputs": [
    {
      "id": "digitalocean-token",
      "type": "promptString",
      "description": "DigitalOcean API Token",
      "password": true
    }
  ],
  "servers": {
    "mcpDigitalOcean": {
      "command": "npx",
      "args": [
        "@digitalocean/mcp",
        "--services",
        "apps"
      ],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "${input:digitalocean-token}"
      }
    }
  }
}

Goes in .vscode/mcp.json; VS Code asks for the token the first time the server starts.

DigitalOcean Per-Service Endpoints

Per-service endpoints are how you give an agent droplets without also giving it your databases.

What it is

What you get

Requirements

Setup effort

Shipping an app to App Platform

Changing a running app's configuration

Answering a DigitalOcean question from its docs

Routine droplet upkeep

Putting a new service on a domain

Picking a model to serve

336 tools

What to know first

Tools you get

Requires

Connect your client

Server setup

Requirements

MCP Clients

Any MCP client

Any MCP client — OAuth

VS Code — Remote

Any MCP client — Local

Claude Code — Local

Claude Desktop — Local

Cursor — Local

VS Code — Local

DigitalOcean Per-Service Endpoints

Per-service endpoints are how you give an agent droplets without also giving it your databases.

What it is

What you get

Requirements

Setup effort

Shipping an app to App Platform

Changing a running app's configuration

Answering a DigitalOcean question from its docs

Routine droplet upkeep

Putting a new service on a domain

Picking a model to serve

336 tools

What to know first

Tools you get

Requires

Connect your client

Server setup

Requirements

MCP Clients

Any MCP client

Any MCP client — OAuth

VS Code — Remote

Any MCP client — Local

Claude Code — Local

Claude Desktop — Local

Cursor — Local

VS Code — Local

Same category

Azure MCP Server

Redis Cloud

Cloudability API

Hetzner Cloud MCP Server