OPC UA Modeler is answering right now. Last checked 2 min ago. 70 installs a week from npm. It exposes 12 tools. Last commit 10 Sep 2026.
OPC UA companion spec types, namespace dependencies, and engineering units for AI agents
Installs per day
peak 283 · avg 28 · -82% w/w
a month agotoday
Uptime history
23 days of history
23 days agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
198 ms
Response time
average over 24h
70
Installs / week
npm and PyPI
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 September 2026. No other catalogue keeps this.
10 Sep
a tool changed the parameters it asks for
opcua_model_reverse
Nothing serious here today
Today is the operative word: we check OPC UA Modeler every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
run in your terminal
claude mcp add node-opcua-modeler-mcp-server --transport http https://api.opcua-modeler.sterfive.io/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"node-opcua-modeler-mcp-server": {
"url": "https://api.opcua-modeler.sterfive.io/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.node-opcua-modeler-mcp-server]
url = "https://api.opcua-modeler.sterfive.io/api/mcp".cursor/mcp.json
{
"mcpServers": {
"node-opcua-modeler-mcp-server": {
"url": "https://api.opcua-modeler.sterfive.io/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"node-opcua-modeler-mcp-server": {
"url": "https://api.opcua-modeler.sterfive.io/api/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
opcua
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.
opcua_model_generate
Generate OPC UA NodeSet2.xml and Symbols.CSV from a YAML model. Requires an API key (set OPCUA_MODELER_API_KEY env var). Returns base64-encoded artifacts if the model is valid, or diagnostics if validation fails. Optionally set include_docs=true to also generate markdown documentation.
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.
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.
types
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.
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.
dsl
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.
engineering
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.
namespaces
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.
resolve
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.
reusable
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.
type
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.opcua-modeler.sterfive.io/api/mcp | streamable-http | answering | 314 ms | 2 min ago |
Alternatives to OPC UA Modeler
same job, measured the same waygit-a2a
by neprel
Git module dependencies and owning-agent routing for coding agents
Claudia
by yuvalsuede
Task management for AI agents with hierarchical tasks, dependencies, sprints, and coordination.
I
LicenseGate
by computersmarts1
Open-source licence risk checks for AI coding agents and dependency trees.
memi
by sarveshsea
Memi is the read-only design engineering audit and skill layer for coding agents.
Fuse
by litenova-solutions
Local .NET compiler verification, change impact, and typed wiring for AI agents.
OpenArx
by openarx
Open scientific and engineering knowledge for AI agents: search, evidence, document publishing.
RepoPilot
by repopilot
Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.
Agent Memory MCP
by ipiton
Memory, docs, and repo context layer for engineering agents.
OPC UA Modeler — questions
Answers built from our own checks of this server.
What can OPC UA Modeler do?
It exposes 12 tools, read directly from the server on our last check. Among them: find_engineering_unit, find_reusable_block, get_dsl_reference, get_type_details, list_namespaces, list_types and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is OPC UA Modeler mostly used for?
Its tools cluster around opcua and types. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is OPC UA Modeler working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 198 ms. The bar chart above shows every period we have measured.
How do I connect OPC UA Modeler?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does OPC UA Modeler need an API key?
No. OPC UA Modeler completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is OPC UA Modeler?
It answers our handshake in 198 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use OPC UA Modeler?
The npm package node-opcua-modeler-mcp-server was installed 70 times in the last week. Week over week that is -82%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is OPC UA Modeler open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.