
Mcp Server Tauri
io.github.HushlorPublished by GitHub account Hushlorv0.14.3Updated Oct 24, 2026
A Model Context Protocol server for use with Tauri v2 applications
Overview
Lets an AI assistant build, test and debug Tauri v2 desktop apps by driving their webview UI, IPC layer, logs and mobile devices.
- What you can do
- Inspect and drive the app UI: find elements, click, scroll, type, wait, read computed styles, take screenshots, snapshot the DOM, pick elements visually and manage windows
- Run JavaScript in the webview and inspect or operate native Windows dialogs
- Work with Tauri IPC: execute commands, read backend state, emit events, and start or stop IPC monitoring to capture traffic
- Read console, Android logcat, iOS and system logs, and list Android devices and iOS simulators
- Manage automation sessions across several running apps by port or bundle ID, and fetch setup instructions for the bridge plugin
- When to use it
- Useful when developing or debugging a Tauri v2 application and you want the assistant to reproduce UI flows, inspect IPC calls, capture logs or check mobile targets instead of describing steps for you to run by hand.
- Requirements
- Runs locally over stdio via the npm package, so Node.js is needed. The Tauri app must include the tauri-plugin-mcp-bridge Rust plugin (debug builds), and the server talks to it over a WebSocket on a port such as 9223. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Mcp Server Tauri in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@hushlor/tauri-mcp-server
A Model Context Protocol (MCP) server that enables AI assistants like Claude, Cursor, and Windsurf to build, test, and debug Tauri® v2 applications.
Independent downstream fork: Hushlor maintains this distribution independently of hypothesi/mcp-server-tauri, preserving the upstream MIT license and attribution.
Features
Quick Start
1. Add the MCP Bridge Plugin to Your Tauri App
Note: The npm package
@hushlor/tauri-plugin-mcp-bridgeis optional—only needed if you want to call the plugin from your app's frontend code. The MCP server communicates with the Rust plugin directly via WebSocket.
2. Configure Your AI Assistant
Use aix to add the server to your AI assistant:
Supported clients: claude-code, cursor, windsurf, vscode, cline, roo-cline, claude, zed, goose, warp, codex
Terminal CLI
If you want to call the same tools directly from a shell, install the companion CLI package:
The CLI keeps the underlying MCP server warm in the background so stateful commands such as driver_session work across separate invocations.
Multi-App Support
The MCP server supports connecting to multiple Tauri apps simultaneously. Each app runs on a unique port, and the most recently connected app becomes the "default" app.
Key Features:
- Connect to multiple apps on different ports
- Default app used when no
appIdentifierspecified - Target specific apps using port number or bundle ID
- Stop individual sessions or all sessions at once
Example Usage:
Available Tools (22 total)
Setup & Configuration
UI Automation
IPC & Plugin
Mobile Development
Links
License
MIT © Hushlor. Original upstream copyright and attribution are preserved in the package LICENSE; see hypothesi/mcp-server-tauri for provenance.
Trademark Notice
TAURI® is a registered trademark of The Tauri Programme within the Commons Conservancy. https://tauri.app/
This project is not affiliated with, endorsed by, or sponsored by The Tauri Programme within the Commons Conservancy.
Source: packages/mcp-server/README.md at commit 06ff367
Tools
0Version history
3- v0.14.3LatestOct 6, 2026
- v0.14.2Oct 6, 2026
- v0.14.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts