Managed OPC UA Server

A TypeScript MCP server that exposes OPC UA read access through server-side authorization and Operator-defined Semantic Controls for safe agent interaction.

See docs/plan.md, docs/operator-guide.md, and CONTEXT.md.

Security posture

• No arbitrary OPC UA writes.
• Reads rely on OPC UA Server credentials and roles for authorization.
• Optional Read Entry Points guide agent discovery.
• Writes use Operator-defined Semantic Controls only.
• High-risk controls are rejected in v1.
• Control attempts are audited.
• Secrets must be provided through environment variables, not literal YAML values.

Development

npm install
npm run typecheck
npm test

Local use

Read the Operator safety guide before enabling controls.

Copy examples/local.config.yaml to a non-committed local config and edit it for your OPC UA Server. Validate locally, run online diagnostics, and generate commissioning review artifacts before serving:

cp examples/local.config.yaml opcua-mcp.local.yaml
npm run dev -- validate --config opcua-mcp.local.yaml
npm run dev -- doctor --config opcua-mcp.local.yaml --format json
npm run dev -- setup --config opcua-mcp.local.yaml \
  --out opcua-mcp.draft.local.yaml \
  --report commissioning-report.local.md
npm run dev -- validate --config opcua-mcp.draft.local.yaml
npm run dev -- doctor --config opcua-mcp.draft.local.yaml --format json
npm run dev -- serve --config opcua-mcp.draft.local.yaml

setup performs bounded metadata-only discovery. Generated Semantic Control candidates remain comments and cannot execute until an Operator reviews and manually promotes them into the Control Catalog. See the commissioning workflow for report interpretation, exit codes, redaction, and safety boundaries.

Write examples and integration write tests must only target simulator, test, or otherwise safe Nodes approved by an Operator.