메뉴
Use the Hypothesi Tauri MCP server and tauri-plugin-mcp-bridge to let an agent inspect and drive a live Tauri 2 app. Trigger when debugging needs screenshots, DOM snapshots, clicks, typing, JS execution, window management, logs, or real-time IPC monitoring.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use CrabNebula DevTools for Tauri 2 Rust-side debugging, IPC analysis, tracing spans, config inspection, and command/event timing. Trigger when browser devtools are insufficient because the issue involves Rust commands, permissions, capability bundles, spans, logs, or backend performance.
Official Tauri 2 debugging baseline for desktop and mobile apps. Use when debugging any Tauri v2 issue before heavier tooling, especially for WebView errors, Rust panics, missing logs, devtools access, debug builds, LLDB/GDB workflows, or plugin-log setup.
Tauri 2 end-to-end debugging workflow that chooses between official baseline tools, CrabNebula DevTools, and a live MCP bridge. Use when debugging is ambiguous or spans frontend UI, Rust commands, IPC, logs, and runtime state together.
| name | tauri-hypothesi-mcp-bridge |
| description | Use the Hypothesi Tauri MCP server and tauri-plugin-mcp-bridge to let an agent inspect and drive a live Tauri 2 app. Trigger when debugging needs screenshots, DOM snapshots, clicks, typing, JS execution, window management, logs, or real-time IPC monitoring. |
This is the best fit when the agent must see and operate the running app instead of guessing from code.
cargo add tauri-plugin-mcp-bridge
Register it only in debug builds:
fn main() {
let mut builder = tauri::Builder::default();
#[cfg(debug_assertions)]
{
builder = builder.plugin(tauri_plugin_mcp_bridge::init());
}
builder
.run(tauri::generate_context!())
.expect("error while running tauri application");
}
@hypothesi/tauri-mcp-server@hypothesi/tauri-mcp-cli9223driver_session: start/stop/status the automation bridgemanage_window: list and target windowswebview_screenshot: capture current UI statewebview_dom_snapshot: inspect structured UI statewebview_execute_js: verify runtime assumptionsread_logs: inspect console, Android, iOS, or system logsipc_monitor: start or stop IPC capture during reproductionipc_get_captured: review what commands/events actually happenedipc_execute_command: directly call backend commands when isolating behaviordriver_session and confirm connection.manage_window to list windows if the app is multi-window.ipc_monitor if the bug may cross the frontend/backend boundary.