Bring Cloud Computing
to VS Code Copilot
Learn how to connect DigitalOcean to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings DigitalOcean data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
DigitalOcean in VS Code Copilot
DigitalOcean and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect DigitalOcean to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.