Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub davedev42/tauri-plugin-mcpTauri desktop app test automation via MCP. Launch, inspect, interact with, and test Tauri v2 apps using accessibility tree snapshots and DOM manipulation.
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Production-ready workflow orchestration with 84 marketplace plugins, 192 local specialized agents, and 156 local skills - optimized for granular installation and minimal token usage
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
Share bugs, ideas, or general feedback.
Cross-platform Tauri test automation plugin via MCP (Model Context Protocol).
Enables AI assistants like Claude to interact with your Tauri desktop app for testing and automation.
This repo doubles as a Claude Code plugin. Install it to get the MCP server, QA agent, skills, and validation hooks all at once:
# 1. Add the marketplace source
claude plugin marketplace add DaveDev42/tauri-plugin-mcp
# 2. Install the plugin
claude plugin install tauri-mcp --scope project
Or inside a Claude Code session:
/plugin marketplace add DaveDev42/tauri-plugin-mcp
/plugin install tauri-mcp --scope project
During installation, you'll be prompted for:
. for single-app repos, apps/desktop for monorepos)This automatically configures the MCP server, QA agent, skills, and validation hooks. No manual .mcp.json setup needed.
What's included:
| Component | Description |
|---|---|
| MCP Server | Auto-configured tauri-mcp (14 tools for app lifecycle, UI interaction, screenshots, logging) |
tauri-qa skill | QA orchestration -- prepares test scenarios, delegates to QA agent, validates results |
tauri-setup skill | Step-by-step guide for installing tauri-plugin-mcp in a Tauri v2 project |
tauri-debug skill | Diagnostic decision trees for common MCP session issues |
qa-tester agent | Testing agent (haiku) that executes test scenarios using MCP tools |
| QA validation hook | Verifies QA PASS results include actual tool call evidence |
src-tauri/Cargo.tomlpnpm add github:DaveDev42/tauri-plugin-mcp#mainsrc-tauri/src/lib.rsmcp:default permissionmain.tsx.mcp.json for Claude Code[dependencies]
tauri-plugin-mcp = { git = "https://github.com/DaveDev42/tauri-plugin-mcp" }
pnpm add github:DaveDev42/tauri-plugin-mcp#main
The MCP server binary (tauri-mcp) is automatically available after installation. No additional setup required.
pub fn run() {
tauri::Builder::default()
.plugin(tauri_plugin_mcp::init())
.run(tauri::generate_context!())
.expect("error while running tauri application");
}
Option A: In tauri.conf.json or config/*.json5 (recommended)
{
"security": {
"capabilities": [{
"identifier": "main-capability",
"windows": ["main"],
"permissions": ["core:default", "mcp:default"]
}]
}
}
Option B: Separate file (src-tauri/capabilities/default.json)
{
"$schema": "../gen/schemas/desktop-schema.json",
"identifier": "default",
"windows": ["main"],
"permissions": ["core:default", "mcp:default"]
}
// Initialize MCP bridge for E2E testing (dev mode only)
if (import.meta.env.DEV) {
import('tauri-plugin-mcp').then(({ initMcpBridge }) => {
initMcpBridge().catch(err => {
console.warn('[MCP] Bridge initialization failed:', err);
});
});
}
The basic setup above includes MCP in all builds. For production apps, you likely want MCP only in development and completely stripped from release binaries.
This approach uses Cargo's optional dependency feature so the plugin is compiled in only when explicitly requested.
[features]
default = []
dev-tools = ["dep:tauri-plugin-mcp"]
[dependencies]
tauri-plugin-mcp = { git = "https://github.com/DaveDev42/tauri-plugin-mcp", optional = true }
pub fn run() {
let mut builder = tauri::Builder::default();
#[cfg(feature = "dev-tools")]
{
builder = builder.plugin(tauri_plugin_mcp::init());
}
builder
.run(tauri::generate_context!())
.expect("error while running tauri application");
}