Automation: capabilities and permissions
McpBridge connects a local MCP client to running Protohaund instances. Protohaund.McpBridge.exe is shipped beside Protohaund.exe in the core application. No separate Windows service is required.
The beta supports trace analysis and operations for the selected module, subject to the license and installed packages. Local permissions are described below.
Start with connecting an MCP client. For multiple running copies, see selecting an application instance. Connector startup is covered in McpBridge.
Instance permissions
Enabling access allows Tracing and monitoring. Other categories are enabled separately:
| Permission | Allowed in beta modules |
|---|---|
Tracing and monitoring | Read available observations and work with trace documents |
Profile switching | Select an available profile and module |
Connection management | Configure, open and close the selected module's connection |
Active reads | Send explicit Modbus RTU reads and CANopen object reads over the current connection |
Device writes | Write Modbus RTU coils and registers over the current connection |
Settings persist between launches. Changes affect the current instance; other instances already running retain their own permissions. An agent cannot enable access or expand permissions through MCP. Virtual-device settings on the shared page do not grant access to those tools under the beta license.
Available tasks
| Area | Capabilities |
|---|---|
| General | Discover application instances, inspect state and capabilities; switch modules or manage connections when authorized |
| Traces | List documents, select frames or messages, build summaries, import and save supported files |
| Modbus RTU | Read cached observations; explicitly read ranges or write coils/registers when authorized |
| CANopen | List observed nodes; read specified SDO objects when authorized |
| VAG | Analyze the available trace; these capabilities do not imply execution of ECU diagnostic commands |
MCP and the interface share the same trace document. MCP filters are independent of Tracer table filters: messages hidden in the table remain in the source data. Import can replace the current document, and saving creates a file; specify the intended path and action explicitly.
modbus.get_observations reads the cache without device requests; consider the source and age of values. modbus.read_registers and canopen.read_objects generate real communication. Use zero-based Modbus addresses; specify compound types and word order according to the device documentation.
modbus.write_registers supports functions 05, 06, 0F and 10 for RTU device addresses 1–247, without broadcast writes. Writes require an idempotency key. OutcomeUnknown means the result was not acknowledged: do not automatically repeat the command with a new key. Establish the device's actual state first.