pulsemcp verified Safe content atomic mcp-remote

DigitalOcean

This MCP server provides AI assistants with complete DigitalOcean cloud infrastructure management through 37 specialized tools across 6 service categories, built using Go with the official DigitalOcean godo SDK and OAuth2 authentication. The implementation offers full CRUD operations for droplets, volumes, snapshots, images, floating IPs, and load balancers, plus Kubernetes cluster management and container registry access, all organized into modular handlers with structured argument validation and comprehensive error handling. Built with stdio transport protocol integration and JSON schema validation for all tool parameters, it serves DevOps teams needing conversational cloud infrastructure management, developers wanting to automate DigitalOcean operations through AI assistants, and system administrators requiring programmatic access to the full spectrum of DigitalOcean services without direct API interaction.

Cognium trust score

97%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/rohit-kaundal/digitalocean-mcp-server
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve DigitalOcean from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"