Chroma MCP vs Kagi MCP Server

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

	Chroma MCP MCP Servers	Kagi MCP Server MCP Servers
Tagline	Official MCP server that gives LLM clients direct access to the Chroma vector database.	Official Kagi Search MCP server: search and extract the web from any MCP-compatible agent.
Category	MCP Servers	MCP Servers
Pricing	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.	Paid· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month
Model	—	—
Editorial score	—	—
Use cases	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	agent web search groundingClaude Code documentation lookupdeep-research pipelinesURL to Markdown extraction for RAGnews and video search from an LLMKagi lens-scoped queries in agentscitation gathering for research assistantscoding agent error-message lookups
Pros	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	Official, first-party MCP server maintained by Kagi (not a community wrapper) Two clean tools that cover the 90% agent case: search and full-page Markdown extraction Both hosted (mcp.kagi.com) and local (uvx/Docker) deployment modes Documented setup recipes for Claude Desktop, Claude Code, Codex CLI, Kiro, OpenCode, Smithery MIT-licensed Python code, easy to fork or audit Rides Kagi's ad-free, spam-de-boosted index rather than generic SERP APIs Supports Kagi lenses and filters so agents can scope searches to news, docs, etc.
Cons	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	Requires a paid Kagi API key with pay-per-use billing; not usable free FastGPT and Universal Summarizer tools are currently absent (rewrite in progress) Python + uv toolchain assumption raises the bar vs. a single-binary MCP server Small surface area: no built-in caching, batching, or spend controls beyond Kagi's invoice cap Hosted endpoint means your queries and Bearer token traverse Kagi infra, not a concern for everyone but worth noting for regulated workloads
Website	github.com	github.com

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

Pick Kagi MCP Server if

✅ Official, first-party MCP server maintained by Kagi (not a community wrapper)
✅ Two clean tools that cover the 90% agent case: search and full-page Markdown extraction
✅ Both hosted (mcp.kagi.com) and local (uvx/Docker) deployment modes
✅ Documented setup recipes for Claude Desktop, Claude Code, Codex CLI, Kiro, OpenCode, Smithery

Compare a different pair →