Chroma Working Memory

Chroma Working Memory

djm81

Creates a persistent, searchable 'second brain' for development by automatically indexing your codebase, logging AI conversations, and maintaining context across sessions using ChromaDB.

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.

26596 views9Local (stdio)

What it does

  • 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

Best for

Developers wanting persistent context in AI coding sessionsTeams tracking evolution of features and decisionsLong-term projects requiring knowledge continuityAI-assisted development workflows
Automated codebase and chat indexingSemantic code chunking preserves logicBidirectional linking between code and discussions

About Chroma Working Memory

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

Chroma Working Memory is released under the NOASSERTION license.

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.

Alternatives

Related Skills

Browse all skills
reverse-engineering-tools

Guide for reverse engineering tools and techniques used in game security research. Use this skill when working with debuggers, disassemblers, memory analysis tools, binary analysis, or decompilers for game security research.

47
memory-mcp

Use and troubleshoot the Memory MCP server for episodic memory retrieval and pattern analysis. Use this skill when working with MCP server tools (query_memory, analyze_patterns, advanced_pattern_analysis), validating the MCP implementation, or debugging MCP server issues.

5
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
scroll

ALWAYS use when: building MCP servers, managing prompts/libraries, searching for skills, working with DAOs/governance, GitHub operations, or using Sage Protocol tools. Provides auto-provisioned MCP servers (memory, context7, brave/duckduckgo, github), skill discovery, and prompt management. Invoke with /scroll.

1
ccxt-typescript

CCXT cryptocurrency exchange library for TypeScript and JavaScript developers (Node.js and browser). Covers both REST API (standard) and WebSocket API (real-time). Helps install CCXT, connect to exchanges, fetch market data, place orders, stream live tickers/orderbooks, handle authentication, and manage errors. Use when working with crypto exchanges in TypeScript/JavaScript projects, trading bots, arbitrage systems, or portfolio management tools. Includes both REST and WebSocket examples.

1
godot

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

732