Ignition-JavaDoc-MCP
Provides fast search and detailed Markdown documentation retrieval for the Ignition Inductive Automation Java API, including classes, packages, and members.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ignition-JavaDoc-MCP Search for the Ignition Dataset class"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ignition Javadocs MCP
An MCP (Model Context Protocol) server for extremely fast and accurate searching and documentation retrieval of the Ignition Inductive Automation Java API.
Features
Lightning Fast Search: Indexes the Javadoc JSON-like artifacts (e.g.
type-search-index.js) to provide sub-second search responses without downloading full HTML.Dynamic HTML Parsing: When detailed documentation is requested, it dynamically fetches the Javadoc HTML and meticulously converts it into clean, AI-readable Markdown using
cheerio.Multi-Version Support: Can query any version of Ignition (default
8.1.39) that publishes Javadoc to the inductive automation SDK domain.
Related MCP server: devdocs-mcp
Tools Provided
search_ignition_api: Search forclass,package, ormemberby keyword.get_ignition_class_docs: Retrieve the full Markdown documentation for a specific class (e.g., package:com.inductiveautomation.ignition.common, class:Dataset).get_ignition_package_docs: Retrieve the full Markdown documentation for a specific package.get_ignition_member_docs: Retrieve documentation for a single member (method/field/constructor). Use theufield from search results asmemberAnchor.
Caching
The search index is cached to disk in .cache/ (one file per Ignition version) so restarts don't re-download it. Cache entries expire after 24 hours. Override the cache location with the IGNITION_JAVADOC_CACHE_DIR environment variable.
Getting Started
Prerequisites
Node.js >= 18
Installation & Build
# Install dependencies
npm install
# Compile the TypeScript to JavaScript
npm run buildUsage with MCP Clients
To use this with an MCP client (such as Claude Desktop), configure your MCP settings file to run this server.
Example configuration:
{
"mcpServers": {
"ignition-javadoc": {
"command": "node",
"args": [
"/path/to/Ignition-Module-Development-Docs/dist/index.js"
]
}
}
}This MCP operates exclusively on stdio.
Available Tools
4 toolsget_ignition_class_docsC
Gets the documentation for a specific class.
Inputs: className (required), packagePath (required), version.
get_ignition_member_docsA
Gets the full documentation for a specific member (method/field/constructor) of a class. Use the 'u' field from search_ignition_api results as memberAnchor.
Inputs: className (required), packagePath (required), memberAnchor (required), version.
get_ignition_package_docsB
Gets the documentation for a specific package.
Inputs: packagePath (required), version.
search_ignition_apiB
Searches the Ignition Java API documentation for classes, packages, or members.
Inputs: query (required), type, version.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
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.
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.
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.
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
Related MCP Connectors
MCP server for developer documentation, generated by doc2mcp.
MCP server for dev documentation, generated by doc2mcp.
MCP server for doc2mcp documentation, generated by doc2mcp.
MCP server for developers documentation, generated by doc2mcp.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides comprehensive access to MCP documentation through structured guides, full-text search, and interactive development workflows for building servers and clients.343 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn 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.63 npm14MIT
- AlicenseAqualityBmaintenanceAn MCP server for intelligently reading Java source code, supporting extraction from Maven dependencies and local projects with dual decompilers.2102 PyPI154Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server for exploring, analyzing, and decompiling Java JAR files.570 npm9MIT