Skip to main content
Glama
idachev

MCP Java Decompiler Server

by idachev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Java Decompiler Server

No user-submitted related servers found.

    Related Servers

    • Java JAR Decompiler & Reverse

      sapyyy
      F
      license
      A
      quality
      A
      maintenance
      Enables decompilation and reverse engineering of Java JAR files through multi-engine decompilation, candidate evaluation, Maven project structuring, AST-based deobfuscation, and bytecode comparison.
      4
      9
      1
      -

    • Java Class Analyzer MCP Server

      handsomestWei
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      3
      21 npm
      43
      Apache 2.0

    • java-class-analyzer-mcp

      Aorls
      A
      license
      A
      quality
      D
      maintenance
      Enables AI to analyze Java classes from Maven project dependencies, with support for decompilation strategies and configurable groupId mappings.
      3
      14 npm
      5
      MIT

    • Java JAR MCP Server

      biggerball
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct input source: file path, package name, and JAR file. The purposes are clearly separated with no overlap, so an agent can accurately select the correct tool.

    Naming Consistency5/5

    All tool names follow the exact same pattern: 'decompile-from-' followed by the source type. This consistent verb_noun structure makes the API predictable and easy to learn.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to the core decompilation task. Each tool earns its place by covering a different input method, and the count is well within the ideal range.

    Completeness4/5

    The server covers the primary decompilation sources (file, package, JAR), which handles most use cases. However, there is no batch operation or way to list classes within a package/JAR, requiring manual workarounds or repeated calls for larger tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources