Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
env0 (BYOK) icon

env0 (BYOK)

Read your env0 organizations, projects, environments, deployments, templates, agents and costs with your own API key

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
Providerenv0unofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which env0 organizations can my key access?
Tools called
list_organizations
What projects exist in my env0 organization?
Tools called
list_projects
Which env0 environments are drifted or failing?
Tools called
list_environments
Show the details of this env0 environment
Tools called
get_environment
How did the recent deployments of this env0 environment go?
Tools called
list_deployments
What templates does my env0 organization have?
Tools called
list_templates

About

env0 (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.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • List organizationsList the env0 organizations the API key belongs to with name, role, billing mode and creation date.
  • List projectsList an organization's env0 projects with name, description, tags, parent project and archive flag.
  • List environmentsList env0 environments with status, drift status, project, workspace name and tags, filterable by project, name, drift status and activity.
  • Get environmentGet one env0 environment: status, drift status, lock state, auto-destroy time, tags and its latest deployment ID.
  • List deploymentsList deployments of an env0 environment with type, status, start and finish times, template and revision, resource count and failed command.
  • List templatesList env0 templates (the IaC sources environments deploy from) with repository, revision, path, type and Terraform or OpenTofu version.
  • List agentsList the agents that run env0 deployments with name, status, SaaS or self-hosted, default flag, version and queue health.
  • Get organization costsGet cloud cost data points of an organization by date and provider (AWS, GCP, Azure) for a timespan, optionally accumulated.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-env0.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-env0.connectorbay.com/mcp
RESTPOST https://byok-env0.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-env0.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your API key ID in the X-Upstream-Key header (get one at docs.envzero.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

env0 connector: questions and answers

What is the env0 connector?

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.

How do I connect env0 to Claude, ChatGPT or Cursor?

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.

Do I need a env0 account or API key?

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.

Is env0 read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the env0 connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

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)

Live · MCP + REST5 tools

Digital Ocean Storage (BYOK)

Read your DigitalOcean block storage volumes, snapshots, images and NFS shares with your own API token

Live · MCP + REST10 tools

Digital Ocean Uptime and Insights (BYOK)

Read your DigitalOcean Uptime checks, their alerts and current regional state, plus Insights alert rules and alert instances, with your own API token

Live · MCP + REST7 tools

Discord Platform (BYOK)

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)

Live · MCP + REST9 tools

Disruptive Technologies (BYOK)

Read your Disruptive Technologies (DT Studio) wireless sensors: organizations, projects, devices, their latest status and historical sensor events with a service account key

Live · MCP + REST6 tools

DNSimple (BYOK)

Read your DNSimple accounts, domains, DNS zones and records, email forwards and certificate details with BYOK

Live · MCP + REST9 tools

Documentation

Back to top

env0 (BYOK) — connector documentation

  • MCP endpoint: https://byok-env0.connectorbay.com/mcp
  • REST API: POST https://byok-env0.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-env0.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own env0 API key ID, sent in the X-Upstream-Key header and the API key secret in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-env0.connectorbay.com/health · Tool schemas: https://byok-env0.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-env0 · agent@connectorbay.com

What env0 (BYOK) is for

env0 (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:

  • "Which env0 organizations can my key access?"
  • "What projects exist in my env0 organization?"
  • "Which env0 environments are drifted or failing?"
  • "Show the details of this env0 environment"
  • "How did the recent deployments of this env0 environment go?"
  • "What templates does my env0 organization have?"

What it does

  • 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.

BYOK key

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.

Data 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.

What it is not

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.

Privacy policy

Back to top

env0 (BYOK) — Privacy Policy

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.

Terms of service

Back to top

env0 (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the env0 (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. env0 (BYOK) provides: Read your env0 organizations, projects, environments, deployments, templates, agents and costs with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own env0 credentials and only access data you are allowed to access. env0's terms apply to your use of env0; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. 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.
  4. No advice, no guarantees. Output is the data env0 returns, lightly trimmed; it may be incomplete, delayed or changed by env0. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your env0 account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent env0's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; env0 may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your env0 key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action env0 takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-env0

env0 (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When 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.

Get env0 (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own env0 API key ID. Create one at https://docs.envzero.com/guides/admin-guide/user-and-organization-management/api-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to env0. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with env0.