MCP integration
Authenticated local control from automation agents.
MCP integration
Busloom can expose the open desktop session as a local Model Context Protocol server. Its 95 tools adapt the same project, connection, discovery, alarm, diagnostic, Trend, report, and automation paths—not a second hidden Modbus client.
Enable a client
Open Application Preferences → MCP
MCP is a Professional feature and is disabled by default.
Enable the local server
The listener binds only to 127.0.0.1 and Busloom must remain open.
Copy URL and bearer token
Configure the client for Streamable HTTP and send the token in the Authorization header.
Keep prompts enabled first
Read and project operations can proceed, while tag writes and real write-capable automation ask in Busloom.
Regenerate after exposure
Regenerating the token restarts the enabled server and disconnects existing clients.
What an agent can orchestrate
The MCP surface covers project creation/open/save, profiles, RTU and TCP/TLS discovery, connection, scans, views, tags, acquisition, bounded observation of changing values, writes, Protocol Diagnostics, Raw Traffic, runtime alarms, machine-readable exports, PNG/PDF Trend reports, automation, Replay, and Git. Mutations use the same project validator and undo/history path. Unsaved MCP edits remain unsaved until the project is explicitly saved.
New 0.4 workflows use the same boundaries
| Workflow | What MCP does | Boundary |
|---|---|---|
| Public device catalog | Search reviewed definitions and preview the ordinary atomic merge | Repeat with apply enabled only after reviewing changes and issues |
| Tag alarms | Create project-owned rules and inspect or acknowledge the shared session runtime | Acknowledgement and transition history reset with the runtime |
| Trend report | Render the selected visible window through the desktop PNG/PDF renderer | Provide an absolute .png or .pdf path; an empty window is rejected |
| Control | Protection | Operator responsibility |
|---|---|---|
| Loopback binding | Prevents direct network exposure | A local malicious process is still in scope |
| Bearer token | Authenticates every request | Store it only in the local MCP client configuration |
| Write prompts | Require visible approval for device changes | Can be disabled explicitly; read-only profiles still win |
| Bounded operations | Limits payloads, observations, scans, and project discovery | Exhaustive scan requires explicit confirmation |