Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Digital Ocean Spaces and CDN (BYOK) — connector documentation

  • MCP endpoint: https://byok-digitalocean-spaces-cdn.connectorbay.com/mcp
  • REST API: POST https://byok-digitalocean-spaces-cdn.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-digitalocean-spaces-cdn.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Digital Ocean Spaces and CDN personal access token with CDN, certificate and Spaces key read scope, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-digitalocean-spaces-cdn.connectorbay.com/health · Tool schemas: https://byok-digitalocean-spaces-cdn.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-digitalocean-spaces-cdn · agent@connectorbay.com

What Digital Ocean Spaces and CDN (BYOK) is for

Digital Ocean Spaces and CDN (BYOK) lets an AI assistant read your own Digital Ocean Spaces and CDN data through the Digital Ocean Spaces and CDN API with a key you supply (personal access token with CDN, certificate and Spaces key read scope). Read-only: 5 tools (list_cdn_endpoints, get_cdn_endpoint, list_certificates, get_certificate, list_spaces_keys). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.digitalocean.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Digital Ocean Spaces and CDN. Digital Ocean Spaces and CDN and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Spaces buckets have a CDN and on what custom domain?"
  • "What TTL does CDN endpoint 19f06b6a use?"
  • "Which SSL certificates do I have and when do they expire?"
  • "When does certificate 892071a0 expire?"
  • "Which Spaces keys exist and which buckets can they access?"

What it does

  • list_cdn_endpoints: List Spaces CDN endpoints with origin, edge endpoint, TTL, custom domain and certificate.
  • get_cdn_endpoint: Get one CDN endpoint: origin, edge endpoint, TTL, custom domain and certificate id.
  • list_certificates: List SSL certificates with state, type (custom or Let's Encrypt), DNS names, expiry and fingerprint.
  • get_certificate: Get one SSL certificate: state, type, DNS names and expiry.
  • list_spaces_keys: List Spaces access keys with name, access key id, creation time and bucket grants (bucket and permission). Only access key ids and bucket grants are returned, never secrets.

BYOK key

You bring your own Digital Ocean Spaces and CDN personal access token with CDN, certificate and Spaces key read scope (https://cloud.digitalocean.com/account/api/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.digitalocean.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Digital Ocean Spaces and CDN API (api.digitalocean.com) with a BYOK key; documentation: https://docs.digitalocean.com/reference/api/reference/cdn/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Digital Ocean Spaces and CDN. Digital Ocean Spaces and CDN and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Digital Ocean Spaces and CDN account.

Built for: Worldwide. Languages: English.