hebros-mcp
Related Servers
Alternatives to hebros-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceProvides efficient code navigation and graph-based analysis for AI agents, enabling symbol resolution, callers, implementations, and type schemas with minimal token usage.-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to perform structural code operations on TypeScript/TSX projects—finding symbols and references and renaming them semantically while preserving source.27 npmMIT
- AlicenseNot gradedqualityBmaintenanceA navigable symbol map of your codebase for coding agents, enabling efficient code navigation and reading only relevant symbols instead of entire files.MIT
- AlicenseNot gradedqualityAmaintenanceExposes a codebase's symbol graph and symbol-aware editing tools to AI agents, enabling targeted symbol lookup, impact analysis, and atomic multi-file edits with reduced context tokens.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceContext compiler for AI coding agents that indexes TypeScript codebases to extract and serve only the relevant symbols and files for a task, reducing token usage and search overhead.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides structured semantic context for JavaScript/TypeScript codebases, enabling coding agents to navigate, review, and change code with explicit uncertainty.18 npm1MIT
TDQS
Scored across 5 tools
Each tool has a distinct primary intent, but get_map, get_references, and get_deps all overlap on reporting 'who imports it', and get_map and find_symbol both expose symbol locations. The descriptions mitigate the ambiguity, but an agent could still misselect for import/usage questions.
Most tools follow a verb_noun snake_case pattern (get_map, get_references, get_deps). find_symbol and reindex are minor deviations but still use the same action-first, lowercase-with-underscore style, so the naming remains predictable.
Five tools is a well-scoped count for a code-intelligence server. Each tool covers a distinct mode of interaction: refresh, definition lookup, structure overview, reference search, and dependency analysis.
The toolset covers the core workflow of navigating a codebase: locating definitions, browsing structure, finding usages, and analyzing dependency impact. The main gap is the lack of fuzzy or pattern-based symbol search, since find_symbol appears to require exact names.