Integrations and deployment

Connect EROBS to MCP clients, Bluesky, and EPICS, or configure it for containers and other beamlines. Task clients submit requests to the existing ROS action servers.

Connection	Boundary	Read
MCP clients	Tools for ROS communication and beamline-specific operations	MCP and the direct agent
GUI chat	A mode-specific task proposal/execution interface around the shared agent	MCP and the direct agent
Bluesky/Ophyd	Convert a RunEngine operation into an `MTCExecution` goal	Bluesky and EPICS
EPICS utilities	Expose one PV as a ROS topic or service	Bluesky and EPICS
Containers	Bundle selected ROS/client dependencies and source	Container images
Other beamlines	Supply models, calibration, tool and site data	Beamline adaptation

The repository’s primary manual interface is the operator GUI. The direct agent and GUI chat remain experimental. Bluesky integration is not verified end to end; its guide lists the known wrapper defects.

To trace a client request in code, use Clients and integrations. Its starting functions cover direct JSON submission, MCP task construction, agent tool calls, and asynchronous Bluesky completion.

Pixi supplies ROS client and scientific/Bluesky dependencies. Running the robot stack additionally requires MoveIt, robot drivers, and any camera SDKs used by the deployment.