Ignition Doc MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ignition_docsA | Search the Ignition User Manual (always the latest version). Use this for questions about Ignition configuration, tags, scripting, modules, gateways, designers, and general product usage. |
| search_ignition_sdkA | Search the Ignition SDK Programmer's Guide. Use this for questions about building Ignition modules: GatewayModuleHook, DesignerModuleHook, ClientModuleHook, AbstractGatewayModuleHook, and the Ignition module API. |
| get_pageA | Fetch the text content of an Ignition documentation page by URL. Use URLs returned by search_ignition_docs or search_ignition_sdk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: two search tools target different documentation sets (user manual vs SDK guide), and get_page fetches content by URL. No overlap or ambiguity exists.
The search tools follow a consistent 'search_ignition_' prefix pattern, and get_page is a simple, clear verb_noun pair. All names are snake_case and readable.
With 3 tools, the set is minimal but well-scoped for a documentation-focused server. It covers the primary needs without unnecessary bloat, though it could benefit from one or two more tools.
The tool surface covers core documentation workflows: searching two main documentation sources and fetching specific pages. Minor gaps like version selection or browsing are absent, but for typical usage it is sufficient.