Reviewed operations, with channel-specific CLI and MCP access
MCP exposes a reviewed subset of the routed contract. CLI-only commands, transaction tools and standalone semantic context have distinct boundaries.
Connect a local harness in three steps
2ot MCP uses local stdio by default. The exact settings file varies by harness, but the server process is simply 2ot mcp.
Run this once in the same environment the harness will use.
2ot --mcp-dump-schemaUse this common MCP-client shape; adapt the surrounding config keys if your harness names them differently.
Inspect the installed MCP schema and tool classification. A prompt is not an authorization policy: raw consequential operations are denied by the runtime.
{
"mcpServers": {
"2ot": {
"command": "2ot",
"args": ["mcp"]
}
}
}2ot --list --json shows installed routes and 2ot --mcp-dump-schema shows the normalized agent-callable contract for that machine.2ot …Stable router
Scripts, CI and internal tools call workspace, compiler and vendor routes directly.
2ot mcpReviewed subset, structured tools
MCP-eligible operations share authoritative definitions with CLI, but several commands remain CLI-only and consequential execution has a separate transaction flow.
2ot --list --json2ot --mcp-dump-schema2ot mcpFast diagnostics
2ot check --fast keeps repeated repair inside the compiler.
Repair context
The standalone 2ot-agent-context compiler utility packages source and semantic context around diagnostics; it is not a routed 2ot gateway command.
Vendor boundaries
Siemens TIA Portal, Beckhoff TwinCAT and CODESYS remain explicit when target-specific behavior matters.
MCP safety and transaction planning
MCP tool discovery is channel- and policy-filtered. A raw persistent mutation does not become safe by requesting it in natural language. Denied dispatches report MCP permission errors with source-backed codes such as raw_consequential_forbidden or authorization_denied. An ineligible command may instead be absent from the tool list entirely.
Where a protected local transaction service and valid credentials are provisioned, stdio MCP transaction_plan can only prepare a workspace plan. An independent human/protected approver and separate CLI execution remain necessary. The standalone 2ot-agent-context utility is not yet an MCP tool. Concrete version-pinned tool schemas and observed rejection envelopes must be generated from an actual release executable before public distribution.