Bring Cloud Computing
to Cursor
Learn how to connect DigitalOcean to Cursor and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the DigitalOcean MCP Server?
Connect your DigitalOcean cloud account to any AI agent and take full control of your infrastructure management and monitoring workflows through natural conversation.
What you can do
- Droplet Management — List all virtual machines (Droplets) and retrieve detailed metadata including status, IP addresses, and hardware specs programmatically
- Domain & DNS Control — Query and manage your domain names and DNS configurations to ensure service availability and correct routing in real-time
- Database Monitoring — Track the status and connection endpoints of your managed PostgreSQL, MySQL, and Redis clusters directly through your agent
- Kubernetes Insights — List all DOKS (DigitalOcean Kubernetes Service) clusters and retrieve health metadata to oversee your containerized deployments
- Resource Inventory — Access account-wide actions, disk images, snapshots, and block storage volumes for a comprehensive high-fidelity overview
How it works
1. Subscribe to this server
2. Retrieve your Personal Access Token from the DigitalOcean dashboard (API > Tokens)
3. Start managing your cloud resources from Claude, Cursor, or any MCP client
No more manual dashboard navigation or searching for IP addresses. Your AI acts as your dedicated cloud architect and SRE coordinator.
Who is this for?
- DevOps Engineers — instantly retrieve droplet specs and check database health using natural language commands
- System Administrators — monitor account actions and manage DNS records without leaving your communication tools
- Technical Founders — orchestrate your startup's cloud infrastructure and monitor snapshots through simple AI queries
Built-in capabilities (9)
Useful for verifying resource availability. Get DigitalOcean account details
Get details for a specific Droplet
Useful for auditing and monitoring changes. List historical account actions
Includes cluster status, engine versions, and endpoints. List managed database clusters
Essential for reviewing web configurations. List all managed DNS domains
Includes metadata such as status, IP addresses, and specs. List all active Droplets
Useful for resource recovery and deployment. List snapshots and disk images
Includes information about cluster health, versions, and nodes. List all Kubernetes clusters
Includes size, region, and current attachment status. List block storage volumes
Why Cursor?
Cursor's Agent mode turns DigitalOcean into an in-editor superpower. Ask Cursor to generate code using live data from DigitalOcean and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
DigitalOcean in Cursor
DigitalOcean and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect DigitalOcean to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for DigitalOcean in Cursor
The DigitalOcean MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
DigitalOcean for Cursor
Every tool call from Cursor to the DigitalOcean MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my DigitalOcean Access Token?
Log in to the Cloud Control Panel, navigate to API in the sidebar, and click Generate New Token under Personal Access Tokens.
Can I perform destructive actions like deleting droplets?
No. The current toolset is focused on querying and monitoring resources. Destructive or state-altering commands are not exposed via the agent.
How do I get technical details for a specific Droplet?
Use the get_droplet_details tool with the Droplet's numeric ID to retrieve full networking and configuration metadata.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.