1. Conduid
  2. AI
  3. Chroma MCP Server
MCP server · AI

Chroma MCP Server

MCP Server for ChromaDB integration into Cursor with MCP compatible AI models

Unclaimed NOASSERTION last commit a year ago ai
54Fair

Scored 3 months ago · breakdown

About Chroma MCP Server

Chroma MCP Server is an MCP server published by djm81 in the AI category: mCP Server for ChromaDB integration into Cursor with MCP compatible AI models. It has been installed 0 times through Conduid.

The repository has 26 stars and 9 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx chroma-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Chroma MCP Server

Powered by Claude · Grounded in docs

I know everything about Chroma MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Chroma MCP Server

CI codecov PyPI - Version

A Model Context Protocol (MCP) server integration for Chroma, the open-source embedding database.

Overview

Chroma MCP Server creates a persistent, searchable "working memory" for AI-assisted development:

  • Automated Context Recall: AI assistants can query relevant information from past sessions
  • Developer-Managed Persistence: Store key decisions and insights in ChromaDB via MCP
  • Second Brain Integration: Integrates with IDE workflows to create a unified knowledge hub

Key features:

  • Automated Codebase Indexing: Track and index code changes
  • Automated Chat Logging: Log AI interactions with enhanced context capture (code diffs, tool sequences)
  • Bidirectional Linking: Connect discussions to code changes for tracing feature evolution
  • Semantic Code Chunking: Preserve logical code structures for more meaningful context retrieval
  • Working Memory Tools: MCP commands for capturing and retrieving development context
  • Validation System: Evidence-based validation for code changes and learning promotions
  • Automated Test-Driven Learning: Fully automated workflow from test failure to verified fix and learning promotion. See the Pytest Plugin Usage Guide to integrate this into your projects.

See the Getting Started with your Second Brain guide for more details.

Quick Start

Installation

# Basic installation
pip install chroma-mcp-server

# Full installation with all embedding models
pip install "chroma-mcp-server[full]"

Running

# With in-memory storage (data lost on restart)
chroma-mcp-server --client-type ephemeral

# With persistent storage
chroma-mcp-server --client-type persistent --data-dir ./my_data

Cursor Integration

Add or modify .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "chroma": {
      "command": "uvx",
      "args": [
        "chroma-mcp-server"
      ],
      "env": {
        "CHROMA_CLIENT_TYPE": "persistent",
        "CHROMA_DATA_DIR": "/path/to/your/data",
        "CHROMA_LOG_DIR": "/path/to/your/logs",
        "LOG_LEVEL": "INFO",
        "MCP_LOG_LEVEL": "INFO",
        "MCP_SERVER_LOG_LEVEL": "INFO"
      }
    }
  }
}

Recent Improvements

  • Enhanced Context Capture: Automatically extracts code diffs, tool sequences, and assigns confidence scores
  • Bidirectional Linking: Creates navigable connections between chat discussions and code changes
  • Semantic Code Chunking: Uses logical boundaries (functions, classes) instead of fixed-size chunks
  • Server-Side Timestamp Enforcement: Ensures consistent timestamps across all collections
  • Automatic Collection Creation: Essential collections (e.g., chat_history_v1, codebase_v1) are automatically created on server startup if they don't exist.
  • Enhanced Logging System: Per-execution log files prevent contamination of JSON communication in stdio mode
  • Embedding Function Management: Tools to update collection metadata when changing embedding functions
  • Collection Setup Command: Simplifies creation of multiple collections with consistent configuration
  • Auto-Promote Workflow: Streamlined derived learning promotion with automatic handling of high-confidence entries
  • Smart Defaults: Interactive promotion with intelligent defaults for all fields based on context
  • Low Confidence Warnings: Visual indicators for entries that may need more careful review
  • Automated Test Workflow: Fully automated capture of test failures, monitoring for fixes, and validated learning promotion

Documentation

Comprehensive documentation is available in the docs directory:

License

Chroma MCP Server is licensed under the MIT License with Commons Clause. This means you can:

Allowed:

  • Use Chroma MCP Server for any purpose (personal, commercial, academic)
  • Modify the code
  • Distribute copies
  • Create and sell products built using Chroma MCP Server

Not Allowed:

  • Sell Chroma MCP Server itself
  • Offer Chroma MCP Server as a hosted service
  • Create competing products based on Chroma MCP Server

See the LICENSE.md file for the complete license text.

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About Chroma MCP Server

How do I install Chroma MCP Server?

Run npx chroma-mcp-server, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Chroma MCP Server safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Chroma MCP Server still maintained?

The last commit was a year ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.