OPC UA Modeler
Server Details
OPC UA companion spec types, namespace dependencies, and engineering units for AI agents
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- node-opcua/node-opcua-modeler-mcp-server
- GitHub Stars
- 2
- Server Listing
- node-opcua-modeler-mcp-server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 12 tools
Most tools target clearly distinct purposes (validate vs generate vs reverse are unambiguous, and get_type_details vs list_types vs search_types differ by scope). The only mild overlap is search_types vs list_types and search_types vs find_reusable_block, but the descriptions clarify 'all namespaces by keyword' vs 'single namespace' vs 'reusable Interface/AddIn by capability'.
Nearly all tools follow a verb_noun convention (find_*, get_*, list_*, search_*, resolve_*). The four model-lifecycle tools use an opcua_model_ prefix, which is a readable grouping but a minor deviation from the rest of the set.
Twelve tools is well within the ideal band and each one maps to a distinct phase of the workflow (discover namespaces/types, look up units/blocks, reference DSL, resolve deps, create/validate/generate/reverse). No tool looks redundant or padded.
The surface covers the full describe→create→validate→generate→reverse lifecycle plus the discovery helpers needed to author YAML correctly. Minor gaps exist (no way to list or diff previously produced models, and editing is delegated to the agent via the DSL reference), but core workflows have no dead ends.
Available Tools
12 toolsfind_engineering_unitFind an engineering unitARead-onlyIdempotentInspect
Find the official UNECE Rec. 20 engineering unit symbol for a given description. ALWAYS call this before using any engineering unit — NEVER guess unit symbols.
Inputs: query (required).
find_reusable_blockFind a reusable interface or AddInARead-onlyIdempotentInspect
Find reusable Interfaces / AddIns by capability — pass a member name or keyword (e.g. "SerialNumber", "DeviceHealth", "Location") and get the standard blocks that already expose it. PREFER applying/composing an existing block over redefining its members inline. Interfaces are applied with interfaces:; addins (types with a DefaultInstanceBrowseName) are composed with addIns:. A single property → use the Interface; a whole named sub-object → use the AddIn.
Inputs: query (required).
get_dsl_referenceGet the DSL grammar referenceARead-onlyIdempotentInspect
Get the grammar reference for the OPC UA modeler YAML DSL: file header, top-level sections, name-prefix conventions, minimal examples, and common mistakes. Call this FIRST before writing any YAML model by hand. Works without an API key.
Inputs: no named parameters.
get_type_detailsGet type detailsARead-onlyIdempotentInspect
Get detailed information about a specific type: its components, properties, methods, interfaces, and optional members. Use this to understand a type's structure before creating instances or subtypes. specRef, on the type and on a member, is the link to the section of the specification that defines it: cite it.
Inputs: alias (required), browseName (required).
list_namespacesList companion specificationsARead-onlyIdempotentInspect
List all well-known OPC UA companion spec namespace aliases with their full names, URIs, and dependencies. Use this to discover what namespaces are available.
Inputs: no named parameters.
list_typesList types in a namespaceARead-onlyIdempotentInspect
List ALL ObjectTypes, VariableTypes, and InterfaceTypes defined in a specific companion spec namespace. ALWAYS call this before using any type from a namespace — NEVER guess type names.
Inputs: alias (required).
opcua_model_createCreate a model from a descriptionARead-onlyInspect
Generate an OPC UA YAML model from a natural language description using AI. Requires an API key (set OPCUA_MODELER_API_KEY env var). The AI will auto-detect relevant companion specs, generate a validated model with documentation, and auto-correct validation errors.
Inputs: prompt (required), forceSpecs.
opcua_model_generateGenerate NodeSet2 XMLARead-onlyIdempotentInspect
Generate OPC UA NodeSet2.xml and the symbols CSV from a YAML model. Requires an API key (set OPCUA_MODELER_API_KEY env var). NodeIds stay stable only if each regeneration passes back the symbols of the previous one: pass symbols_csv, or mode "new" for a first generation, or mode "renumber" to change ids on purpose. A call with none of these is refused with SYMBOLS_DECISION_REQUIRED. Returns base64-encoded artifacts if the model is valid. The result lists symbol counts (reused/new/dropped), hints and next steps.
Inputs: yaml (required), mode, symbols_csv, include_docs. Returns: mode, files, hints, valid, +5 more
opcua_model_reverseReverse-engineer NodeSet2 XMLARead-onlyIdempotentInspect
Reverse-engineer a NodeSet2.xml file back into the YAML DSL format. Requires an API key (set OPCUA_MODELER_API_KEY env var). Optionally specify the target namespace URI to extract.
Inputs: xml (required), namespace_uri, self_contained.
opcua_model_validateValidate an OPC UA modelARead-onlyIdempotentInspect
Validate an OPC UA YAML model for correctness. Returns diagnostics with severity (error/warning/info), codes, messages, and line numbers. Works without an API key (limited to 50 calls/day). ALWAYS validate before generating.
Inputs: yaml (required).
resolve_dependenciesResolve namespace dependenciesARead-onlyIdempotentInspect
Given one or more companion spec namespace aliases, returns the full resolved dependency list that MUST go in the YAML namespaces: section. Always call this before generating the namespaces block.
Inputs: aliases (required).
search_typesSearch types across specsARead-onlyIdempotentInspect
Search for types across ALL companion specs by keyword. Use this when you don't know which namespace defines a type. Returns matching types with their namespace alias.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
MCP server for the Fail Modes taxonomy — a knowledge base of AI system failure modes
AI-security knowledge as MCP: standards-mapped tools (OWASP, NIST, MITRE) for AI agents.
Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.
Cross-OEM industrial machine intelligence: identity, normalization, automation, attestation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects AI agents to OPC UA-enabled industrial systems for real-time monitoring and control of operational data. It enables users to read, write, and browse industrial device nodes through natural language interactions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, browse, read, search, and safely write OPC UA industrial device data within controlled edge networks, with guarded two-phase writes and evidence-based root-cause diagnostics.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to read, write, browse, search, and subscribe to live data on OPC-UA industrial automation servers, with caching, discovery index, and support for stdio or HTTP transports.5MIT
- AlicenseAqualityBmaintenanceConnect AI assistants to industrial OPC UA systems. Browse nodes, read live data and history, and monitor subscriptions, events and alarms. Runs locally over stdio in read-only mode by default.1133MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.