ui-bridge-mcp

# UI Bridge MCP MCP (Model Context Protocol) server for UI Bridge - enables AI to inspect and interact with UI elements. ## Overview This MCP server provides tools for: - **Inspecting UI elements** - Get element positions, bounds, visibility, and state - **Interacting with elements** - Click, type, focus, hover - **Two modes of operation**: - **Control mode**: Interact with the qontinui-runner's own Tauri webview - **External mode**: Interact with external browser tabs via Chrome extension ## Installation ```bash # Using pip pip install ui-bridge-mcp # Using poetry poetry add ui-bridge-mcp ``` ## Prerequisites The MCP server requires the **qontinui-runner** to be running on port 9876. For external browser tab access, you also need the Chrome extension connected. ## Configuration ### Claude Desktop Add to your `claude_desktop_config.json`: ```json { "mcpServers": { "ui-bridge": { "command": "ui-bridge-mcp" } } } ``` ### Claude Code Add to your MCP settings: ```json { "mcpServers": { "ui-bridge": { "command": "ui-bridge-mcp" } } } ``` ### Environment Variables | Variable | Default | Description | |----------|---------|-------------| | `QONTINUI_RUNNER_HOST` | `localhost` (or WSL host) | Runner hostname | | `QONTINUI_RUNNER_PORT` | `9876` | Runner port | ## Available Tools ### Health Check | Tool | Description | |------|-------------| | `ui_health` | Check if qontinui-runner is accessible | ### Control Mode (Runner's Own UI) | Tool | Description | |------|-------------| | `ui_snapshot` | Get complete UI state with all elements | | `ui_discover` | Force element discovery/registration | | `ui_get_element` | Get detailed info for a specific element | | `ui_click` | Click an element by ID | | `ui_type` | Type text into an input element | | `ui_focus` | Focus an element | ### External Mode (Browser Tabs) | Tool | Description | |------|-------------| | `extension_status` | Check Chrome extension connection | …