What it does & operational scope
Chroma Vector Memory MCP Server links language models to Chroma vector collections over standard input and output. Designed for zero-daemon local execution via uvx, it enables agents to create persistent collections, insert text documents with automated default embeddings, and perform semantic similarity queries against local disk stores.
Chroma Vector Memory MCP Server is an open-source Model Context Protocol server developed by Chroma under Apache-2.0 that provides zero-daemon embedded vector storage and semantic retrieval over stdio.
Your AI coding agent requires live access to Chroma Vector Memory tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "chroma": { "command": "uvx", "args": ["chroma-mcp"] } }}Exposed tool endpoints & primitives
Discovered MCP Tools
4 Tools Readyquery_collection🟢 Read-Only (Safe)Query Chroma vector store with embeddings and return nearest neighbor documents
create_collection🟡 State MutationInitialize a new named collection with metadata and distance metric
upsert_documents🟡 State MutationInsert or update text chunks and vector embeddings into a target collection
delete_collection🔴 Destructive / ConfirmPermanently drop an existing collection and associated vector indices
Scopes, secret storage, and sandbox boundaries
Run Chroma Vector Memory MCP Server with scoped environment tokens. Never run under root and restrict network ingress.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Chroma Vector Memory MCP Server from the last 7 days"query_collection({ query: "Chroma Vector Memory MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Chroma Vector Memory MCP Server"query_collection_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Zero external daemon required; runs entirely as an embedded local process.
+ Includes default embedding functions to get started without external API keys.
+ Lightweight local file storage ideal for personal workstation experiments.
− Local embedded SQLite vector storage inflates file sizes quickly, increasing memory footprint during cold-boot collection loads.
− Concurrent multi-process writes to the embedded database trigger write lock timeouts unless managed via a client-server daemon.
Side-by-side rival comparisons
Compare Chroma Vector Memory MCP Server vs Qdrant Semantic Memory MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 1,4 "method": "tools/call",5 "params": {6 "name": "inspect",7 "arguments": {}8 }9}
