tauri-mcp-cli

Automates Tauri v2 webview interaction, IPC debugging, and driver session management from terminal commands.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/serguei9090/LogLensAi --skill tauri-mcp-cli-serguei9090
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tauri-mcp-cli
Source: https://github.com/serguei9090/LogLensAi/tree/main/.agents/skills/tauri-mcp-cli
Command: npx skills add https://github.com/serguei9090/LogLensAi --skill tauri-mcp-cli-serguei9090

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing and debugging Tauri v2 desktop and mobile apps normally requires manual clicking through the UI and guessing at IPC behavior. This Skill lets an agent drive the app from the terminal: starting driver sessions, clicking elements, capturing screenshots, executing JavaScript in the webview, and inspecting IPC traffic. ## Core Features & Use Cases - Driver Session Lifecycle: Start, verify, and stop MCP driver sessions with keep-alive daemon state shared across separate CLI invocations. - UI Automation: Click, focus, type, scroll, wait for selectors, and capture screenshots written to disk for before/after verification. - IPC Inspection: Execute backend commands, monitor and capture IPC traffic around interactions, and emit synthetic events. - Mobile and Remote Targets: Connect to Android emulators, iOS simulators, and real devices via adb reverse or explicit host/port. - Use Case: After changing a login form, start a driver session, type credentials into the email field, click submit, wait for the success message, and screenshot the result to confirm the fix. ## Quick Start Ask the agent to start a tauri-mcp driver session on port 9223, verify it reports connected true, then click a selector and take a screenshot of the result.

Frequently Asked Questions about tauri-mcp-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a Tauri app from the command line?

Start a driver session with tauri-mcp driver-session start --port 9223, then verify connected: true via driver-session status. After that, run webview-interact, webview-keyboard, and webview-screenshot commands in separate shell invocations; the daemon preserves session state.

How do I debug IPC commands in a Tauri v2 app?

Use ipc-execute-command to invoke backend commands directly, and ipc-monitor start/stop with ipc-get-captured to record IPC traffic around a UI interaction. ipc-get-backend-state returns the current backend state as JSON.

Can tauri-mcp connect to Android or iOS devices?

Yes. Emulators and simulators work with a standard local session. Real Android devices require adb reverse tcp:9223 tcp:9223 first, and real iOS devices or network targets need an explicit --host address. Mobile logs are read via read-logs --source android or ios.

Why does tauri-mcp driver-session status show connected false?

The start command can succeed even when no app is reachable, so always check the status output. Confirm the app is running in dev mode, the tauri-plugin-mcp-bridge plugin is registered, and the port matches; restart the daemon if it is stale.

Why does webview-execute-js return null for my script?

The script must be an expression, not an arrow function wrapper. Passing "() => { return document.title; }" returns null, while passing "document.title" directly returns the value.

Does tauri-mcp webview-screenshot return image data on stdout?

No. Screenshots always write files to disk via the --file flag; the CLI does not return base64 image data on stdout. Scroll off-screen content into view before capturing.