What it contains
Vector-backed semantic code search that indexes repositories and retrieves relevant code via MCP for Claude Code, Codex, Gemini, Cursor and others.
Typical uses
Reduce repeated directory exploration/context cost on large codebases with semantic retrieval.
Why people choose it
Inference: selected when repos are too large for naïve file loading and vector/embedding infrastructure is acceptable.
Last meaningful updateUnknown
Production readinessproduction
Classification
Subject domains
semantic code searchcodebase context
Task categories
semantic code searchcodebase context
Project phases
implementationoperations
Secondary types
libraryIDE extension
Select when
- Need semantic code search over a large repository
Do not select when
- Small repository
- Cannot provision vector DB/embeddings
Implementation complexitymedium
Routing heuristic 75.0%
Security boundary clarity
3/5 First-party routing documentation
5/5 Strengths
None documented.
Poor-fit scenarios
- Small repository
- Cannot provision vector DB/embeddings
Limitations
None documented.
README.md
Index/search code.
indexsemantic retrieval
README.md
Expose search to MCP clients.
MCP
README.md
IDE semantic search.
IDE
FrameworksNone documented
Operating systemsNone documented
Installation methodsNone documented
InterfacesMCP, library, VS Code
Required credentialsembedding key, Milvus/Zilliz credentials
External servicesMilvus/Zilliz, embedding provider
Major dependenciesNone documented
Compatibility notes
None documented.
One-sentence semantic summary
Vector-backed semantic code search that indexes repositories and retrieves relevant code via MCP for Claude Code, Codex, Gemini, Cursor and others.
Capability keywords
code indexingsemantic searchMCPVS Code extension
User intent phrases
- Need semantic code search over a large repository
Negative match phrases
- Small repository
- Cannot provision vector DB/embeddings
Differentiators
None documented.
Security considerations
None documented.
Privacy considerations
- Indexed code follows configured embedding/vector data boundaries.
Uncertainty
Unresolved items
None documented.
Inference notes
None documented.
Repository usage guidance
installation summaryUnknown
basic usage summaryReduce repeated directory exploration/context cost on large codebases with semantic retrieval.
documented entry pointsNone documented
key configuration filesNone documented
important directoriesNone documented
documentation pathsREADME.md
example pathsNone documented
Relationships
complementary
high
Repomix is a snapshot packer; Claude Context is live semantic retrieval.
Recommended combinations
Large-repository context efficiency high
Each repository covers a distinct layer; avoid combining tools that duplicate lifecycle ownership.
Order of operations
- Use Repomix for handoff/snapshot
- Index active repo with Claude Context
- Install RTK for command-heavy sessions
Spec-first large-repo delivery high
Each repository covers a distinct layer; avoid combining tools that duplicate lifecycle ownership.
Order of operations
- Create constitution/spec/plan/tasks
- Use semantic search during planning/implementation
- Use RTK for terminal verification
- Implement against approved tasks
Routing rules
rule_028: Need semantic code search over a large repository P972
Rationale
Vector-backed semantic code search that indexes repositories and retrieves relevant code via MCP for Claude Code, Codex, Gemini, Cursor and others.
Required conditions
None documented.
Preferred
zilliztech/claude-context
Fallback
None