by djm81
Chroma Working Memory offers a persistent, searchable 'second brain' for developers with ChromaDB, codebase indexing, an
Creates a persistent, searchable 'second brain' for development by automatically indexing your codebase, logging AI conversations, and maintaining context across sessions using ChromaDB.
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.
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.
NOASSERTION
Chroma Working Memory is released under the NOASSERTION license.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired Chroma Working Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Chroma Working Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Chroma Working Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Chroma Working Memory is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Chroma Working Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Chroma Working Memory has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Chroma Working Memory for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
According to our notes, Chroma Working Memory benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Chroma Working Memory is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Chroma Working Memory against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 72
A Model Context Protocol (MCP) server integration for Chroma, the open-source embedding database.
Chroma MCP Server creates a persistent, searchable "working memory" for AI-assisted development:
Key features:
See the Getting Started with your Second Brain guide for more details.
# Basic installation
pip install chroma-mcp-server
# Full installation with all embedding models
pip install "chroma-mcp-server[full]"
# 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
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"
}
}
}
}
chat_history_v1, codebase_v1) are automatically created on server startup if they don't exist.Comprehensive documentation is available in the docs directory:
Chroma MCP Server is licensed under the MIT License with Commons Clause. This means you can:
✅ Allowed:
❌ Not Allowed:
See the LICENSE.md file for the complete license text.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.