Allows analysis of Java classes from Apache Commons and other Apache Maven dependencies, providing decompiled source code and documentation.
Enables analysis of Java classes from Quarkus and Quarkiverse projects, supporting decompilation and source retrieval from Maven repositories.
Provides analysis of Java classes from Spring Framework libraries, with support for sources.jar, CFR decompiler, and javap fallback.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@java-class-analyzer-mcp analyze the class org.springframework.beans.factory.BeanFactory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
通用Java类分析MCP工具，让AI自动分析Maven项目依赖中的类。
✅ 完整JavaDoc支持 - 自动从sources.jar读取原始源码
✅ 智能降级 - sources.jar → CFR → javap 四级降级
✅ 通用可配置 - 支持任何Maven项目和groupId
✅ 灵活配置 - 通过mcp.json或config.json配置
✅ 自动化 - CFR反编译器可选自动下载
Related MCP server: Maven Package README MCP Server
cd .cursor/java-class-analyzer
npm install有三种配置方式，按优先级：
{
"mcpServers": {
"java-class-analyzer": {
"command": "node",
"args": [".cursor/java-class-analyzer/index.js"],
"env": {
"MAVEN_REPO": "${HOME}/.m2/repository",
"GROUP_ID_MAPPINGS": "[{\"groupId\":\"com/mycompany\",\"prefix\":\"com.mycompany.\"}]"
}
}
}
}复制 config.example.json 为 config.json 并修改：
cp config.example.json config.json默认支持常见的groupId：
com.ql.*
com.qinglusaas.*
io.quarkus.*
io.quarkiverse.*
org.apache.commons.*
org.springframework.*
重启Cursor
在对话中: "请初始化Java类索引"
开始使用: "请分析 [类名]"
环境变量: MAVEN_REPO
默认值: ${HOME}/.m2/repository
{
"env": {
"MAVEN_REPO": "/custom/path/to/.m2/repository"
}
}环境变量: GROUP_ID_MAPPINGS (JSON数组)
说明: 用于识别JAR文件名中的groupId前缀
{
"env": {
"GROUP_ID_MAPPINGS": "[{\"groupId\":\"com/mycompany\",\"prefix\":\"com.mycompany.\"}]"
}
}或在config.json中：
{
"groupIdMappings": [
{ "groupId": "com/mycompany", "prefix": "com.mycompany." },
{ "groupId": "org/example", "prefix": "org.example." }
]
}环境变量: CFR_JAR_PATH
默认值: cfr.jar（当前目录）
{
"env": {
"CFR_JAR_PATH": "/path/to/cfr.jar"
}
}在config.json中配置：
{
"decompile": {
"enableSourcesJar": true,
"enableCFR": true,
"enableJavap": true
}
}工具会按以下优先级获取源码：
优先级 | 方式 | JavaDoc | 质量 | 说明 |
1 | sources.jar | ✅ | 最高 | Maven源码包 |
2 | CFR | ❌ | 高 | 反编译器 |
3 | javap | ❌ | 中 | JDK工具 |
4 | 基本信息 | ❌ | 低 | 兜底 |
java_class_indexer - 构建类索引
java_class_analyzer - 分析反编译类
java_class_search - 搜索类
✅ 所有Maven项目
✅ 任何groupId
✅ 公司内部二方包
✅ 开源第三方库
分析和反编译指定的Java类。根据类的全限定名查找对应的JAR包并进行反编译,返回源代码。
Inputs: className (required).
构建Java项目依赖类的索引。扫描Maven依赖的所有JAR包,建立类名到JAR包的映射关系。
Inputs: no named parameters.
搜索Java类。根据关键词模糊搜索已索引的类名,返回匹配的类列表。
Inputs: keyword (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Ship better Java with your coding agent.
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
