Brave Search MCP vs Chroma MCP

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Brave Search MCP MCP Servers	Chroma MCP MCP Servers
Tagline	Give any MCP client web and local search powered by the Brave Search API.	Official MCP server that gives LLM clients direct access to the Chroma vector database.
Category	MCP Servers	MCP Servers
Pricing	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month	Free· Open source (Apache 2.0). Free to run locally or self-hosted; embedding-function API keys (OpenAI, Cohere, Jina, VoyageAI, Roboflow) billed by those providers. Chroma Cloud pricing set separately by Chroma.
Model	—	—
Editorial score	—	—
Use cases	Grounded web search inside Claude DesktopAgent fact-checking and citation lookupIDE-side research from Cursor or WindsurfLocal business and restaurant discoveryCheap RAG augmentation for small chatbotsMCP server learning and forkingPrivacy-respecting alternative to Google search in agents	Long-term memory for Claude DesktopTeam knowledge base shared across agentsRAG over local documentsSemantic code search in Cursor or ContinueVector store for custom MCP agentsPersonal notes and journal recallMetadata-filtered document retrievalChroma Cloud access from LLM clients
Pros	Two focused tools (web + local search) that are easy to reason about and stable to prompt against Small, single-file TypeScript implementation that's trivial to read, fork, or self-host Ships as both an npm package and a Docker image, with VS Code one-click install Backed by Brave's independent index, so results don't depend on Google/Bing rate limits or ToS Free tier covers 2,000 queries/month, enough for personal agents and prototyping MIT-licensed reference implementation from the MCP project itself Local-search fallback to web means agents rarely get an empty result set	Official server from the Chroma team, tracks the database's features closely Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary Twelve well-scoped MCP tools cover the full collection and document lifecycle Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence Zero-config install via uvx - drops into Claude Desktop or Cursor in a couple of JSON lines Apache 2.0 licensed and readable Python source; easy to fork or extend Query tools expose HNSW tuning and metadata/full-text filters, not just naive semantic search
Cons	Repository is archived (read-only since May 29, 2025) and no longer receives fixes or new features Superseded by Brave's own official server, which adds image/video/news/summarizer tools and HTTP transport Free tier is capped at 1 query per second, which throttles multi-step agents Local search is US-centric and quality varies sharply outside North America No streaming HTTP transport in this version, stdio only, which complicates remote/multi-tenant deployments Brave's index, while good, is smaller than Google's and can miss long-tail queries	You still have to run and back up the Chroma store yourself unless you pay for Chroma Cloud Command-line API key arguments are convenient but leak into process lists; env/.env path is safer but extra setup No built-in access control or multi-tenant isolation - anything the MCP client sees, it can delete Embedding-function persistence only works for collections created on Chroma v1.0.0+; older stores need migration Python-only server; teams on pure Node stacks add a runtime dependency MCP tool surface is CRUD-shaped - no higher-level RAG primitives like chunking, re-ranking, or hybrid fusion
Website	github.com	github.com

Pick Brave Search MCP if

✅ Two focused tools (web + local search) that are easy to reason about and stable to prompt against
✅ Small, single-file TypeScript implementation that's trivial to read, fork, or self-host
✅ Ships as both an npm package and a Docker image, with VS Code one-click install
✅ Backed by Brave's independent index, so results don't depend on Google/Bing rate limits or ToS

Pick Chroma MCP if

✅ Official server from the Chroma team, tracks the database's features closely
✅ Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary
✅ Twelve well-scoped MCP tools cover the full collection and document lifecycle
✅ Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence

Compare a different pair →