Chroma MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROMA_SSL | No | Whether to use SSL (for HTTP client/self-hosted) | |
| CHROMA_HOST | No | Your host (for HTTP client/self-hosted) | |
| CHROMA_PORT | No | Your port (for HTTP client/self-hosted) | |
| CHROMA_TENANT | No | Your tenant ID (for cloud client) | |
| CHROMA_API_KEY | No | Your API key (for cloud client) | |
| CHROMA_DATABASE | No | Your database name (for cloud client) | |
| CHROMA_DATA_DIR | No | Full path to your data directory (for persistent client) | |
| CHROMA_CLIENT_TYPE | No | The type of Chroma client to use (http, cloud, persistent, ephemeral) | |
| CHROMA_DOTENV_PATH | No | Path to .env file (defaults to .chroma_env) | |
| CHROMA_JINA_API_KEY | No | Jina API key for Jina embedding function | |
| CHROMA_COHERE_API_KEY | No | Cohere API key for Cohere embedding function | |
| CHROMA_OPENAI_API_KEY | No | OpenAI API key for OpenAI embedding function | |
| CHROMA_ROBOFLOW_API_KEY | No | Roboflow API key for Roboflow embedding function | |
| CHROMA_VOYAGEAI_API_KEY | No | VoyageAI API key for VoyageAI embedding function | |
| CHROMA_CUSTOM_AUTH_CREDENTIALS | No | Your custom auth credentials (for HTTP client/self-hosted) |
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
Server capabilities have not been inspected yet.
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_collectionB | Create a new Chroma collection with configurable HNSW parameters. |
| chroma_peek_collectionB | Peek at documents in a Chroma collection. |
| chroma_get_collection_infoB | Get information about a Chroma collection. |
| chroma_get_collection_countB | Get the number of documents in a Chroma collection. |
| chroma_modify_collectionC | 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chroma-core/chroma-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server