Chroma MCP Server
by zwczwczwc
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 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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
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/zwczwczwc/chroma-mcp-ollama'
If you have feedback or need assistance with the MCP directory API, please join our Discord server