Repo Lens MCP Server
Related Servers
Alternatives to Repo Lens MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceCode-search engine that parses TypeScript and JavaScript with a real AST, stores the symbol graph in SQLite, and serves AI assistants exact matching declarations (functions, classes, types) via BM25 fused with declaration-exact ranking — saving tokens by returning only the relevant code instead of whole files.50 npm3MIT
- FlicenseNot gradedqualityDmaintenanceA local server that provides powerful code analysis and search capabilities for software projects, helping AI assistants and development tools understand codebases for tasks like code generation and refactoring.4-
- AlicenseAqualityBmaintenanceEnables unified code search and analysis over a monorepo, combining exact, semantic, and call graph queries with indexing, incremental updates, and impact analysis.12MIT
- AlicenseNot gradedqualityCmaintenanceProvides IDE-like code navigation and search for local repositories, enabling AI assistants to perform symbol search, trigram indexing, and semantic navigation.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceProvides knowledge extraction and cross-repo analysis tools for multi-repository organizations. It enables users to query type definitions, service dependencies, and infrastructure configurations across an entire organization's codebase.MIT
- AlicenseNot gradedqualityCmaintenanceA graph-powered code intelligence engine that indexes codebases into a structural knowledge graph to provide AI agents with deep context on function calls, types, and execution flows. It offers local, zero-dependency tools for hybrid search, impact analysis, and dead code detection across Python, JavaScript, and TypeScript projects.956 PyPI814MIT
TDQS
Scored across 5 tools
Each tool targets a distinct code construct: repositories, functions, classes, types/interfaces, and API routes. The descriptions clearly separate concerns, so an agent is unlikely to confuse one tool for another.
All tool names follow the consistent `repolens_<verb>_<noun>` pattern using snake_case. The verb choices are uniform (`list` for one, `find` for the rest) and the object nouns clearly indicate the target.
Five tools is well-scoped for a focused cross-repository code search server. Each tool covers a meaningful piece of the search surface without redundant or unnecessary entries.
The set covers the primary search needs for functions, classes, types, and API routes across repositories. Notable gaps remain such as full-text search, enums, variables, or imports, but these are workable minor omissions rather than critical dead ends.