Elasticsearch MCP Server vs Chroma MCP
A side-by-side look at the Elasticsearch MCP Server and Chroma MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Elasticsearch MCP Server for databases work as a local process; choose Chroma MCP for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Elasticsearch MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
list_indices, get_index, create_index.
Choose Chroma MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CHROMA_CLIENT_TYPE, CHROMA_DATA_DIR, CHROMA_TENANT, CHROMA_DATABASE, CHROMA_API_KEY, CHROMA_HOST, CHROMA_PORT, CHROMA_CUSTOM_AUTH_CREDENTIALS. - You want tools like
chroma_list_collections, chroma_create_collection, chroma_peek_collection.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 65/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | CHROMA_CLIENT_TYPECHROMA_DATA_DIRCHROMA_TENANTCHROMA_DATABASECHROMA_API_KEYCHROMA_HOSTCHROMA_PORTCHROMA_CUSTOM_AUTH_CREDENTIALS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 313 | 600 |
| Directory activity | 3 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 20 | 13 |
| Full listing | View Elasticsearch MCP Server | View Chroma MCP |
Tools & capabilities
Elasticsearch MCP Server tools 20
list_indicesList all indices.get_indexReturns information (mappings, settings, aliases) about one or more indices.create_indexCreate a new index.delete_indexDelete an index.search_documentsSearch for documents.index_documentCreates or updates a document in the index.get_documentGet a document by ID.delete_documentDelete a document by ID.delete_by_queryDeletes documents matching the provided query.get_cluster_healthReturns basic information about the health of the cluster.get_cluster_statsReturns high-level overview of cluster statistics.list_aliasesList all aliases.- +8 more on the listing page
Chroma MCP tools 13
chroma_list_collectionsList all collection names in the Chroma database with pagination support. Args: limit: Optional maximum number of collections to return offset: Optional number of collections to skip before returning results Returns: List of collection names or ["__NO_COLLECTIONS_FOUND__"] if database is emptychroma_create_collectionCreate a new Chroma collection with configurable HNSW parameters. Args: collection_name: Name of the collection to create embedding_function_name: Name of the embedding function to use. Options: 'default', 'cohere', 'openai', 'jina', 'voyageai', 'ollama', 'roboflow' metadata: Optional metadata dict to add to the collectionchroma_peek_collectionPeek at documents in a Chroma collection. Args: collection_name: Name of the collection to peek into limit: Number of documents to peek atchroma_get_collection_infoGet information about a Chroma collection. Args: collection_name: Name of the collection to get info aboutchroma_get_collection_countGet the number of documents in a Chroma collection. Args: collection_name: Name of the collection to countchroma_modify_collectionModify a Chroma collection's name or metadata. Args: collection_name: Name of the collection to modify new_name: Optional new name for the collection new_metadata: Optional new metadata for the collectionchroma_fork_collectionFork a Chroma collection. Args: collection_name: Name of the collection to fork new_collection_name: Name of the new collection to create metadata: Optional metadata dict to add to the new collectionchroma_delete_collectionDelete a Chroma collection. Args: collection_name: Name of the collection to deletechroma_add_documentsAdd documents to a Chroma collection. Args: collection_name: Name of the collection to add documents to documents: List of text documents to add ids: List of IDs for the documents (required) metadatas: Optional list of metadata dictionaries for each documentchroma_query_documentsQuery documents from a Chroma collection with advanced filtering. Args: collection_name: Name of the collection to query query_texts: List of query texts to search for n_results: Number of results to return per query where: Optional metadata filters using Chroma's query operators Examples: - Simple equality: {"metadata_field": "value"} - Comparison: {"metadata_field": {"$gt": 5}} - Logical AND: {"$and": [{"field1": {"$eq": "value1"}}, {"field2": {"$gt": 5}}]} - Logical OR: {"$or": [{"field1": {"$eq": "value1"}}, {"field1": {"$eq": "value2"}}]} where_document: Optional document content filters Examples: - Contains: {"$contains": "value"} - Not contains: {"$not_contains": "value"} - Regex: {"$regex": "[a-z]+"} - Not regex: {"$not_regex": "[a-z]+"} - Logical AND: {"$and": [{"$contains": "value1"}, {"$not_regex": "[a-z]+"}]} - Logical OR: {"$or": [{"$regex": "[a-z]+"}, {"$not_contains": "value2"}]} include: List of what to include in response. By default, this will include documents, metadatas, and distances.chroma_get_documentsGet documents from a Chroma collection with optional filtering. Args: collection_name: Name of the collection to get documents from ids: Optional list of document IDs to retrieve where: Optional metadata filters using Chroma's query operators Examples: - Simple equality: {"metadata_field": "value"} - Comparison: {"metadata_field": {"$gt": 5}} - Logical AND: {"$and": [{"field1": {"$eq": "value1"}}, {"field2": {"$gt": 5}}]} - Logical OR: {"$or": [{"field1": {"$eq": "value1"}}, {"field1": {"$eq": "value2"}}]} where_document: Optional document content filters Examples: - Contains: {"$contains": "value"} - Not contains: {"$not_contains": "value"} - Regex: {"$regex": "[a-z]+"} - Not regex: {"$not_regex": "[a-z]+"} - Logical AND: {"$and": [{"$contains": "value1"}, {"$not_regex": "[a-z]+"}]} - Logical OR: {"$or": [{"$regex": "[a-z]+"}, {"$not_contains": "value2"}]} include: List of what to include in response. By default, this will include documents, and metadatas. limit: Optional maximum number of documents to return offset: Optional number of documents to skip before returning results Returns: Dictionary containing the matching documents, their IDs, and requested includeschroma_update_documentsUpdate documents in a Chroma collection. Args: collection_name: Name of the collection to update documents in ids: List of document IDs to update (required) embeddings: Optional list of new embeddings for the documents. Must match length of ids if provided. metadatas: Optional list of new metadata dictionaries for the documents. Must match length of ids if provided. documents: Optional list of new text documents. Must match length of ids if provided. Returns: A confirmation message indicating the number of documents updated. Raises: ValueError: If 'ids' is empty or if none of 'embeddings', 'metadatas', or 'documents' are provided, or if the length of provided update lists does not match the length of 'ids'. Exception: If the collection does not exist or if the update operation fails.- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Elasticsearch MCP Server
{
"mcpServers": {
"cr7258-elasticsearch-mcp-server": {
"command": "uvx",
"args": [
"elasticsearch-mcp-server"
]
}
}
}
Chroma MCP
{
"mcpServers": {
"chroma-core-chroma-mcp": {
"command": "uvx",
"args": [
"chroma-mcp"
],
"env": {
"CHROMA_CLIENT_TYPE": "YOUR_CHROMA_CLIENT_TYPE_HERE",
"CHROMA_DATA_DIR": "YOUR_CHROMA_DATA_DIR_HERE",
"CHROMA_TENANT": "YOUR_CHROMA_TENANT_HERE",
"CHROMA_DATABASE": "YOUR_CHROMA_DATABASE_HERE",
"CHROMA_API_KEY": "YOUR_CHROMA_API_KEY_HERE",
"CHROMA_HOST": "YOUR_CHROMA_HOST_HERE",
"CHROMA_PORT": "YOUR_CHROMA_PORT_HERE",
"CHROMA_CUSTOM_AUTH_CREDENTIALS": "YOUR_CHROMA_CUSTOM_AUTH_CREDENTIALS_HERE"
}
}
}
}
Frequently asked questions
Elasticsearch MCP Server is categorized under Databases and uses a local stdio subprocess. Chroma MCP belongs to Databases and uses a local stdio subprocess. Pick Elasticsearch MCP Server for databases work and Chroma MCP for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Elasticsearch MCP Server is listed as free. Auth: api key required. Chroma MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cr7258-elasticsearch-mcp-server and chroma-core-chroma-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Elasticsearch MCP Server has a quality signal of 65/100 (Great) with 3 views, 0 installs and 313 GitHub stars. Chroma MCP has 61/100 (Good) with 4 views, 0 installs and 600 GitHub stars.