
How to add DigitalOcean MCP to Windsurf
DigitalOcean's App Platform MCP: deploy apps, tail logs, roll back. Archived — superseded by mcp-digitalocean. Paste the config into ~/.codeium/windsurf/mcp_config.json and restart Windsurf.
Last updated June 14, 2026 · 80★ · stdio · apikey · official
Windsurf config for DigitalOcean MCP
npx @digitalocean/mcp{
"mcpServers": {
"digitalocean-mcp": {
"command": "npx",
"args": [
"@digitalocean/mcp"
],
"env": {
"DIGITALOCEAN_API_TOKEN": "<your-do-token>"
}
}
}
}Setup steps
- 1Open Windsurf → Cascade → the hammer/MCP icon → Configure (or edit ~/.codeium/windsurf/mcp_config.json).
- 2Paste the DigitalOcean MCP config below.
- 3Fill in placeholder secrets, then save.
- 4Click Refresh in the MCP panel.
- 5DigitalOcean MCP's tools become available to Cascade.
Before you start
- Node.js 12+ with npm/npx
- DigitalOcean Personal Access Token with App Platform scopes (cloud.digitalocean.com/account/api/tokens)
- An MCP client: Claude Desktop v1.9+, Claude Code, Cursor or Windsurf
What DigitalOcean MCP can do in Windsurf
list_appsList all App Platform apps on the account.
create_appCreate a new app, e.g. from a GitHub repo.
get_appGet details of an app.
update_appUpdate an app's spec or settings.
delete_appDelete an app.
restart_appRestart an app or its components.
list_deploymentsList deployments for an app.
create_deploymentTrigger a new deployment.
Security
This repo is archived: it still runs via npx but receives no updates or security fixes — DigitalOcean's notice points to @digitalocean-labs/mcp-digitalocean as the successor. The DIGITALOCEAN_API_TOKEN you supply can create and delete real apps and deployments, so scope it to App Platform permissions only and rotate it regularly.
DigitalOcean MCP + Windsurf FAQ
Where is the Windsurf config file?
Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Paste the DigitalOcean MCP config there under the "mcpServers" key and restart the client.
Is DigitalOcean MCP safe to use with Windsurf?
This repo is archived: it still runs via npx but receives no updates or security fixes — DigitalOcean's notice points to @digitalocean-labs/mcp-digitalocean as the successor. The DIGITALOCEAN_API_TOKEN you supply can create and delete real apps and deployments, so scope it to App Platform permissions only and rotate it regularly.
Is the DigitalOcean MCP server still maintained?
No — the repository is archived. DigitalOcean's archive notice points to digitalocean-labs/mcp-digitalocean as the replacement. The @digitalocean/mcp npm package still runs, but it is frozen: no new features and no security fixes.
Can it manage Droplets or managed databases?
No. This server covers App Platform only: apps, deployments, logs, alerts, rollbacks and bandwidth metrics. For broader DigitalOcean coverage, use the successor project mcp-digitalocean.
Is it safe to keep using an archived server with my DO token?
It works, with a shrinking safety margin: the code runs locally via npx and talks only to DigitalOcean's API, but unpatched issues stay unpatched. Use a token scoped strictly to App Platform, rotate it regularly, and plan a migration to the successor.