Digital Ocean Spaces and CDN (BYOK)
Read your DigitalOcean Spaces CDN endpoints, SSL certificates and Spaces access key grants with your own API token (bucket contents need the separate S3 API)
Read your env0 organizations, projects, environments, deployments, templates, agents and costs with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_organizationslist_projectslist_environmentsget_environmentlist_deploymentslist_templatesenv0 (BYOK) lets an AI assistant read your own env0 data through the env0 API with a key you supply (API key ID). Read-only: 8 tools (list_organizations, list_projects, list_environments, get_environment, list_deployments, list_templates, list_agents, get_organization_costs). 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.env0.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by env0. env0 and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the env0 API (api.env0.com) with a BYOK key; documentation: https://docs.envzero.com/api-reference/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
8 tools, grouped by job. Every one is read-only or compute-only.
https://byok-env0.connectorbay.com/mcpThree ways in, the same 8 tools.
https://byok-env0.connectorbay.com/mcpPOST https://byok-env0.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-env0.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.envzero.com).env0 (BYOK) lets an AI assistant read your own env0 data through the env0 API with a key you supply (API key ID). It is a hosted MCP server with 8 tools such as List organizations, List projects, List environments, Get environment, List deployments, List templates, published by Unify Dynamics LLC. It is independent and not affiliated with env0.
Add the MCP endpoint https://byok-env0.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-env0.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-env0.json.
Yes: this is a bring-your-own-key connector. Create a API key ID at https://docs.envzero.com/guides/admin-guide/user-and-organization-management/api-keys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your DigitalOcean Spaces CDN endpoints, SSL certificates and Spaces access key grants with your own API token (bucket contents need the separate S3 API)
Read your DigitalOcean block storage volumes, snapshots, images and NFS shares with your own API token
Read your DigitalOcean Uptime checks, their alerts and current regional state, plus Insights alert rules and alert instances, with your own API token
Read Discord's public catalog data (sticker packs, default sounds, voice regions, server templates, gateway limits, stage instances) with your own bot token (read-only)
Read your Disruptive Technologies (DT Studio) wireless sensors: organizations, projects, devices, their latest status and historical sensor events with a service account key
Read your DNSimple accounts, domains, DNS zones and records, email forwards and certificate details with BYOK
https://byok-env0.connectorbay.com/mcpPOST https://byok-env0.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-env0.connectorbay.com/openapi.jsonX-Upstream-Key header and the API key secret in X-Upstream-Key-2 of every request (never stored, logged or cached)https://byok-env0.connectorbay.com/health · Tool schemas: https://byok-env0.connectorbay.com/tools.jsonenv0 (BYOK) lets an AI assistant read your own env0 data through the env0 API with a key you supply (API key ID). Read-only: 8 tools (list_organizations, list_projects, list_environments, get_environment, list_deployments, list_templates, list_agents, get_organization_costs). 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.env0.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by env0. env0 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:
list_organizations: List the env0 organizations the API key belongs to with name, role, billing mode and creation date.list_projects: List an organization's env0 projects with name, description, tags, parent project and archive flag.list_environments: List env0 environments with status, drift status, project, workspace name and tags, filterable by project, name, drift status and activity.get_environment: Get one env0 environment: status, drift status, lock state, auto-destroy time, tags and its latest deployment ID.list_deployments: List deployments of an env0 environment with type, status, start and finish times, template and revision, resource count and failed command.list_templates: List env0 templates (the IaC sources environments deploy from) with repository, revision, path, type and Terraform or OpenTofu version.list_agents: List the agents that run env0 deployments with name, status, SaaS or self-hosted, default flag, version and queue health.get_organization_costs: Get cloud cost data points of an organization by date and provider (AWS, GCP, Azure) for a timespan, optionally accumulated.You bring your own env0 API key ID (https://docs.envzero.com/guides/admin-guide/user-and-organization-management/api-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 api.env0.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.
Live from the env0 API (api.env0.com) with a BYOK key; documentation: https://docs.envzero.com/api-reference/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by env0. env0 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 env0 account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What env0 (BYOK) is. env0 (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own env0 data: Read your env0 organizations, projects, environments, deployments, templates, agents and costs with your own API key. You bring your own env0 API key ID; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one env0 call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.env0.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If env0 rejects it, we say so without repeating it.
What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What env0 receives. The request we make on your behalf, including the key and the arguments, under env0's own terms and privacy policy. env0 acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer env0 gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.
What we do not do. We do not build a profile, sell or share personal information, or keep your env0 data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.
Sub-processors. env0 (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).
Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at env0 at any time to end all access.
Children. env0 (BYOK) is a general-audience service operated by the adult using the assistant, under env0's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the env0 (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-env0.connectorbay.com/mcphttps://byok-env0.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. env0 (BYOK) never asks for them.