ChromaDB Remote MCP Server
Give coding agents remote vector search and collection operations against ChromaDB over MCP without running a local Chroma stack on your laptop.
Overview
chromadb-remote-mcp is a MCP server for the Build phase that connects agents to a remote ChromaDB vector store via streamable HTTP.
What is this MCP server?
- ChromaDB Remote MCP Server title in registry; version 1.0.2
- Hosted streamable-http remote at meloncafe.github.io/chromadb-remote-mcp/mcp
- Optional Docker OCI package devsaurus/chromadb-remote-mcp with port 8080:8080 mapping
- CHROMADB_MCP_URL and optional MCP_AUTH_TOKEN environment variables for self-hosted deployments
- Registry version 1.0.2
- Docker runtime maps host port 8080 to container 8080
- OCI identifier devsaurus/chromadb-remote-mcp:latest
What problem does it solve?
Local Chroma setups break across machines and make it hard for agents to query the same vector collections consistently.
Who is it for?
Indie developers prototyping agent retrieval against Chroma without baking database wiring into every prompt.
Skip if: Builders who need a managed proprietary vector SaaS with no self-hosted URL or Docker operations.
What do I get? / Deliverables
Your agent can use MCP tools against a shared remote Chroma endpoint while you build RAG or memory features.
- MCP-accessible ChromaDB operations against a configured remote URL
- Repeatable agent retrieval workflow without per-machine Chroma installs
Recommended MCP Servers
Journey fit
Vector database MCP servers belong in Build because they are infrastructure hooks while you implement RAG and agent memory. ChromaDB over streamable HTTP is a third-party integration your agent calls during backend and agent-tooling work.
How it compares
Remote database MCP bridge, not an embedding model or chunking skill inside the repo.
Common Questions / FAQ
Who is chromadb-remote-mcp for?
Developers building agent or RAG features who want ChromaDB reachable through standard MCP clients over HTTP.
When should I use chromadb-remote-mcp?
Use it when your workflow needs collection queries or vector operations from an agent during integration and backend build work.
How do I add chromadb-remote-mcp to my agent?
Add the streamable-http remote URL from the registry or set CHROMADB_MCP_URL to your deployment; optionally configure MCP_AUTH_TOKEN and Docker port 8080 if you run the OCI package locally.