MCP100 Assessment

Editorial verdict

Official Chroma MCP server for managing collections and retrieving vector/full-text/metadata-filtered data. Capabilities: Create/manage Chroma collections; Add and query collection data; Vector similarity search; Full-text search; Metadata-filtered retrieval; Connect to local, self-hosted HTTP, or Chroma Cloud backends

Reviewed October 21, 2026

Task Fit

Mapped

Working with structured data

Trust

Status warning

maintenance_source_health; client_coverage; tool_contract; install_supply_chain; advisory_freshness; adoption_evidence_presence

Maintenance

Date unavailable

No dated repository or package update is currently stored.

Popularity

Signals available

Visible usage signals are shown for discovery only, not as proof of safety.

Best for

Teams using Chroma that want MCP-native collection management and retrieval.

Not ideal for

Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.

Avoid if

Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.

Trade-offs

Write/index-poisoning risk plus tenant/auth configuration need stronger MCP-specific production evidence.

Evidence scope

Evidence

Current source snapshot

Popularity

601 MCP repository stars

125,570 package downloads · PyPI Stats last_month · Third-party

Repository identity: chroma-core/chroma-mcp

Package identity: chroma-mcp · version 0.2.6

PyPI Stats last_month · third-party estimate
Package evidence: exact. Exact current MCP implementation/distribution. Current official package/repo remain valid, but release activity is materially older than most peers; keep lifecycle freshness separate from source-health stale flag.
Observed 2026-10-21; source: https://pypistats.org/api/packages/chroma-mcp/recent

Stars observed October 21, 2026 · Downloads observed October 21, 2026

Repository evidence: exact. Exact current MCP implementation/distribution. Current official package/repo remain valid, but release activity is materially older than most peers; keep lifecycle freshness separate from source-health stale flag.

Package evidence: exact. Exact current MCP implementation/distribution. Current official package/repo remain valid, but release activity is materially older than most peers; keep lifecycle freshness separate from source-health stale flag.

Maintenance

Publisher activity observed October 21, 2026

Current source snapshot

Trust review

Source relationship: First-party MCP

Reviewed October 21, 2026

Sources

GitHub repository ↗Package registry ↗

Supporting evidence (2)

Source file: pyproject.toml ↗Evidence source ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Transport not recorded

Publisher documented

Use Chroma official config with `uvx chroma-mcp`; select ephemeral, persistent, or Chroma Cloud settings from the official README and register that exact stdio command in Claude Code.

The publisher provides client-specific setup instructions.

Verify safely: Claude Code: `claude mcp list` and/or `/mcp` to confirm Connected; use any stronger vendor-documented smoke test where listed.

Uninstall and revoke

Claude Code: `claude mcp remove <name>`; also revoke OAuth/device/API credentials in the vendor account when the vendor provides such a control.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-09-20T00:00:00.000Z

Evidence 1 ↗

Reviewed setup

Type-appropriate, source-backed setup for this mcp server profile.

Setup notes: Source rechecked October 21, 2026: Chroma MCP Server Lifecycle: source current not deprecated; latest public release 2025-08-14. Current official package/repo remain valid, but release activity is materially older than most peers; keep lifecycle freshness separate from source-health stale flag.

Show source-catalog configuration

Use Chroma official config with `uvx chroma-mcp`; select ephemeral, persistent, or Chroma Cloud settings from the official README and register that exact stdio command in Claude Code.

Capability

What it does

Official Chroma MCP server for managing collections and retrieving vector/full-text/metadata-filtered data. Capabilities: Create/manage Chroma collections; Add and query collection data; Vector similarity search; Full-text search; Metadata-filtered retrieval; Connect to local, self-hosted HTTP, or Chroma Cloud backends

Data & DatabasesSoftware & Technology

Representative uses

Teams using Chroma that want MCP-native collection management and retrieval.

Important limits

Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.

Context Footprint

Not measured yet

Estimated token footprint of the MCP tool schemas exposed to the agent.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Chroma Cloud uses an API key; self-hosted HTTP can use custom authentication credentials; local modes may have no network auth.
Permissions: Can read and mutate collections/data available to the configured Chroma client.
Data handling: Vector/document content is stored in the configured local, self-hosted, or Chroma Cloud backend and exposed to the connected AI client.
Cost: Open-source server; Chroma Cloud, embedding providers and infrastructure may be billable.
Risk and cautions: Write/index-poisoning risk plus tenant/auth configuration need stronger MCP-specific production evidence.

Related reviewed MCPs

Other options

Google MCP Toolbox for Databases

MCP100 Recommended

Connect MCP clients to enterprise databases with prebuilt or explicitly defined tools.

Choose this instead if

Choose Google MCP Toolbox for Databases instead if schema exploration and database-aware coding in development environments.

Connect MCP clients to enterprise databases with prebuilt or explicitly defined tools.

Compare with Chroma View Google MCP Toolbox for Databases details

Redis MCP

MCP100 Recommended

Manage and search Redis data through Redis's MCP server.

Choose this instead if

Choose Redis MCP instead if inspecting and manipulating Redis strings, hashes, lists, sets, sorted sets, streams, JSON, and search indexes.

Manage and search Redis data through Redis's MCP server.

Compare with Chroma View Redis MCP details

Supabase MCP

MCP100 Recommended

Connect AI tools to Supabase projects and development workflows.

Choose this instead if

Choose Supabase MCP instead if inspecting one Supabase project's schema, logs, advisors, and docs.

Connect AI tools to Supabase projects and development workflows.

Compare with Chroma View Supabase MCP details

Read publisher documentation

Publisher documentation

MCP100 source-backed summary

A concise MCP100 summary built from the reviewed publisher sources. It is not a publisher README; use the original link for the latest full documentation.

View original README ↗

Chroma

Official Chroma MCP server for managing collections and retrieving vector/full-text/metadata-filtered data. Capabilities: Create/manage Chroma collections; Add and query collection data; Vector similarity search; Full-text search; Metadata-filtered retrieval; Connect to local, self-hosted HTTP, or Chroma Cloud backends

What it can help with

Teams using Chroma that want MCP-native collection management and retrieval.

Important limits

Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.

Loading optional publisher documentation…

FAQ

Is this an official MCP?

github:chroma-core is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Publisher documentation ↗