driver_session
Start or stop a WebSocket automation session for Tauri apps. Manage multiple app connections by specifying app identifiers; the most recent becomes default.
Instructions
[Tauri Apps Only] Start/stop automation session to connect to a RUNNING Tauri app. Supports multiple concurrent app connections - each app runs on a unique port. The most recently connected app becomes the "default" app used when no appIdentifier is specified. Use action "status" to check connection state: returns single app format when 1 app connected, or array format with "isDefault" indicator when multiple apps connected. Action "stop" without appIdentifier stops ALL sessions; with appIdentifier stops only that app. The identifier field (e.g., "com.example.myapp") uniquely identifies each app. REQUIRED before using other webview_* or ipc_* tools. Connects via WebSocket to the MCP Bridge plugin in the Tauri app. For browser automation, use Chrome DevTools MCP instead. For Electron apps, this tool will NOT work.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"action": "<action>"
},
"name": "driver_session"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Host address to connect to (e.g., 192.168.1.100). Falls back to MCP_BRIDGE_HOST or TAURI_DEV_HOST env vars | |
| port | No | Port to connect to (default: 9223) | |
| action | Yes | Action to perform: start or stop the session, or check status | |
| appIdentifier | No | App identifier (port number or bundle ID) to stop. Only used with action "stop". If omitted, stops all sessions. |