Skip to main content
Glama
soubhagya2001

Ignition-JavaDoc-MCP

by soubhagya2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Ignition-JavaDoc-MCP

No user-submitted related servers found.

    Related Servers

    • source-rag-mcp

      hanhy06
      F
      license
      B
      quality
      B
      maintenance
      MCP server for searching, browsing, and analyzing decompiled Minecraft source code locally. Supports symbol lookup, text search, reference lookup, and lightweight RAG.
      11
      -

    • Ignition Doc MCP

      nurnaufal321
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that provides AI assistants with real-time access to Inductive Automation Ignition documentation, enabling accurate answers on Ignition-specific topics by searching live docs and fetching full pages.
      3
      MIT

    • devdocs-mcp

      madhan-g-p
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode. Not via Scraping! But using the supported downloading option from devdocs.
      45 npm
      13
      MIT

    • easy-code-reader

      FangYuan33
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for intelligently reading Java source code, supporting extraction from Maven dependencies and local projects with dual decompilers.
      2
      88 PyPI
      154
      Apache 2.0

    • dejared-mcp

      hqkh4nh
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for exploring, analyzing, and decompiling Java JAR files.
      104 npm
      6
      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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the JavaDoc API: searching, retrieving class docs, package docs, or member docs. There is no overlap in their purposes, so an agent can easily choose the correct tool for a given task.

    Naming Consistency5/5

    All tool names follow a consistent pattern of a verb (search/get) followed by 'ignition' and then the target type (api, class_docs, package_docs, member_docs). This uniform structure makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With only four tools, the server is tightly scoped to its purpose of exploring the Ignition API documentation. Each tool covers a fundamental operation (search, package, class, member) without unnecessary bloat, making the set feel complete and manageable.

    Completeness5/5

    The tool set covers the full lifecycle of browsing JavaDoc: searching for any API element, then drilling down into packages, classes, and members. There are no obvious missing operations for a documentation server, as search can find anything and retrieval covers all levels of detail.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources