Chroma Working Memory▌

by djm81
Chroma Working Memory offers a persistent, searchable 'second brain' for developers with ChromaDB, codebase indexing, an
Provides a persistent, searchable, automatically updated 'second brain' for development by integrating ChromaDB with automated codebase indexing, chat logging, and sequential thinking tools that maintain context across sessions.
best for
- / Developers wanting persistent context in AI coding sessions
- / Teams tracking evolution of features and decisions
- / Long-term projects requiring knowledge continuity
- / AI-assisted development workflows
capabilities
- / Index and search codebase changes automatically
- / Log AI chat conversations with code context
- / Query past development decisions and insights
- / Link discussions to specific code changes
- / Capture and retrieve working memory across sessions
- / Validate code changes with evidence-based system
what it does
Creates a persistent, searchable 'second brain' for development by automatically indexing your codebase, logging AI conversations, and maintaining context across sessions using ChromaDB.
about
Chroma Working Memory is a community-built MCP server published by djm81 that provides AI assistants with tools and capabilities via the Model Context Protocol. Chroma Working Memory offers a persistent, searchable 'second brain' for developers with ChromaDB, codebase indexing, an It is categorized under ai ml, developer tools.
how to install
You can install Chroma Working Memory in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
NOASSERTION
Chroma Working Memory is released under the NOASSERTION license.
readme
Chroma MCP Server
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:
- Main Documentation - Complete guide to installation, configuration, and usage
- Getting Started - Detailed setup instructions
- Developer Guide - For contributors and developers
- IDE & Tool Integration Guides - Guides for integrating with IDEs and other tools.
- Automated Chat Logging - Enriched chat history with bidirectional linking
- Usage Guides - Detailed guides on how to use specific features and workflows.
- Enhanced Context Capture - Details on code diff extraction and tool sequencing
- Semantic Code Chunking - Logic-preserving code chunking for meaningful retrieval
- Automated Test Workflow (Pytest Plugin Usage) - Test-driven learning with automatic validation
- Thinking Tools & Utilities - Documentation for structured thinking and memory tools.
- Client and Developer Scripts - Guides for CLI tools and developer scripts.
- Logging Documentation - Overview of logging features and configuration.
- Server Logging - Details on the improved logging system
- Automation Documentation - Guides on automating development tasks.
- Project Rules & Guidelines - Development rules, guidelines, and best practices.
- Refactoring Plans - Documentation on various refactoring efforts and architectural plans.
- API Reference - Available MCP tools and parameters
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.
FAQ
- What is the Chroma Working Memory MCP server?
- Chroma Working Memory is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Chroma Working Memory?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Chroma Working Memory is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Chroma Working Memory against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Chroma Working Memory is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Chroma Working Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Chroma Working Memory for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Chroma Working Memory surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Chroma Working Memory has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Chroma Working Memory benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Chroma Working Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Chroma Working Memory is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.