repomap-mcp
Related Servers
Alternatives to repomap-mcp
No user-submitted related servers found.
Related Servers
- 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.39 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.46 npm4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that indexes your codebase using tree-sitter AST parsing and gives AI tools instant access to structural intelligence like dependency graphs, call trees, and dead code detection from a local SQLite database.MIT
- -licenseNot gradedqualityNot gradedmaintenanceAST-aware code exploration MCP server for AI agents, optimized for token efficiency.-
- AlicenseAqualityCmaintenanceAn AST-based MCP server that provides token-efficient codebase skeletons to LLM agents, reducing context token usage by 80-95% by exposing structural information instead of full source files.54 npm3MIT
- AlicenseNot gradedqualityCmaintenanceToken-efficient code intelligence MCP server that indexes codebases with tree-sitter AST parsing and provides 150 tools for AI agents, using 61-95% fewer tokens than traditional grep/Read workflows.163 npm4Business Source 1.1
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: repo_map provides a high-level structural overview via PageRank, while search_identifiers finds specific code symbols. There is no overlap in functionality, so an agent can easily choose the right one.
Both tool names use a consistent verb_noun pattern (repo_map, search_identifiers) with clear verbs describing the action and nouns describing the target. The naming is predictable and descriptive.
With only two tools, the server feels thin but not inadequate given its focused purpose on codebase mapping and identifier search. The scope is narrow enough that two tools may suffice, though additional tools like file listing or definition retrieval could be expected.
The server covers two core needs (structural overview and symbol search), but is missing common operations like viewing file contents, getting code definitions at a point, or listing references for a symbol. An agent may hit dead ends if it needs more detailed code navigation beyond identifiers.