ChromaDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_chromadbB | Query the ChromaDB ExchangeResearch collection for relevant documents. Use this to find information related to exchange research, trading, or financial data. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as querying a specific collection in ChromaDB for exchange research data.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'query_chromadb' follows a clear verb_noun pattern, though no pattern can be established across multiple tools.
A single tool is insufficient for a database server's scope, which typically requires operations like create, update, delete, or list collections. This feels thin and limits functionality to basic queries only.
The tool surface is severely incomplete for a ChromaDB server. It only supports querying a specific collection, missing essential operations such as creating collections, inserting documents, updating data, or managing collections, which are critical for database interactions.