launch_appLABSCO SUMMARY
The desktop app becomes something an agent can poke.
Debugging a Tauri app usually means alt-tabbing between the app, its logs and its devtools. Here the window, the console, the resource use and the IPC layer are all reachable from one thread — including calling a Rust command without going through the UI that would normally trigger it.
What it is
An MCP server for testing and debugging Tauri v2 applications. It speaks JSON-RPC over stdio, implements the initialize/shutdown handshake, and exposes a set of Tauri-specific tools with JSON Schema definitions.
What you get
- The app launched with arguments, and stopped gracefully
- Stdout and stderr captured while it runs
- CPU, memory and disk usage tracked
- Screenshots of the app window, and its dimensions, position and state read back
- Keyboard input and mouse clicks simulated, with movement, dragging and scrolling supported
- JavaScript executed inside the webview, and DevTools connection information returned
- The registered Tauri commands listed, and any of them called directly
Requirements
A Tauri v2 application to point it at. For Claude Desktop the simplest path is the .dxt desktop extension from the releases page — download it and double-click. The server accepts both the numeric and the date-based form of the protocol version string, so an older client still handshakes.
Setup effort
Build from source — clone the repository, then follow the steps on this page
USE CASES
01
Reproducing a bug from a clean start
Launch the app with the arguments that trigger it, then capture the log output.
02
Seeing what the user sees
Take a screenshot of the window and read its dimensions and state.
03
Walking a flow without touching the mouse
Send the clicks and keystrokes, then screenshot where it ended up.
04
Testing a Rust command in isolation
List the registered IPC handlers, then call the one you want with your own arguments.
05
Inspecting frontend state
Execute JavaScript in the webview and read what comes back, with the DevTools endpoint if you need to attach.
06
Finding out whether it leaks
Track CPU, memory and disk while you exercise the app, then stop it cleanly.
12 tools
Listed in project docs. Your client may show a different list.
stop_appget_app_logsmonitor_resourcestake_screenshotget_window_infosend_keyboard_inputsend_mouse_clickexecute_jsget_devtools_infolist_ipc_handlerscall_ipc_commandBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
- Rust toolchain, for the cargo install and the source build
- On macOS, accessibility and screen-recording permission, for input simulation and screenshots
INSTALLATION
Connect your client
Server setup
Clone the repository
TERMINAL
git clone https://github.com/dirvine/tauri-mcp.git
cd tauri-mcpBuild and install
TERMINAL
cargo install --path .Start the MCP server
TERMINAL
tauri-mcp serveMCP Clients
Claude Desktop
Download the .dxt desktop extension from the releases page: https://github.com/dirvine/tauri-mcp/releases (the current release ships tauri-mcp-0.1.5.dxt)
Double-click the .dxt file to install it, or drag it onto Claude Desktop. The extension configures the server for you.
Use the extension rather than the cargo route for Claude Desktop: the project says Claude Desktop disconnects immediately from the Rust binary configured directly ("command": "tauri-mcp"). The project names the cargo install for command-line use (tauri-mcp serve), integration with other tools, and development and testing, and publishes no client configuration for it.
