tauri-mcp

A generic MCP server that drives a built Tauri app's UI over WebDriver (tauri-driver + msedgedriver on Windows / WebKitWebDriver on Linux): launch the real app, then click, type, scroll, drag, read, and screenshot it like a human — or drop to raw JS when needed.

Not tied to any one project. Point it at any local Tauri app with projectDir or appPath. This server only knows how to drive a window; anything app-specific (reading an app's own database or config) belongs in a separate server of your own.

Tools

All tools are prefixed app_ and operate on a single running session (one app at a time).

Session

Acting (mouse / keyboard)

Reading / observing

Escape hatch

app_execute_js is unrestricted: it can read/write any DOM or JS state and invoke any Tauri backend command directly via await window.__TAURI_INTERNALS__.invoke("cmd_name", { arg }) (always present in Tauri v2, regardless of withGlobalTauri) — anything the app's own frontend can do, including commands with real side effects (writing config, filesystem, launching processes). No sandboxing beyond what the app's own command handlers enforce. It's also the workaround for OS-native dialogs (see below).

Related MCP server: MCP Server Tauri

Targeting elements: prefer text

app_snapshot emits positional CSS selectors like div > div:nth-of-type(3) > button, which break the moment the DOM is restructured. Wherever a tool takes a target, prefer text (visible text or accessible name) — app_click({ text: "Browse" }) is how a human would say it and survives layout changes. exact: true requires an exact match; otherwise it tries exact text, then substring, then ARIA accessible name (covers icon-only buttons with aria-label).

Requirements

• Node 24+ and npm install once in this folder.

• tauri-driver: cargo install tauri-driver --locked.

• Windows: Microsoft Edge WebDriver version-matched to your installed WebView2 Runtime (Settings → About Microsoft Edge WebView2, or HKLM\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5} → pv). A mismatched major version connects fine but silently never leaves about:blank — app_launch now detects this and errors. winget install Microsoft.EdgeDriver does not reliably match; download the exact version from https://msedgedriver.microsoft.com/<version>/edgedriver_win64.zip and drop it at ./bin/msedgedriver.exe (checked first) or set EDGEDRIVER_PATH.

• The target app must already be built, and not with plain cargo build — a debug binary points at devUrl and only renders if a Vite dev server is up. Use cargo tauri build --debug --no-bundle (fast) or cargo tauri build --no-bundle (release). app_launch does not build for you.

When projectDir/appPath is omitted, app_launch uses the TAURI_PROJECT_DIR environment variable; if that is unset too, it returns a clear error. There is no built-in default project.

Run / verify

npm install
# point it at any built Tauri app:
TAURI_PROJECT_DIR=/path/to/tauri-project npm run verify-automation
# or:
TAURI_APP_PATH=/path/to/built/app npm run verify-automation

The verify script launches the app, snapshots it, clicks the first interactive element, screenshots, and closes.

Known limitation: OS-native dialogs

WebDriver can only see the webview DOM. Tauri file/folder pickers, message boxes, and other OS-native dialogs are not part of the DOM and can't be clicked through — a flow that opens one will stall. Workaround: skip the dialog and drive the backend directly with app_execute_js, e.g.

// instead of clicking a "Choose folder" button that opens a native picker:
return await window.__TAURI_INTERNALS__.invoke("set_output_dir", { path: "/some/folder" });

Troubleshooting

• app_launch errors "window never rendered" — msedgedriver/WebView2 version mismatch, or a plain cargo build binary. See Requirements.

• "a session is already running" after a crash — app_force_cleanup, then relaunch.

• Selectors keep breaking — target by text instead (see above).

Register with Claude Code

Add it to an .mcp.json (project root, or ~/.claude.json for all projects), then restart Claude Code. Tools then appear as tauri:app_launch, etc.

{
  "mcpServers": {
    "tauri": {
      "command": "node",
      "args": ["--no-warnings", "/absolute/path/to/tauri-mcp/index.mjs"]
    }
  }
}

Or via the CLI:

claude mcp add tauri -- node --no-warnings /absolute/path/to/tauri-mcp/index.mjs