Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI coding agent developers and platform teams who need the entire codebase as semantic search context for Claude Code / Cursor / Codex CLI / Gemini CLI / Qwen Code / any MCP-aware coding agent, and for engineering orgs that have hit the 'load the whole repo into the context window' wall with a 12k-line cost-per-prompt. The durable differentiator is the merkle-tree indexer + hybrid
Who should use it
Who should skip it
Skip zilliztech/claude-context unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
zilliztech/claude-context is tracked by RepoRadar as an MCP server in the MCP Servers section. First seen 2026-07-04; the source record was last checked on 2026-07-04. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, zilliztech/claude-context is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The zilliztech/claude-context record combines a 8.7/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Default install path uses Zilliz Cloud (free tier covers most small-to-medium codebases; orgs with strict data-residency requirements need self-hosted Milvus) + OpenAI embeddings (orgs that can't ship OpenAI keys can use Ollama local or VoyageAI or Gemini as the embedding provider); The merkle-tree incremental indexer is O(changed files) not O(repo size) but the initial `index_codebase` run on a large monorepo can take 10-30 minutes and produce a large vector index; budget the first-run cost and disk space accordingly.