Chroma MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROMA_SSL | No | Whether to use SSL for self-hosted Chroma (true/false) | |
| CHROMA_HOST | No | Host for self-hosted Chroma instance | |
| CHROMA_PORT | No | Port for self-hosted Chroma instance | |
| CHROMA_TENANT | No | Tenant ID for Chroma Cloud | |
| CHROMA_API_KEY | No | API key for Chroma Cloud | |
| CHROMA_DATABASE | No | Database name for Chroma Cloud | |
| CHROMA_DATA_DIR | No | Data directory for persistent client | |
| CHROMA_CLIENT_TYPE | No | Type of Chroma client: ephemeral, persistent, http, or cloud | |
| CHROMA_DOTENV_PATH | No | Path to .env file | |
| CHROMA_CUSTOM_AUTH_CREDENTIALS | No | Custom auth credentials for self-hosted Chroma |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chroma_list_collectionsA | List all collection names in the Chroma database with pagination support. |
| chroma_create_collectionC | Create a new Chroma collection with configurable HNSW parameters. |
| chroma_peek_collectionB | Peek at documents in a Chroma collection. |
| chroma_get_collection_infoC | Get information about a Chroma collection. |
| chroma_get_collection_countC | Get the number of documents in a Chroma collection. |
| chroma_modify_collectionB | Modify a Chroma collection's name or metadata. |
| chroma_fork_collectionC | Fork a Chroma collection. |
| chroma_delete_collectionB | Delete a Chroma collection. |
| chroma_add_documentsC | Add documents to a Chroma collection. |
| chroma_query_documentsA | Query documents from a Chroma collection with advanced filtering. |
| chroma_get_documentsA | Get documents from a Chroma collection with optional filtering. |
| chroma_update_documentsA | Update documents in a Chroma collection. |
| chroma_delete_documentsA | Delete documents from a Chroma collection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct operation: collection management (list, create, peek, info, count, modify, fork, delete) and document operations (add, query, get, update, delete). No two tools have overlapping purposes.
All tools follow a consistent 'chroma_verb_noun' pattern (e.g., chroma_list_collections, chroma_create_collection). The naming is uniform and predictable.
13 tools is an appropriate number for a vector database MCP server, covering all essential CRUD operations for collections and documents without being excessive or insufficient.
The tool set provides comprehensive coverage: create, read (get, list, peek, count), update (modify collection, update documents), and delete for both collections and documents. Advanced querying with filtering is supported, and there are no obvious gaps for typical usage.