How to Use the DigitalOcean MCP in Cursor

Q: How do I add the DigitalOcean MCP Server to my Cursor editor?

Add the DigitalOcean server to your project-level .cursor/mcp.json file under the mcpServers key. Once saved, Cursor's chat and Agent modes will immediately recognize the new DigitalOcean capabilities.

Q: Can Cursor automatically configure my DigitalOcean Kubernetes clusters?

No, Cursor can only read cluster state using listkubernetesclusters. It cannot change DigitalOcean cluster configurations, deploy pods, or modify node pools.

Build and debug your DigitalOcean setup while writing code inside Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect DigitalOcean MCP to Cursor

Create your Vinkius account to connect DigitalOcean to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup DigitalOcean with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Pull live droplet specs into Cursor

Pull live server specs into your editor using `get_droplet_details` to write code against actual DigitalOcean hardware configurations. Cursor's Agent mode uses this MCP connection to inject real DigitalOcean IP addresses and status metadata directly into your active workspace. You don't have to write code using mock objects or outdated stubs in Cursor. Cursor writes deployment scripts and configuration files using the exact specs of your live DigitalOcean droplets.

Audit live DNS records from Cursor

Audit your DNS configurations inside Cursor by calling `list_domains` to match your code with live routing. The Cursor editor uses this tool to check which domains are pointed at your DigitalOcean nameservers. When writing domain validation logic or setting up SSL certificates in Cursor, the editor cross-references your code against the live DigitalOcean DNS records.

Track actions with the DigitalOcean MCP Server

Monitor active deployments using this MCP Server by running `list_actions` to track recent infrastructure changes. Cursor reads the execution history to verify if a DigitalOcean droplet resize or volume attachment completed successfully. This workflow lets you debug DigitalOcean deployment failures without leaving your Cursor code editor. You see the exact status of your background DigitalOcean API actions right next to your Cursor terminal output.

Setup guide

Set up DigitalOcean MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the DigitalOcean MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent DigitalOcean transactions." If the MCP tools are loaded correctly, Cursor will call the DigitalOcean tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "digitalocean-alternative-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DigitalOcean. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect DigitalOcean now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about DigitalOcean MCP in Cursor

Add the DigitalOcean server to your project-level `.cursor/mcp.json` file under the `mcpServers` key. Once saved, Cursor's chat and Agent modes will immediately recognize the new DigitalOcean capabilities.

No, Cursor can only read cluster state using `list_kubernetes_clusters`. It cannot change DigitalOcean cluster configurations, deploy pods, or modify node pools.

No, your DigitalOcean API keys remain local to your machine. Cursor communicates with the server locally, ensuring your DigitalOcean cloud credentials never leave your workspace.

Ask the Cursor Composer or Agent to list your storage. It will invoke `list_volumes` and display the size and attachment status of your DigitalOcean block storage.

The server only retrieves read-only DigitalOcean metadata like droplet specs, database endpoints, and DNS records. This operational DigitalOcean data is processed locally inside Cursor's sandbox before being used to generate code.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript