javalens-mcp
Related Servers
Alternatives to javalens-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA high-performance MCP server for intelligent documentation search, proactive bug detection, and semantic analysis of codebases.2515 npmMIT
- AlicenseAqualityCmaintenanceA high-performance MCP server that bridges AI agents with Java codebases, providing professional-grade Java language intelligence via Eclipse JDT.LS.153 npm3GPL 3.0
- AlicenseBqualityAmaintenanceAn MCP server that validates generated code against project structure and installed dependencies, catching undefined symbols, wrong API calls, dead code, and type mismatches in real time. It provides tools for project indexing, symbol/API checking, sandboxed execution, file scanning, and code analysis.1MIT
- AlicenseAqualityDmaintenanceMCP server for comprehensive code analysis, navigation, and quality assessment across 25+ programming languages.988MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server for local git repositories that provides tools for code search, git history analysis, complexity metrics, test discovery, and dependency management.MIT
- AlicenseBqualityBmaintenanceA Codex MCP server that provides low-token Java semantic navigation using source indexing and optionally JDT Language Server for enhanced symbol, references, and diagnostics.71Apache 2.0
TDQS
Scored across 75 tools
Many tools overlap in purpose: composite analyzers (analyze_file, analyze_type, analyze_method) duplicate granular tools, and multiple position-based info tools (get_symbol_info, get_hover_info, get_type_at_position, get_javadoc) retrieve similar data. Descriptions clarify intended use, but the large set of near-neighbors creates meaningful misselection risk.
Consistent snake_case with a verb_noun pattern for the vast majority (find_references, get_type_hierarchy, extract_method, apply_quick_fix). A few outliers like health_check, pull_up, and push_down lack a clear verb_noun form, but remain readable and stylistically consistent.
75 tools is far beyond the typical 3-15 range and exceeds the 50+ threshold for extreme mismatch. The breadth of Java analysis features justifies many tools, but the set is excessively large and will severely burden tool selection.
Covers navigation, search, refactoring, diagnostics, metrics, dependency analysis, framework detection (Spring, JPA, JAX-RS), tests, and impact analysis. Only minor gaps like extract class or safe delete exist; the core Java code intelligence lifecycle is fully represented.