Skip to main content
Glama
SachieWang

java-jdtls-mcp-server

by SachieWang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to java-jdtls-mcp-server

No user-submitted related servers found.

    Related Servers

    • codeweave-mcp

      semihkayan
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.
      153 npm
      4
      Apache 2.0

    • mcdev-mcp

      use-ai-for-mc
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that empowers AI coding agents to work effectively with Minecraft mod development, providing static analysis of decompiled source code and runtime interaction with a running Minecraft instance.
      31
      55 npm
      14
      MIT

    • JDTLS-MCP

      sunix
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Eclipse JDT Language Server to AI agents via MCP. Embedded OSGi architecture runs jdtls in the same JVM — no subprocess, no network hop. Tools: hover, definition, references, completion, diagnostics, document & workspace symbols.
      5
      Eclipse Public 2.0

    • jvmsrc

      Sintexer
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives coding agents IDE-like access to JVM classpaths by querying the actual build tool, providing precise source code, signatures, and structure without cache-walking or version guesswork.
      61 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.5/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'find_references' and 'java_get_references' are very similar and could cause confusion. 'java_get_diagnostics' and 'java_get_workspace_diagnostics' also overlap somewhat. Overall, descriptions help differentiate, but ambiguity exists.

    Naming Consistency4/5

    The majority of tools follow the 'java_verb_noun' pattern (12 out of 15). However, 'configure_jdt_ls', 'find_references', and 'read_java_content' deviate from this convention, breaking perfect consistency.

    Tool Count5/5

    15 tools is well-scoped for a Java language server integration. The set covers key operations like startup, diagnostics, symbol queries, references, and project loading without being overly large or trivial.

    Completeness4/5

    The tool set covers common LSP operations (hover, definition, references, diagnostics, symbols) and includes workspace-level diagnostics. Missing features like code completion, formatting, or rename, but the set is sufficient for typical agent interactions with JDT LS.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources