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.
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.
2ot --list --json2ot --mcp-dump-schema2ot mcp2ot check --fastThe 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.
Start with a resource the client can parse directly
Machine-oriented overview.
https://2ot.ai/for-agents.mdCompact product/documentation index.
https://2ot.ai/llms.txtExpanded product context.
https://2ot.ai/llms-full.txtDiscovery catalog for public resources.
https://2ot.ai/.well-known/ai-catalog.jsonOfficial favicon, theme variants, Android maskable icons and Google recrawl guidance.
https://2ot.ai/.well-known/brand-assets.jsonManifest-driven route inventory.
https://2ot.ai/sitemap.xmlLocal operational MCP model.
https://2ot.ai/mcp-agents.mdInstalled 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.