ChromaSAFE
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Chroma - the open-source embedding database. The fastest way to build Python or JavaScript LLM apps with memory!
Docs
Homepage
[](https://smithery.ai/server/@chroma-core/chroma-mcp)
The Model Context Protocol (MCP) is an open protocol designed for effortless integration between LLM applications and external data sources or tools, offering a standardized framework to seamlessly provide LLMs with the context they require.
This server provides data retrieval capabilities powered by Chroma, enabling AI models to create collections over generated data and user inputs, and retrieve that data using vector search, full text search, metadata filtering, and more.
This is a MCP server for self-hosting your access to Chroma. If you are looking for Package Search you can find the repository for that here.
Features
- Flexible Client Types
- Ephemeral (in-memory) for testing and development
- Persistent for file-based storage
- HTTP client for self-hosted Chroma instances
c5743d0ea7e2OBSERVED · 2026-09-29Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add chroma-mcp --env CHROMA_API_KEY=${CHROMA_API_KEY} --env CHROMA_CUSTOM_AUTH_CREDENTIALS=${CHROMA_CUSTOM_AUTH_CREDENTIALS} -- uvx chroma-mcp{
"mcpServers": {
"chroma-mcp": {
"command": "uvx",
"args": [
"chroma-mcp"
],
"env": {
"CHROMA_API_KEY": "${CHROMA_API_KEY}",
"CHROMA_CUSTOM_AUTH_CREDENTIALS": "${CHROMA_CUSTOM_AUTH_CREDENTIALS}"
}
}
}
}Exposed tools (13)
7 read · 4 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
chroma_add_documents | write | Add documents to a Chroma collection. |
chroma_create_collection | write | Create a new Chroma collection with configurable HNSW parameters. |
chroma_delete_collection | destructive | Delete a Chroma collection. |
chroma_delete_documents | destructive | Delete documents from a Chroma collection. |
chroma_fork_collection | read | Fork a Chroma collection. |
chroma_get_collection_count | read | Get the number of documents in a Chroma collection. |
chroma_get_collection_info | read | Get information about a Chroma collection. |
chroma_get_documents | read | Get documents from a Chroma collection with optional filtering. |
chroma_list_collections | read | List all collection names in the Chroma database with pagination support. |
chroma_modify_collection | write | Modify a Chroma collection |
chroma_peek_collection | read | Peek at documents in a Chroma collection. |
chroma_query_documents | read | Query documents from a Chroma collection with advanced filtering. |
chroma_update_documents | write | Update documents in a Chroma collection. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (3)
chroma_delete_collection, chroma_delete_documents
You can also use environment variables to configure the client. The server will automatically load variables from a `.env` file located at the path specified by `--dotenv-path` (defaults to `.chroma_e
When using external embedding functions that access an API key, follow the naming convention
Gates applied: no_behavioural_pass.
c5743d0ea7e2full audit observations/trust-audit/mcp-server/chroma-core__chroma.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-09-29 | c5743d0ea7e2 | SAFE | B | 89 | first audit |
Questions
What is the Chroma MCP server?
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma
What tools does Chroma expose?
13 in total: 7 read-only, 4 that write, and 2 that can delete or overwrite (chroma_delete_collection, chroma_delete_documents). Every one is listed on this page with its risk.
Is Chroma safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Chroma need?
It reads CHROMA_API_KEY and CHROMA_CUSTOM_AUTH_CREDENTIALS from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Chroma run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as chroma-mcp.
How current is this page?
The grade is for one exact copy of the source (c5743d0ea7e2), read on 2026-09-29. The repository is watched and re-audited when it changes.