Skip to content

enhance: add official DigitalOcean remote - #1392

Draft
calvinmclean wants to merge 6 commits into
obot-platform:feat/7376-catalog-overhaulfrom
calvinmclean:feat/digitalocean-remote
Draft

enhance: add official DigitalOcean remote#1392
calvinmclean wants to merge 6 commits into
obot-platform:feat/7376-catalog-overhaulfrom
calvinmclean:feat/digitalocean-remote

Conversation

@calvinmclean

@calvinmclean calvinmclean commented Aug 10, 2026

Copy link
Copy Markdown
Member

Summary

Replaces the existing containerized DigitalOcean catalog entry with DigitalOcean's official remote MCP services. The entry retains its existing entryKey, so catalog users receive the remote implementation as an update rather than a parallel entry.

Authentication remains unchanged: users provide a DigitalOcean personal access token, sent as a bearer Authorization header.

Service Selection

Users select a single supported DigitalOcean service. The selected value determines the remote MCP subdomain, for example https://droplets.mcp.digitalocean.com/mcp. Because each remote subdomain exposes a separate MCP server, one entry instance cannot select multiple services.

Tool Preview

This entry intentionally has no tool preview. Tool sets differ by selected service subdomain, so a single preview would be incomplete or misleading.

Changes

  • Replaces the container runtime and bundled image with the official remote service URL template.
  • Replaces ENABLED_SERVICES with a constrained single-service selector.
  • Removes the container-specific tool preview.
  • Retains PAT authentication and the existing catalog entry identity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant