Skip to main content
Glama
hypothesi

MCP Server Tauri

by hypothesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Server Tauri

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
      927 npm
      1
      MIT

    • MCP Tauri Automation

      Radek44
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-driven testing and automation of Tauri desktop applications through natural language, allowing users to interact with UI elements, capture screenshots, execute commands, and test application flows without manual clicking or complex scripts.
      9
      7
      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.
      927 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

    A4.2/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools are clearly separated by domain (webview_*, ipc_*, window, device, session), and the descriptions explicitly disambiguate overlapping concerns like webview_find_element vs webview_dom_snapshot vs webview_select_element. However, webview_select_element and webview_get_pointed_element return nearly identical metadata and differ only in how the element is chosen, which could cause confusion.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern with clear domain prefixes: get_setup_instructions, list_devices, driver_session, manage_window, read_logs, and the webview_*/ipc_* families. Minor deviations exist: driver_session is a noun phrase rather than verb_noun, and ipc_get_backend_state breaks the ipc_* verb pattern slightly, but overall the convention is predictable.

    Tool Count4/5

    20 tools is on the higher end but justified for a Tauri automation server covering session management, webview interaction, IPC monitoring, and device support. Each tool serves a distinct purpose, though a few (webview_select_element vs webview_get_pointed_element) could arguably be merged.

    Completeness4/5

    The tool set covers the full automation lifecycle: setup, session management, webview inspection/interaction, IPC monitoring, and logging. Minor gaps exist—there's no explicit tool for managing app lifecycle (launch/terminate) or for handling multiple windows beyond listing/info/resize—but the core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources