Server facts
mcp-server-tauri
Project
- Author
- hypothesi
- Repository
- github.com/hypothesi/mcp-server-tauri
- License
- Not specified
- Category
- Mobile & Desktop Automation
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 323
- Last commit
- Data as of
Tags
- Automation
- Debugging
- desktop
- development
- mobile
- programming
- tauri
- testing
- visual
Overview
Webview testing in mcp-server-tauri begins with a driver session linked over WebSocket to the MCP Bridge plugin inside a running Tauri app. Once connected, an assistant can locate and focus elements, inspect computed styles, capture the visible viewport, and interact through clicks, scrolling, gestures, and keyboard input. Console logs and JavaScript execution support webview investigation, while IPC tools invoke Rust functions, monitor calls, and retrieve captured arguments and responses. Tauri events can also be emitted to exercise event handlers.
Project-level tools run Tauri CLI commands, read main or platform-specific configuration, and validate JSON structure before writing configuration changes. Documentation lookup supplies Tauri v2 guidance and API references. For mobile testing, the server lists Android devices and emulators plus iOS simulators, and can launch an Android AVD or iOS Simulator. Platform log access covers Android logcat, iOS device logs, and desktop system logs. The /fix-webview-errors prompt guides an assistant through connecting to the app, retrieving JavaScript console errors, analyzing them, and helping with fixes. These workflows target Tauri applications rather than Electron or browser-only projects.
mcp-server-tauri setup notes
- mcp-server-tauri records stdio only; confirm a network transport upstream before planning remote access.
- mcp-server-tauri has no recorded license; confirm reuse terms in its repository.