Developer Tools

sterfive.io

Provides tools for exploring and resolving OPC UA companion specification namespaces and types, aiding developers working with OPC UA information models.

1 endpoint12 known toolsFirst detected July 25, 2026Last detected July 29, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: opcua-modeler
Version: 1.6.1

Capabilities

tools.listChanged

Known tools 12

resolve_dependencies

Given one or more companion spec namespace aliases, returns the full resolved dependency list that MUST go in the YAML `namespaces:` section.

Inferred read-only

list_namespaces

List all well-known OPC UA companion spec namespace aliases with their full names, URIs, and dependencies.

Inferred read-only

list_types

List ALL ObjectTypes, VariableTypes, and InterfaceTypes defined in a specific companion spec namespace.

Inferred read-only

get_type_details

Get detailed information about a specific type: its components, properties, methods, interfaces, and optional members.

Inferred read-only

search_types

Search for types across ALL companion specs by keyword.

Inferred read-only

find_reusable_block

Find reusable Interfaces / AddIns by capability — pass a member name or keyword (e.

Inferred read-only

find_engineering_unit

Find the official UNECE Rec.

Inferred read-only

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.

Inferred read-only

opcua_model_validate

Validate an OPC UA YAML model for correctness.

Inferred read-only

opcua_model_generate

Generate OPC UA NodeSet2.

Inferred read-only

opcua_model_reverse

Reverse-engineer a NodeSet2.

Inferred read-only

opcua_model_create

Generate an OPC UA YAML model from a natural language description using AI.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.opcua-modeler]
url = "https://api.opcua-modeler.sterfive.io/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "opcua-modeler": {
      "type": "http",
      "url": "https://api.opcua-modeler.sterfive.io/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: opcua-modeler
Remote MCP URL: https://api.opcua-modeler.sterfive.io/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "opcua-modeler": {
      "url": "https://api.opcua-modeler.sterfive.io/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "opcua-modeler": {
      "type": "http",
      "url": "https://api.opcua-modeler.sterfive.io/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "opcua-modeler",
  "transport": "streamable-http",
  "url": "https://api.opcua-modeler.sterfive.io/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.