java-class-analyzer-mcp
Related Servers
Alternatives to java-class-analyzer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceDecompiles Maven dependencies into readable Java source directly inside your AI agent.1031 npm1Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI tools to analyze Java dependencies by scanning Maven projects, decompiling JAR files, and extracting detailed class information including methods, fields, and inheritance relationships. Solves the problem of AI hallucinations when generating code that calls external dependencies by providing accurate class structures through decompilation.312 npm43Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up Java class definitions and list dependencies from Maven projects by analyzing local JAR files via the Model Context Protocol.4 npm4MIT
- AlicenseAqualityFmaintenanceDecompiles Java .class files, packages, and JARs into readable source code, enabling AI assistants to inspect Java bytecode.330 npm20ISC
- AlicenseNot gradedqualityAmaintenanceIndexes local Maven and Gradle caches to enable AI agents to search for Java classes, method signatures, and source code, including from internal or obscure libraries.45 npm22ISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to fetch comprehensive information about Maven packages from Maven Central, including README content, package metadata, dependencies, and search functionality with GitHub integration.8 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: one builds the index, one searches it, and one decompiles a specific class. There is no functional overlap or ambiguity between them.
All tools share the java_class_ prefix and follow the same noun-style naming pattern: indexer, analyzer, search. This creates a predictable and recognizable set.
Three tools is well-scoped for a Java class analysis server: index, search, and analyze. Each tool is necessary and the count feels complete without being bloated.
The tool surface covers the full workflow: building an index from Maven dependencies, searching indexed classes by keyword, and analyzing/decompiling a selected class. There are no obvious dead ends or missing operations for the stated purpose.