Skip to content

MCP server

Chroma MCP server

Chroma's official MCP server lets AI create collections, add, query, update and delete documents in a Chroma vector database, local or cloud.

At a glance

Maintained by
Chroma
Tools exposed
10 listed below
Reviewed
September 24, 2026

Why it matters

What it does and why it matters

Chroma is an open-source vector database that is easy to run locally and also available as a cloud service. Its official MCP server gives an assistant full control of collections and documents: create, add, query, update and delete. It works with a temporary in-memory database, a local folder or Chroma Cloud.

That makes it a practical choice for prototypes and small knowledge assistants, where a team wants search by meaning without running heavy infrastructure.

Because it has full read and write access, including deleting whole collections, we keep it to local or development data during building. For production use, a curated collection with a separate loading process and search-only access through your app is safer.

Use cases

Best business use cases

Local prototypes

Try semantic search on a laptop in minutes.

Assistant memory

Store and recall notes by meaning.

Document search

Search small document sets by meaning.

RAG testing

Test chunking and retrieval choices quickly.

Cloud collections

Work with Chroma Cloud collections.

Tools

Available tools

Tool names as published by the maintainer at review time. Versions change, so check the repository for the current list.

Read and write: Full read and write, including deleting documents and collections.

  • chroma_list_collections

    Lists collections with paging.

  • chroma_create_collection

    Creates a collection with optional HNSW settings.

  • chroma_peek_collection

    Shows sample documents from a collection.

  • chroma_get_collection_info

    Gets collection details.

  • chroma_add_documents

    Adds documents with optional metadata and IDs.

  • chroma_query_documents

    Runs semantic search with filters.

  • chroma_get_documents

    Gets documents by ID or filter.

  • chroma_update_documents

    Updates document content, metadata or embeddings.

  • chroma_delete_documents

    Deletes specific documents.

  • chroma_delete_collection

    Deletes a collection.

Workflows

Example workflows

Test a retrieval idea locally

  1. 1

    Start the server with a local persistent folder.

  2. 2

    Create a collection for sample documents.

  3. 3

    Add documents through the assistant.

  4. 4

    Run real questions as queries.

  5. 5

    Adjust chunking and repeat.

Clean up a collection

  1. 1

    Peek at the collection contents.

  2. 2

    Find outdated documents by metadata.

  3. 3

    Review the list the assistant returns.

  4. 4

    Approve updates or deletions.

  5. 5

    Re-run test queries.

Prompts

Example prompts

  • “Create a collection called policies and add these three documents.”

  • “Query the policies collection for "remote work equipment" and show the top five.”

  • “List documents in the collection updated before 2025.”

Setup

Installation and configuration

Examples for Claude Desktop and Claude Code. Replace the placeholder values with your own keys, and store secrets outside version control.

Claude Desktop: claude_desktop_config.json

{
    "mcpServers": {
        "chroma": {
            "command": "uvx",
            "args": [
                "chroma-mcp",
                "--client-type",
                "cloud",
                "--tenant",
                "your-tenant-id",
                "--database",
                "your-database-name",
                "--api-key",
                "your-api-key"
            ]
        }
    }
}

Claude Code: terminal

claude mcp add chroma -- uvx chroma-mcp --client-type persistent --data-dir /full/path/to/your/data/directory
  • Local server: stdio. PyPI: chroma-mcp (uvx chroma-mcp). Client types: ephemeral, persistent, http, cloud.
  • Needs: None for ephemeral or persistent local use; Chroma Cloud: tenant, database, API key (CHROMA_TENANT, CHROMA_DATABASE, CHROMA_API_KEY); Optional embedding provider keys: CHROMA_<PROVIDER>_API_KEY.

Security

Security considerations

  • Development data

    Use local or development collections while building.

  • Review deletes

    Confirm before deleting documents or collections.

  • Cloud credentials

    Scope Chroma Cloud keys to one database.

  • Personal data

    Avoid storing personal data in test collections.

Related servers

Servers that pair well with it

Qdrant

Qdrant's official MCP server gives AI a semantic memory: store information in a Qdrant collection and find it again by meaning.

Pinecone

Pinecone's official developer MCP server lets AI search Pinecone docs, manage indexes, upsert records, search and rerank.

Weaviate

An MCP server built into Weaviate that lets AI read collection settings, list tenants, run hybrid search and, when allowed, upsert objects.

Keep exploring

FAQ

Questions people ask us

Have a question that is not here? Ask us directly.

Start a project

Want this connected to your own systems? We build AI workflows with MCP.

Send a short brief. We reply with questions, a suggested plan and an estimate you can compare with other offers.

Your privacy choices

We use necessary storage to run this site. With your permission we also use Google Analytics to see which pages help people, and load maps from Google. You can change this at any time. Read the cookie policy.