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.
Install Chroma MCP Server (if not already done)
Prepare Your Storage and Logging Directories
- Decide on the folder(s) for persistent data storage and logging.
- For example, create folders called
my_data and my_logs in your project directory if you want to use the paths ./my_data and ./my_logs.
Collect the Required ENV Values
- You will need the following values for configuration:
CHROMA_CLIENT_TYPE: Usually set to persistent for persistent storage.CHROMA_DATA_DIR: Absolute or relative path to your persistent data directory, e.g., /path/to/your/data.CHROMA_LOG_DIR: Absolute or relative path to your logging directory, e.g., /path/to/your/logs.LOG_LEVEL, MCP_LOG_LEVEL, MCP_SERVER_LOG_LEVEL (Optional): Set logging levels; commonly INFO is used.
Fill in Values in the FastMCP Connection Interface using "Install Now"
- Open the FastMCP integration interface.
- Click on the "Install Now" button for the Chroma MCP Server.
- In the connection form, fill in the following fields with the corresponding values:
CHROMA_CLIENT_TYPE → persistentCHROMA_DATA_DIR → (your desired data directory path, e.g., /path/to/your/data)CHROMA_LOG_DIR → (your desired log directory path, e.g., /path/to/your/logs)- Optional: Set
LOG_LEVEL, MCP_LOG_LEVEL, MCP_SERVER_LOG_LEVEL to INFO or your preferred log level.
Save the Configuration
- Complete the setup by saving your changes in the FastMCP interface.
Note: No external API keys, tokens, or credentials are required for Chroma MCP Server—only local directory paths and log settings.
