attocode-code-intel
Related Servers
Alternatives to attocode-code-intel
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to perform local code search, indexing, and analysis across Java, JavaScript/TypeScript, .NET/C#, and Python projects through the MCP protocol.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceRepository intelligence MCP server for structural code analysis, dependency graphs, call graphs, symbol search, impact analysis, and repository-aware AI.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to register projects and analyze source code through Tree-sitter WASM parsing, exposing tools for AST and symbol extraction, custom queries, reference finding, complexity and similarity analysis, dependency discovery, and text search. It also ships a web studio with a Monaco editor, AST explorer, Git view, and read-only SQLite console for interactive exploration.MIT
- AlicenseNot gradedqualityDmaintenanceMulti-language code intelligence MCP server providing structured code analysis including symbol search, references, hierarchies, and change impact. Supports 25 languages with persistent indexing and LSP integration.27 npmMIT
- FlicenseNot gradedqualityDmaintenanceWorkspace-aware MCP server that provides AI clients with structural code understanding via AST parsing, hybrid retrieval, and git history, enabling accurate code search, definition lookup, and blame analysis.-
- AlicenseNot gradedqualityBmaintenanceProvides a code graph querying and visualization MCP server, enabling users to search, trace, and describe code components, overlay diffs, and explore architecture through natural language.MIT
TDQS
Scored across 17 tools
Most tools have a distinct angle: symbol-name search (search_symbols), regex content search (fast_search) and meaning search (semantic_search) are clearly separated, as are call_graph and cross_references. There is real overlap among the neighborhood/context tools (dependencies, impact_analysis, relevant_context, explore_codebase) and between the bundle tool inspect_symbol and the specialized reference/test tools, but descriptions give enough cues to choose correctly in most cases.
All names are snake_case with no style mixing, which makes the set readable. However the conventions are blended: some are verb_object (search_symbols, inspect_symbol, review_change, suggest_tests, notify_file_changed) while others are bare noun phrases (symbols, dependencies, capabilities, project_summary, call_graph), a minor inconsistency rather than a usability problem.
At 17 tools the server is slightly above the comfortable range, but each tool maps to a real code-intelligence capability (search, symbols, graphs, context, review, tests). A few could be folded together—bootstrap overlaps project_summary/explore_codebase, and inspect_symbol duplicates parts of cross_references and suggest_tests—so the surface is a touch heavier than necessary.
Coverage is broad for a code-intelligence domain: three search modes, symbol definition/reference lookup, call graph, dependency and impact analysis, contextual exploration, review and test suggestion, plus index notification and a capabilities tool. Minor gaps remain—no explicit file-content read or manual re-index/status tool, and no symbol-level write operations—but these are largely outside the stated read-oriented purpose.