What client types are available?
Ephemeral (in‑memory), Persistent (local storage), HTTP (remote), and Cloud (managed). The default is ephemeral.
MCP.chroma
@volteditor
Basic information
About MCP.chroma
a mcp server for interacting with ChromaDB
MCP.chroma config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryMCP.chroma tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is mcp.chroma?
A Rust-based MCP server that provides a model‑context–protocol interface to ChromaDB, a vector database for embeddings. It enables collection and document management through a set of tools, supporting multiple client types (HTTP, Cloud, Persistent, Ephemeral).
How to use mcp.chroma?
Clone the repository, build with Cargo (cargo build --release), create a .chroma_env file or use command‑line options (e.g., --client-type, --host, --port), then run the binary. Configure the client type, host, port, SSL, tenant, database, and API key either via environment variables or CLI flags.
Key features of mcp.chroma
- Collection management: create, list, modify, delete
- Document operations: add, query, get, update, delete
- Multiple client types: ephemeral, persistent, HTTP, cloud
- Thought processing for session management
Use cases of mcp.chroma
- Create and manage vector document collections for semantic search
- Query collections to find documents similar to a given text
- Integrate vector database operations into AI assistants like Claude or Cursor
- Store and retrieve embeddings for RAG (retrieval‑augmented generation) pipelines
Frequently asked questions
How do I configure the server?
Use a `.chroma_env` file with environment variables such as `CHROMA_CLIENT_TYPE`, `CHROMA_HOST`, `CHROMA_PORT`, `CHROMA_API_KEY`, etc., or pass the corresponding CLI flags (e.g., `--client-type`, `--host`, `--port`).
Can I use mcp.chroma with Claude or Cursor?
Yes. The README includes example configuration blocks for both Claude (via `mcpServers` in a JSON config) and Cursor (via `.vscode/mcp.json`), specifying the command, args, and environment variables.
What transport does the server use?
The README does not explicitly mention the transport protocol beyond stating it follows the MCP protocol. The examples show an HTTP‑based client type, implying support for HTTP transport.
Are there any runtime dependencies?
The server is built in Rust and requires Cargo to compile. At runtime it depends on a running ChromaDB instance when using the HTTP or Cloud client types; the ephemeral and persistent clients do not require an external database.
More Databases MCP servers
Elasticsearch MCP Server
elastic685
Expired Domains MCP | Karma.Domains
karma-domainsConnect Karma.Domains to ChatGPT, Claude, Cursor, VS Code, or another MCP client — and find a domain in plain language. The same auctions, expired, backorder, and buy-now data you use in the app, plus saved filters, note
Redis
modelcontextprotocolModel Context Protocol Servers
88.2K
Sail MCP Server for Spark SQL
lakehqDrop-in Apache Spark replacement written in Rust, unifying batch processing, stream processing, and compute-intensive AI workloads.
3.1K
Postgres Mcp
crystaldbaPostgres MCP Pro provides configurable read/write access and performance analysis for you and your AI agents.
3.0K
Comments