Skip to main content
Glama
Radek44

MCP Tauri Automation

by Radek44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Tauri Automation

No user-submitted related servers found.

    Related Servers

    • tauri-plugin-mcp

      DaveDev42
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to automate and test Tauri desktop applications through the Model Context Protocol. It provides tools for app management, UI interaction, and state inspection across multiple platforms without requiring CDP dependencies.
      14
      644 npm
      1
      MIT

    • tauri-mcp

      DonsWayo
      A
      license
      Not graded
      quality
      D
      maintenance
      A Tauri plugin that enables AI agents to interact with Tauri applications through screenshots, DOM inspection, and input simulation via the Model Context Protocol. It allows agents to perform actions like clicking, typing, and executing JavaScript within the application's webview context.
      644 npm
      1
      MIT

    • Tauri MCP Server

      Hushlor
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI assistants to build, test, and debug Tauri v2 applications through UI automation (screenshots, clicks, typing, element finding), IPC monitoring, log streaming, and mobile device management.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources