Java Class Analyzer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CFR_PATH | No | CFR反编译工具的路径（可选，程序会自动查找） | |
| NODE_ENV | No | 运行环境标识。production: 生产环境，减少日志输出，启用性能优化；development: 开发环境，输出详细调试信息；test: 测试环境 | production |
| JAVA_HOME | No | Java安装路径。如果设置，程序会使用 ${JAVA_HOME}/bin/java 执行Java命令（用于CFR反编译）；如果未设置，程序会使用PATH中的 java 命令 | |
| MAVEN_REPO | No | Maven本地仓库路径。如果设置，程序会使用指定的仓库路径扫描JAR包；如果未设置，程序会使用默认的 ~/.m2/repository 路径 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_dependenciesC | 扫描Maven项目的所有依赖，建立类名到JAR包的映射索引 |
| decompile_classC | 反编译指定的Java类文件，返回Java源码 |
| analyze_classC | 分析Java类的结构、方法、字段等信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: analyze_class examines class structure, decompile_class converts bytecode to source code, and scan_dependencies maps dependencies in a project. An agent can easily distinguish between analyzing structure, decompiling, and dependency scanning.
All tool names follow a consistent verb_noun pattern in snake_case (analyze_class, decompile_class, scan_dependencies), with clear, descriptive verbs that indicate the action performed on the target noun. There are no deviations or mixed conventions.
With only 3 tools, the set feels thin for a Java class analyzer server, potentially lacking operations like listing classes, updating analyses, or handling specific Java features. While the tools cover core functions, more tools might be expected for comprehensive analysis.
The tools cover key areas (analysis, decompilation, dependency scanning) but have notable gaps, such as no create, update, or delete operations for classes or dependencies, and no tools for handling multiple classes or projects. This could limit agents in complex workflows.