Official Chroma MCP server for connecting Claude to Chroma collections, documents, semantic search, full-text search, metadata filtering, persistent storage, self-hosted Chroma, and Chroma Cloud.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
6 safety and 4 privacy notes across 6 risk areas. Review closely: credentials & tokens, permissions & scopes, network access, third-party handling.
{
"mcpServers": {
"chroma": {
"command": "uvx",
"args": ["chroma-mcp"]
}
}
}Chroma MCP Server is the official Chroma Model Context Protocol server for self-hosting Claude access to Chroma data retrieval workflows. It connects MCP clients to Chroma collections and documents through ephemeral, persistent, HTTP, or Chroma Cloud client modes.
The server supports collection management, document ingestion, semantic search, full-text search, metadata filtering, document retrieval, document updates, and document deletion. It can also use several embedding functions, including default, Cohere, OpenAI, Jina, Voyage AI, and Roboflow.
These sources were reviewed on 2026-06-06. Prefer the Chroma docs, repository README, PyPI metadata, package metadata, server implementation, and license for current setup commands, supported tools, client modes, embedding providers, and authentication behavior.
chroma-core/chroma-mcp.uvx chroma-mcp.api.trychroma.com.For an ephemeral local client:
{
"mcpServers": {
"chroma": {
"command": "uvx",
"args": ["chroma-mcp"]
}
}
}
For durable or remote use, follow the README's persistent, HTTP, and cloud configuration examples. Prefer environment variables or a reviewed dotenv file for credentials instead of putting API keys directly into shared MCP config.
Chroma MCP is a retrieval database control surface, not just a read-only search helper. It can add, update, and delete indexed content, and remote modes can touch shared production or team databases. Require explicit approval for collection creation, document writes, document updates, document deletion, and collection deletion.
Treat retrieved context as untrusted input until it is checked for relevance, freshness, permissions, and prompt-injection risk. Keep API keys and custom auth credentials out of prompts and version control, and review whether embedding providers or Chroma Cloud are approved for the documents being indexed.
Chroma includes an Apache-2.0 open-source project and hosted Chroma Cloud offerings. This listing is not sponsored, paid, or affiliate-driven, and it is scoped to the source-backed MCP server.
Existing content includes a general Chroma tools entry in content/tools, but
no Chroma MCP Server entry was found in content/mcp. This submission is scoped
to chroma-core/chroma-mcp, the official MCP server, and does not change the
existing Chroma database listing.
Show that Chroma MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/chroma-mcp-server)Chroma MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
| Field | Official Chroma MCP server for connecting Claude to Chroma collections, documents, semantic search, full-text search, metadata filtering, persistent storage, self-hosted Chroma, and Chroma Cloud. Open dossier | Official Pinecone Developer MCP server that connects Claude and other MCP clients to Pinecone projects and documentation for index management, record upserts, semantic search, cascading multi-index search, reranking, and documentation lookup over integrated-inference indexes. Open dossier | MCP server from Zilliz for connecting Claude to Milvus vector database collections, text search, vector search, hybrid search, inserts, deletes, indexes, collection loading, database switching, and collection metadata. Open dossier | Connect Claude to a Weaviate vector database — run hybrid search, inspect collection config, list tenants, and upsert objects — using Weaviate's built-in Model Context Protocol server. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | oktofeesh1 | JSONbored | oktofeesh1 | — |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | |||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Chroma | Pinecone | Zilliz | Weaviate |
| Added | 2026-06-06 | 2026-06-11 | 2026-06-06 | 2026-06-17 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Chroma MCP can create, modify, and delete collections. Document tools can add, update, query, retrieve, and delete documents, metadata, custom IDs, and embeddings. Persistent, HTTP, and cloud modes can mutate durable retrieval stores rather than temporary test collections. External embedding functions can send document text or image-derived content to third-party embedding providers. Chroma Cloud and self-hosted HTTP modes require careful handling of tenants, databases, API keys, custom auth credentials, SSL settings, and network exposure. Retrieved context can influence Claude output even when stale, irrelevant, over-broad, or not authorized for the task. | ✓The server can create indexes and upsert records, so an agent with a write-capable API key can change live Pinecone project state. Run the npm package `@pinecone-database/mcp` through `npx`, which downloads and executes the published package on each launch; pin to a trusted version if reproducibility matters. Scope the Pinecone API key to the intended project and use read-only or least-privilege keys when index creation and writes are not needed. Require human review before `create-index-for-model` and `upsert-records` runs that mutate production indexes. | ✓Milvus MCP can read collection metadata, query collections, and run text, vector, text-similarity, multi-vector, and hybrid searches. Write-capable tools can create collections, insert data, upsert data, delete entities, create indexes, bulk insert records, load collections, release collections, and switch databases. The README notes that the environment file has higher priority than command-line arguments, so stale or unexpected environment settings can silently change the target Milvus instance. SSE and Streamable HTTP modes can expose database operations over HTTP and should be network-restricted. Remote Milvus or Zilliz Cloud credentials should be scoped to the collections and databases Claude is allowed to access. | ✓The MCP server runs inside your Weaviate instance and respects its existing RBAC; scope the API key to least privilege. The object-upsert tool writes data — restrict write access to the collections Claude should modify. |
| Privacy notes | ✓Collections can store source documents, chunks, embeddings, metadata, IDs, filters, and query results that reveal private project, customer, or research data. Query text, retrieved documents, metadata filters, and embedding inputs may expose sensitive information to Chroma Cloud, self-hosted operators, embedding providers, logs, or downstream model providers. CHROMA_API_KEY, custom auth credentials, embedding provider API keys, tenant IDs, database names, hostnames, and dotenv files should stay out of prompts, issues, logs, screenshots, and committed files. Persistent data directories and exported collections need the same access control, backup, encryption, and retention review as the source documents they index. | ✓The `PINECONE_API_KEY` is read from the MCP client environment and grants access to the associated Pinecone project; keep it out of prompts, notes, and committed files. Index names, configurations, namespaces, statistics, record contents, and search queries can be exposed to the MCP client and model provider. Records and search text may contain embedded documents, customer data, or proprietary content, so review what is sent into indexes and returned by searches. Documentation search and tool calls reach Pinecone endpoints such as api.pinecone.io, so network access and request metadata leave the local machine. | ✓Milvus collections can contain embeddings, sparse vectors, scalar fields, IDs, document chunks, metadata, image or multimodal references, query logs, and retrieval results that reveal sensitive project or user data. Milvus URI, tokens, database names, collection names, vector payloads, filter expressions, and retrieved records should stay out of prompts, issues, logs, screenshots, and committed files. Search results can include private source content that may be re-exposed in model transcripts or downstream tickets. HTTP transports, debug tools, query traces, failed-search artifacts, backups, and benchmark datasets need retention and access-control review. | ✓Query text, retrieved objects, and collection metadata enter the MCP client context and the model's prompt. The Weaviate endpoint URL and API key are secrets — keep them in the client config or environment, not in shared repositories. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude to Pinecone projects and docs to list and describe indexes, create integrated-inference indexes, upsert and search records, run cascading search, and rerank results.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.