Tauri Dev MCP Server

A Model Context Protocol (MCP) server that enables AI assistants to interact with Tauri applications for development, debugging, and automation.

Features

• DOM Inspection: inspect_element, query_selector
• Console Monitoring: get_console_logs
• UI Automation: click_element, input_text, scroll_to_element, hover_element, select_option, check_checkbox, press_key, wait_for_element
• Tauri Command Invocation: tauri_invoke MCP tool and direct HTTP API access to invoke any Tauri commands

Quick Start

1. Build components

   cd mcp-server && npm install && npm run build
   cd ../tauri-plugin && cargo build --release

2. Run example app (with optional custom address)

   # Default (127.0.0.1:3001)
   cd example-app && npm run tauri dev
   
   # Custom address
   cd example-app && TAURI_MCP_HOST=localhost TAURI_MCP_PORT=8080 npm run tauri dev

3. Add plugin to your Tauri app

   # In your Cargo.toml
   [dependencies]
   tauri-dev-mcp = { path = "path/to/tauri-dev-mcp/tauri-plugin" }

   // In your main.rs
   fn main() {
       // Initialize logging (choose one):
       env_logger::init();  // For env_logger
       // OR
       tracing_subscriber::fmt::init();  // For tracing
   
       tauri::Builder::default()
           .plugin(tauri_dev_mcp::init())
           .invoke_handler(tauri::generate_handler![
               // Your Tauri commands here
           ])
           .run(tauri::generate_context!())
           .expect("error while running tauri application");
   }

   // In your tauri.conf.json, enable global Tauri API access:
   {
     "app": {
       "withGlobalTauri": true,
       // ... other settings
     }
   }

   Logs: Plugin will show startup messages like "🌐 Tauri Dev MCP HTTP API server started" and "✅ MCP Inspector injected successfully!"

4. Configure Claude Desktop

   {
     "mcpServers": {
       "tauri-dev": {
         "command": "node",
         "args": ["./mcp-server/dist/index.js"],
         "env": {
           "TAURI_MCP_HOST": "localhost",
           "TAURI_MCP_PORT": "8080"
         }
       }
     }
   }

   Note: Use same TAURI_MCP_HOST/TAURI_MCP_PORT values in both Tauri app and MCP server config. Omit env field for defaults (127.0.0.1:3001).

Testing

MCP Tools (via Claude Desktop or MCP clients)

Use the tauri_invoke tool in Claude Desktop or any MCP client:

Tool: tauri_invoke
Arguments:
- command: "get_app_version"
- args: {}

Tool: tauri_invoke  
Arguments:
- command: "greet"
- args: {"name": "Claude"}

Direct HTTP API Testing

npm test

# MCP tools
curl -X POST http://127.0.0.1:3001/api/execute \
  -H "Content-Type: application/json" \
  -d '{
    "tool": "query_selector",
    "params": {"selector": "button", "limit": 5}
  }'

Tauri Command Invocation

# Invoke Tauri commands via dedicated endpoint
curl -X POST http://127.0.0.1:3001/api/invoke \
  -H "Content-Type: application/json" \
  -d '{
    "command": "get_app_version",
    "args": {}
  }'

# Command with parameters
curl -X POST http://127.0.0.1:3001/api/invoke \
  -H "Content-Type: application/json" \
  -d '{
    "command": "greet",
    "args": {"name": "World"}
  }'

# Complex command with JSON response
curl -X POST http://127.0.0.1:3001/api/invoke \
  -H "Content-Type: application/json" \
  -d '{
    "command": "get_system_info",
    "args": {}
  }'

Troubleshooting

Inspector Not Available

Problem: window.__TAURI_DEV_MCP is undefined

Solution: The inspector auto-injects on first tool call. If issues persist, ensure logging is configured and check terminal for error messages.

License

MIT