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

Chroma Cloud (BYOK) — connector documentation

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

What Chroma Cloud (BYOK) is for

Chroma Cloud (BYOK) lets an AI assistant read your own Chroma Cloud data through the Chroma Cloud API with a key you supply (Chroma Cloud API key). Read-only: 10 tools (get_user_identity, get_tenant, list_databases, get_database, list_collections, get_collection, count_collections, count_records, get_indexing_status, get_record). 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.trychroma.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Chroma Cloud. Chroma Cloud 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 Chroma Cloud tenant and databases does my key belong to?"
  • "Show my Chroma tenant my-tenant"
  • "Which databases are in my Chroma tenant?"
  • "Show my Chroma database my-database"
  • "What collections are in my Chroma database?"
  • "Show Chroma collection 3f2504e0-4f89-41d3-9a0c-0305e82c3301"

What it does

  • get_user_identity: Show the identity of the key: user id, tenant name and the databases it can reach.
  • get_tenant: Get one Chroma tenant by name.
  • list_databases: List the databases of a tenant with id and name.
  • get_database: Get one Chroma database by name: id, name and tenant.
  • list_collections: List the collections of a database with id, name, dimension, metadata and version.
  • get_collection: Get one collection by id: name, dimension, metadata, log position and version.
  • count_collections: Count the collections in a database. The answer is a single number.
  • count_records: Count the records in a collection. The answer is a single number.
  • get_indexing_status: Show how many operations of a collection are indexed or still waiting, with progress.
  • get_record: Get one record of a collection by its id: the stored document text and metadata (embeddings are not returned).

BYOK key

You bring your own Chroma Cloud Chroma Cloud API key (https://trychroma.com/). 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.trychroma.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 Chroma Cloud API (api.trychroma.com) with a BYOK key; documentation: https://docs.trychroma.com/reference/chroma-api/database/list-databases. 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 Chroma Cloud. Chroma Cloud 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 Chroma Cloud account.

Built for: Worldwide. Languages: English.