Daytona (BYOK) — connector documentation
- MCP endpoint:
https://byok-daytona.connectorbay.com/mcp - REST API:
POST https://byok-daytona.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-daytona.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Daytona API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-daytona.connectorbay.com/health· Tool schemas:https://byok-daytona.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-daytona · agent@connectorbay.com
What Daytona (BYOK) is for
Daytona (BYOK) lets an AI assistant read your own Daytona data through the Daytona API with a key you supply (API key). Read-only: 9 tools (list_sandboxes, get_sandbox, list_snapshots, list_volumes, list_organizations, get_organization_usage, list_regions, get_current_user, get_current_api_key). 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 app.daytona.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Daytona. Daytona 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 Daytona sandboxes are started right now?"
- "Show the details of my Daytona sandbox called my-sandbox"
- "Which Daytona snapshots do I have and when were they last used?"
- "What Daytona volumes does my organization have?"
- "Which Daytona organizations am I in, and what are their limits?"
- "How much of my Daytona quota am I using?"
What it does
list_sandboxes: List your Daytona sandboxes with state, snapshot, CPU, memory and disk, labels and activity times; page with the cursor. Eventually consistent.get_sandbox: Get one sandbox: state, desired state, snapshot, resources, labels, network flags, volumes, auto-stop, auto-archive and auto-delete intervals and activity times.list_snapshots: List snapshots (the images sandboxes start from) with state, resources, size and last use, one page at a time.list_volumes: List the persistent volumes of your organization with state and last use.list_organizations: List the Daytona organizations the key can see, with limits per sandbox, suspension flag, default region and rate limits.get_organization_usage: Show quota and current usage of one organization per region (CPU, memory, disk, GPU) plus snapshot and volume quotas.list_regions: List the regions your organization can run sandboxes in, with type and ID.get_current_user: Show the Daytona user the key belongs to: id, name, email and creation date.get_current_api_key: Show details of the API key in use: name, permissions, creation, last use and expiry (the key value is not returned).
BYOK key
You bring your own Daytona API key (https://app.daytona.io/dashboard/keys). 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 app.daytona.io 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
- https://www.daytona.io/docs/en/tools/api (the API this connector calls, with a BYOK key)
Live from the Daytona API (app.daytona.io) with a BYOK key; documentation: https://www.daytona.io/docs/en/tools/api. 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 Daytona. Daytona 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 Daytona account.
Built for: Worldwide. Languages: English.