zed-mcp-server-digitalocean
A Zed extension that exposes DigitalOcean's MCP server inside Zed's Agent panel by downloading the @digitalocean/mcp Node package and launching it via Node. It forwards a required DigitalOcean API token and optional configuration (enabled services, API endpoint override) so Zed can use MCP tools for DigitalOcean resources.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses a DigitalOcean personal access token for authentication. The README does not document token scope/least-privilege, secure storage/redaction behavior, or whether the extension logs requests/responses. It downloads and launches a Node package (@digitalocean/mcp), so supply-chain and dependency integrity practices are not described in the provided content.
⚡ Reliability
Best When
You want to use DigitalOcean MCP capabilities from within Zed and can securely provide a DigitalOcean personal access token to the extension.
Avoid When
You cannot accept token-based access risk or you need strong, documented guarantees about error handling, rate limits, and operational reliability of the wrapper/launcher.
Use Cases
- • Letting a Zed agent browse/manage DigitalOcean resources (e.g., apps, databases, droplets) through MCP tools
- • Centralizing DigitalOcean MCP tool access inside the Zed Agent panel for interactive workflows
- • Using a local MCP proxy/launcher approach rather than manually configuring remote MCP endpoints
Not For
- • Environments where third-party code execution (Node package download/launch) is not allowed
- • Teams that require documented MCP tool schemas, strict rate-limit handling, or robust operational guarantees from the extension itself
- • Production setups needing clear SLA/SLO and detailed incident/error-recovery behavior from the MCP server wrapper
Interface
Authentication
The extension requires a DigitalOcean personal access token in settings. The README does not describe token scopes, least-privilege recommendations, or how tokens are stored/redacted.
Pricing
No pricing information provided for the extension itself; any costs would come from DigitalOcean API usage.
Agent Metadata
Known Gotchas
- ⚠ Requires a valid DigitalOcean API token; failures may occur if the token is missing/expired
- ⚠ The extension launches a Node-based MCP server; network/API errors will propagate from DigitalOcean and may need agent-side retry logic
- ⚠ Services selection is controlled by a comma-separated string; incorrect values may disable expected tools
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zed-mcp-server-digitalocean.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.