VECTOR DATA MANAGEMENT / Chroma
Chroma MCP
Lets an assistant create and query Chroma collections through local, HTTP or Chroma Cloud database connections.
“This is a MCP server for self-hosting your access to Chroma.”
01 / THE REASONING
Why this made the selection.
- Documents collection and document operations rather than claiming retrieval alone.
- Exposes persistent, ephemeral, HTTP and cloud Chroma connection choices in its configuration.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md (installation, capability and permission sections)
- pyproject.toml
- src/chroma_mcp/server.py
- LICENSE
- 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch.
Our findings
- The server entrypoint selects Chroma client and embedding configuration from CLI/environment settings.
- Chroma client types describe database connections, not four different MCP transports.
- Persistent mode needs --client-type persistent and an explicit --data-dir.
- Collection embedding choice is reused on retrieval; provider API keys are a separate dependency from Chroma database credentials.
Not established by this review
- Server startup, authentication and tool execution were not tested.
- No authenticated session, installation, permission bypass or package-to-source parity test was performed.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
uvx chroma-mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Select persistent, HTTP or cloud configuration if an ephemeral database is unsuitable.
- Configure database and optional embedding-provider credentials outside the prompt.
- The command above is the command and args of the README’s ephemeral Claude Desktop block (uvx with chroma-mcp), not a separate installer. It was not run.
Before you start
- uv/Python; database connection details and embedding-provider credentials when required.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
"chroma": {
"command": "uvx",
"args": [
"chroma-mcp"
]
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Official documentation ↗Checked
https://github.com/chroma-core/chroma-mcp/blob/98ff67589bdcc31b730a5415ff9529433f949077/README.md
Supports: summary, whySelected, bestFor, limitations, install, access, compatibility, transports, configExample, review
- Applicable source licence ↗Checked
https://github.com/chroma-core/chroma-mcp/blob/98ff67589bdcc31b730a5415ff9529433f949077/LICENSE
Supports: license
https://github.com/chroma-core/chroma-mcp/blob/98ff67589bdcc31b730a5415ff9529433f949077/pyproject.toml
Supports: language, review
https://github.com/chroma-core/chroma-mcp/blob/98ff67589bdcc31b730a5415ff9529433f949077/src/chroma_mcp/server.py
Supports: language, review