Labsco
MCP SERVER

Tauri MCP Server

by dirvine

Drive a running Tauri v2 app from your assistant — launch it, click and type in it, screenshot it, run JavaScript in its webview and call its IPC commands directly.

Runtime Debugging & Crash Analysis
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 `tauri-mcp-node-*.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

One command — cargo install tauri-mcp