Servers Playground How we check Add a server Log in

OPC UA Modeler

Working · 3.3 s

io.github.node-opcua/node-opcua-modeler-mcp-serverv1.6.1

OPC UA companion spec types, namespace dependencies, and engineering units for AI agents

Developer Tools

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://api.opcua-modeler.sterfive.io/api/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

find_engineering_unit Read-only

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.

querystring, required

Description or common name of the unit (e.g. "revolutions per minute", "celsius", "pressure bar")

OPC UA Modeler MCP server | mcptry

Tools (12)

find_engineering_unit

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.

read-only

Argument	Type	Description
query*	string	Description or common name of the unit (e.g. "revolutions per minute", "celsius", "pressure bar")

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Description or common name of the unit (e.g. \"revolutions per minute\", \"celsius\", \"pressure bar\")"
    }
  },
  "additionalProperties": false
}

find_reusable_block

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.

read-only

Argument	Type	Description
query*	string	Member name or capability keyword (e.g. "SerialNumber", "health", "calibration")

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Member name or capability keyword (e.g. \"SerialNumber\", \"health\", \"calibration\")"
    }
  },
  "additionalProperties": false
}

get_dsl_reference

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.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

get_type_details

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.

read-only

Argument	Type	Description
alias*	string	Companion spec alias where the type is defined (e.g. "machinery")
browseName*	string	The type browse name (e.g. "MachineryItemIdentificationType")

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "alias",
    "browseName"
  ],
  "properties": {
    "alias": {
      "type": "string",
      "description": "Companion spec alias where the type is defined (e.g. \"machinery\")"
    },
    "browseName": {
      "type": "string",
      "description": "The type browse name (e.g. \"MachineryItemIdentificationType\")"
    }
  },
  "additionalProperties": false
}

list_namespaces

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.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

list_types

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.

read-only

Argument	Type	Description
alias*	string	Companion spec alias (e.g. "machinery", "di", "robotics")

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "alias"
  ],
  "properties": {
    "alias": {
      "type": "string",
      "description": "Companion spec alias (e.g. \"machinery\", \"di\", \"robotics\")"
    }
  },
  "additionalProperties": false
}

opcua_model_create

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.

read-only

Argument	Type	Description
prompt*	string	Natural language description of the OPC UA model to generate
forceSpecs	array	Companion spec aliases to force (e.g. ["di", "ia"])

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "prompt"
  ],
  "properties": {
    "prompt": {
      "type": "string",
      "description": "Natural language description of the OPC UA model to generate"
    },
    "forceSpecs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Companion spec aliases to force (e.g. [\"di\", \"ia\"])"
    }
  },
  "additionalProperties": false
}

opcua_model_generate

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.

read-only

Argument	Type	Description
mode	string	"new": first generation, no symbols yet. "update": regeneration, symbols required. "renumber": allocate new NodeIds on purpose. Omit when passing symbols.
yaml*	string	The full YAML model source to generate from
symbols_csv	string	The symbols CSV of the previous generation (the content of <name>.model.symbols.csv, or the base64 symbols_csv a previous call returned). Keeps NodeIds stable.
include_docs	boolean	Set to true to include markdown documentation (slower)

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "yaml"
  ],
  "properties": {
    "mode": {
      "enum": [
        "new",
        "update",
        "renumber"
      ],
      "type": "string",
      "description": "\"new\": first generation, no symbols yet. \"update\": regeneration, symbols required. \"renumber\": allocate new NodeIds on purpose. Omit when passing symbols."
    },
    "yaml": {
      "type": "string",
      "description": "The full YAML model source to generate from"
    },
    "symbols_csv": {
      "type": "string",
      "description": "The symbols CSV of the previous generation (the content of <name>.model.symbols.csv, or the base64 symbols_csv a previous call returned). Keeps NodeIds stable."
    },
    "include_docs": {
      "type": "boolean",
      "description": "Set to true to include markdown documentation (slower)"
    }
  },
  "additionalProperties": false
}

opcua_model_reverse

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.

read-only

Argument	Type	Description
xml*	string	The NodeSet2.xml content to reverse-engineer
namespace_uri	string	Target namespace URI to extract (auto-detected if omitted)
self_contained	boolean	Return one self-contained .opcua.yaml stream: the model, its NodeId symbol table and dependency declarations (default: bare YAML)

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "xml"
  ],
  "properties": {
    "xml": {
      "type": "string",
      "description": "The NodeSet2.xml content to reverse-engineer"
    },
    "namespace_uri": {
      "type": "string",
      "description": "Target namespace URI to extract (auto-detected if omitted)"
    },
    "self_contained": {
      "type": "boolean",
      "description": "Return one self-contained .opcua.yaml stream: the model, its NodeId symbol table and dependency declarations (default: bare YAML)"
    }
  },
  "additionalProperties": false
}

opcua_model_validate

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.

read-only

Argument	Type	Description
yaml*	string	The full YAML model source to validate

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "yaml"
  ],
  "properties": {
    "yaml": {
      "type": "string",
      "description": "The full YAML model source to validate"
    }
  },
  "additionalProperties": false
}

resolve_dependencies

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.

read-only

Argument	Type	Description
aliases*	array	Companion spec aliases to resolve (e.g. ["machineTool", "robotics"])

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "aliases"
  ],
  "properties": {
    "aliases": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Companion spec aliases to resolve (e.g. [\"machineTool\", \"robotics\"])"
    }
  },
  "additionalProperties": false
}

search_types

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.

read-only

Argument	Type	Description
query*	string	Search keyword (e.g. "identification", "temperature", "motion")

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search keyword (e.g. \"identification\", \"temperature\", \"motion\")"
    }
  },
  "additionalProperties": false
}