Mcp Server Tauri

@hushlor/tauri-mcp-server

[npm version] [License: MIT]

A Model Context Protocol (MCP) server that enables AI assistants like Claude, Cursor, and Windsurf to build, test, and debug Tauri® v2 applications.

📖 Full Documentation

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

cargo add tauri-plugin-hushlor-mcp-bridge --rename tauri-plugin-mcp-bridge --version 0.14.0

// src-tauri/src/main.rsfn main() {    let mut builder = tauri::Builder::default();
    #[cfg(debug_assertions)]    {        builder = builder.plugin(tauri_plugin_mcp_bridge::init());    }
    builder        .run(tauri::generate_context!())        .expect("error while running tauri application");}

Note: The npm package @hushlor/tauri-plugin-mcp-bridge is 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:

npx -y @a1st/aix add mcp tauri --command 'npx @hushlor/tauri-mcp-server' --user

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:

npm install -g @hushlor/tauri-mcp-clitauri-mcp driver-session start --port 9223tauri-mcp driver-session status --json

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 appIdentifier specified
• Target specific apps using port number or bundle ID
• Stop individual sessions or all sessions at once

Example Usage:

// Connect to first appawait driver_session({ action: "start", port: 9223 })
// Connect to second appawait driver_session({ action: "start", port: 9224 })
// Check status - shows both apps with default indicatorawait driver_session({ action: "status" })
// Use default app (most recent - port 9224)await webview_screenshot()
// Target specific app by portawait webview_screenshot({ appIdentifier: 9223 })
// Stop specific appawait driver_session({ action: "stop", appIdentifier: 9223 })
// Stop all appsawait driver_session({ action: "stop" })

Available Tools (22 total)

Setup & Configuration

UI Automation

IPC & Plugin

Mobile Development

Links

• Documentation
• GitHub Repository
• MCP Bridge Plugin (crates.io)
• Changelog

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.