reflens
Related Servers
Alternatives to reflens
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that indexes codebases into a local graph and provides on-demand context retrieval for AI coding agents, reducing token usage by tracking session history and delivering only relevant code subgraphs.5 npmMIT
- AlicenseAqualityBmaintenanceMCP server that helps AI coding agents understand a repository by providing lightweight tree/map, code search, and token-budgeted context packing tools without dumping the entire monorepo into the prompt.32 npm105MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.47 npm4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that enables coding agents to retrieve project context, semantically search indexed documentation, and read specific documents from registered repositories.MIT
- AlicenseAqualityCmaintenanceA local-first MCP server that enables AI tools to safely inspect and search code repositories, providing indexing, deterministic BM25 search, code outlining, and context bundles without code modification.91MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server for codebase context that gives AI coding agents structural understanding through symbol graph, semantic search, blast radius, and convention detection tools.38MIT
TDQS
Scored across 8 tools
Each tool has a uniquely defined purpose: listing repos, module navigation, architecture digest, search, exact source retrieval, dependency exploration, history, and verification. Descriptions are detailed and clearly distinguish their roles, leaving no ambiguity.
All tools follow a consistent 'reflens_<action>' or 'reflens_<noun>' pattern in snake_case. The naming is predictable and uniform across the entire set.
Eight tools is well-scoped for a reference intelligence server. Each tool earns its place, covering all expected operations (list, browse, search, read, analyze, history, verify) without unnecessary bloat.
The tool surface covers the full lifecycle of interacting with reference code: discovery (list, modules, map), retrieval (search, read), analysis (neighbors, history), and verification (verify). There are no obvious gaps for its stated purpose.