machine discovery

Give the harness a deterministic industrial tool layer

The engineer chooses the harness and permissions. 2ot provides local execution, structured evidence and machine-readable discovery underneath it.

NEW HARNESS?

Connect 2ot over MCP in about a minute

Verify the local schema, paste one stdio server entry into the harness, reload, and enumerate the installed tools.

60-second MCP setup →
harness
agent / CI / script
discover
list + schema
2ot
route + analyze
evidence
compiler / vendor
LOCAL OPERATIONAL SURFACE
discover
2ot --list --json
describe
2ot --mcp-dump-schema
connect
2ot mcp
diagnose
2ot check --fast
BOUNDARY

The website is discovery, not the control plane

Public WebMCP, Markdown and discovery resources are read-only. Project-changing and device-facing operations stay local inside the engineer-selected environment.

MACHINE-READABLE ENTRY POINTS

Start with a resource the client can parse directly

Installed surface wins

The local executable—not the marketing site—is authoritative for commands and tool schemas.

Vendor routing stays explicit

Use an explicit target for consequential work; inspect the current workspace binding before planning a vendor operation.

Licensed knowledge stays local

Siemens-derived API corpus data remains on the licensed workstation.