Chroma MCP (Multi-Modal Controller for Persistance) Server acts as a vector database integration layer for LLM applications. It provides a set of tools that allow LLM agents to interact with ChromaDB, handling complex operations like document creation, updates, and deletions. The current version is 0.2.6, and it sees somewhat frequent updates, often tied to new releases of the underlying `chromadb` library.
pip install chroma-mcpNo compatibility data collected yet for this library.
The Chroma MCP Server is a FastAPI application. This quickstart demonstrates how to run it locally using `uvicorn`, configuring the ChromaDB backend via environment variables to use a temporary directory for data storage. The server will start and be accessible at `http://127.0.0.1:8000` (or configured host/port).
Refer to the `chroma-mcp` release notes and `chromadb` documentation for specific version compatibility and migration guides. Test agent interactions thoroughly after updating `chroma-mcp`.
Ensure all necessary environment variables are set correctly before starting the server. Use `.env` files with tools like `python-dotenv` or explicitly set them in your deployment environment.
Update `chroma-mcp` to v0.2.2 or later. Review agent logic that processes query/get results to ensure compatibility with the corrected `include` behavior.
Carefully follow the documentation for SSL/TLS setup. For testing, consider starting without SSL first to ensure basic connectivity, then introduce SSL gradually. Ensure correct certificate paths and permissions.
Install uvicorn: `pip install uvicorn`
Set either `CHROMA_DB_PATH` to a local directory or `CHROMA_DB_URI` to a remote ChromaDB instance. Example: `export CHROMA_DB_PATH='./chroma_data'` or `os.environ['CHROMA_DB_PATH'] = './chroma_data'`.
Ensure `chroma-mcp` is correctly installed (`pip install chroma-mcp`). Verify that your Python environment is active and that the command `uvicorn chroma_mcp.app:app` is run from a location where `chroma_mcp` is importable.