Skip to main content
Glama
L1ch404

io.github.L1ch404/jolink-runtime

by L1ch404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.L1ch404/jolink-runtime

No user-submitted related servers found.

    Related Servers

    • mcdev-mcp

      use-ai-for-mc
      A
      license
      A
      quality
      A
      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
      97 npm
      14
      MIT

    • Coding Tools MCP

      xyTom
      A
      license
      Not graded
      quality
      B
      maintenance
      Empower any MCP-compatible AI Agent(MCP Client) with engineering-grade capabilities to understand, modify, run, and deliver real-world code repositories.
      465 PyPI
      1,125
      Apache 2.0

    • WinCode

      linnnn89
      A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents to access Windows-first code intelligence, repository understanding, change-impact analysis, and safe workspace management through a unified high-level MCP gateway.
      11
      1
      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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly separate purpose: fast tests, application lifecycle, status/log inspection, and debugging. Cross-references such as using java_status to observe test runs are explicit and do not create ambiguity.

    Naming Consistency5/5

    All tools use the same java_ prefix and snake_case convention, and the second element is a stable noun or noun phrase. The naming pattern is predictable even though it is resource-oriented rather than verb-first.

    Tool Count5/5

    Four tools is well-scoped for a Java runtime development assistant. Each tool bundles related operations such as run/cancel/result and launch/restart/stop, so the count feels complete rather than sparse.

    Completeness4/5

    The main development loop is covered: run tests, launch/restart apps, inspect status/logs, and debug. Minor gaps exist because the tools deliberately exclude full Maven/Gradle verification and packaging, and there is no explicit test discovery operation.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources