LayerMap
Related Servers
Alternatives to LayerMap
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a precise, local call/type/data graph so they can find who calls what, what breaks when code changes, and which tests to run, with every answer traced to file:line.125 PyPI1Functional Source , Version 1.1, ALv2 Future
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and terminal users to query codebases for callers, impact, tests, dependencies, and refactor previews using static AST analysis, with every match accounted for and uncertain relationships clearly marked.1,067 npm2MIT
- AlicenseBqualityBmaintenanceEnables coding agents to query a static AST-based call graph for TypeScript/JavaScript repositories, including who-calls, impact analysis, entry-to-dependency traces, hotspots, symbol search, and git-blame archaeology, with every result backed by source evidence chains.91MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.19 PyPI4MIT
- AlicenseNot gradedqualityCmaintenanceGives coding agents a read-only, token-budgeted code graph spanning every repository in a project: symbols, calls, imports, and cross-repo HTTP, config, and package links, each backed by file:line evidence on both sides. This lets agents trace how symbols connect across repos and determine the impact of an API change by distinguishing links that are actually used from ones that are only declared.534 npmApache 2.0
- AlicenseAqualityBmaintenanceLocal AST call graph and code map for AI coding agents. Finds where to start for a task (ranked files), who calls a method and how far a change ripples, method bodies by line range, string and constant search, and framework views (Laravel routes, validation, events; Vue props and emits). Supports PHP, JS, TS, Vue, Rust, Swift, Python and Go. Runs locally, no API key or account needed.1114MIT
TDQS
Scored across 4 tools
Each tool has a recognizably different role: search finds declarations, explore reads structure/callers, find_references enumerates usages, and check_changes reports diff impact. The explore vs. find_references boundary is the only fuzzy spot, but descriptions explicitly contrast them (cached callers vs. broader, more expensive full reference computation). A competent agent should select correctly most of the time.
All four tools share a project_ prefix followed by a verb_noun pattern: project_search_map, project_explore_map, project_find_references, project_check_changes. The action word differs meaningfully per tool, so names are both consistent and self-describing.
Four tools map cleanly onto the four distinct verbs of a static code-map workflow (search, explore, enumerate references, assess a diff). Nothing feels redundant or missing at the count level; each tool clearly earns its place.
The surface covers the full discovery-to-verification lifecycle: locate a declaration, trace callers/callees to entry points, enumerate all usages, and evaluate change impact against a commit. Minor gaps remain, notably no full-text search (explicitly deferred to reading the source directly) and no standalone route/entry-point or module-dependency listing outside the diff-oriented tool, but these are workable given the descriptions.