MCP Tauri Automation
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAURI_APP_PATH | No | Path to your Tauri app binary (required in tool call or env) | |
| TAURI_DRIVER_PATH | No | Path to tauri-driver binary | tauri-driver |
| TAURI_SCREENSHOT_DIR | No | Where to save screenshots | ./screenshots |
| TAURI_WEBDRIVER_PORT | No | Port where tauri-driver runs | 4444 |
| TAURI_DEFAULT_TIMEOUT | No | Element wait timeout in ms | 5000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| launch_appB | Launch a Tauri application via tauri-driver. The tauri-driver must be running on the configured port (default: 4444). |
| close_appA | Close the currently running Tauri application gracefully |
| capture_screenshotA | Capture a screenshot of the application window. Returns base64-encoded PNG image data by default. |
| click_elementB | Click a UI element identified by a CSS selector |
| type_textC | Type text into an input field or editable element |
| wait_for_elementB | Wait for an element to appear in the DOM. Useful for handling async UI states. |
| get_element_textB | Get the text content of an element |
| execute_tauri_commandC | Execute a Tauri IPC command. The command must be exposed in the Tauri app's src-tauri/src/main.rs file. |
| get_app_stateB | Get the current state of the application, including whether it's running, session info, and page details |
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 9 tools
Each tool has a clearly distinct purpose with no significant overlap. The tools cover different aspects of Tauri automation: launching/closing apps, UI interaction (clicking, typing, waiting), element inspection, screenshot capture, and command execution. The descriptions make it easy to distinguish between similar tools like click_element and wait_for_element.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. The naming is predictable and readable: capture_screenshot, click_element, close_app, execute_tauri_command, get_app_state, get_element_text, launch_app, type_text, wait_for_element. There are no deviations in naming conventions.
With 9 tools, this is well-scoped for Tauri automation. Each tool earns its place by covering essential operations: app lifecycle management, UI interaction, element inspection, and command execution. The count is neither too sparse nor bloated, providing comprehensive coverage without redundancy.
The tool set provides excellent coverage for core Tauri automation workflows including app control, UI interaction, and state inspection. Minor gaps exist such as no explicit tool for navigating between pages/windows or handling file operations, but agents can work around these using existing tools like execute_tauri_command for extended functionality.