tauri-plugin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAURI_PROJECT_ROOT | Yes | The path to the Tauri project root directory. This is used to locate the project's socket file for communication. | . |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_session_statusA | Check session (app) status. Use probe_bridge to verify bridge health per window. |
| start_sessionC | Start session (launch Tauri app) |
| stop_sessionB | Stop session (kill app) |
| list_windowsA | List all open windows with their labels, titles, and focus state |
| focus_windowB | Focus a specific window by label |
| snapshotA | Get accessibility tree (returns ref numbers for click/fill) |
| clickC | Click element by ref or selector |
| fillC | Fill input by ref or selector |
| press_keyD | Press key |
| evaluate_scriptC | Run JS in webview |
| screenshotC | Take screenshot |
| navigateC | Navigate to URL |
| get_logsC | Get application logs with filtering. Filters can be combined (e.g., ["build", "error"] for build errors only). |
| get_restart_eventsA | Get recent app restart/reload events with the files that triggered them. Includes Rust rebuilds (backend) and HMR updates (frontend). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct action or information source: UI interactions (click, fill, press_key), scripting (evaluate_script), navigation (navigate), visual capture (screenshot), accessibility (snapshot), window management (list_windows, focus_window), session lifecycle (start/stop_session), and diagnostics (get_logs, get_restart_events, get_session_status). No two tools have overlapping purposes.
All tool names follow a clear verb_noun pattern using lowercase with underscores (e.g., get_logs, focus_window, start_session). Even single-word names like click, fill, navigate are consistent with the imperative style. No mixed conventions or inconsistent verbs.
14 tools is well-scoped for a Tauri testing/MCP server. It covers all major aspects: session control, window management, UI interaction, scripting, diagnostics, and capture. The count is neither too sparse (missing essential features) nor bloated.
The tool surface covers the full lifecycle of a Tauri app test: start/stop sessions, manage windows, interact via clicks/keys/scripts, navigate, capture screenshots and accessibility trees, and retrieve logs/events. No obvious gaps for typical automation tasks, making it a self-contained toolset.