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
      C
      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
      2,143 npm
      1
      MIT

    • MCP Tauri Automation

      Radek44
      A
      license
      A
      quality
      B
      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
      8
      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.
      2,143 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
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (interact, keyboard, screenshot, execute_js, IPC commands, window management). The main overlap is among the element-inspection cluster: webview_find_element, webview_dom_snapshot, webview_select_element, and webview_get_pointed_element all return element metadata, and select_element vs get_pointed_element are especially close (both return rich metadata + annotated screenshot), but the descriptions distinguish their invocation mechanisms.

    Naming Consistency4/5

    A predictable verb_noun pattern dominates and domain prefixes (webview_*, ipc_*) group related tools clearly. Minor deviation: a few tools (driver_session, manage_window, list_devices, read_logs) drop the prefix convention, but they remain readable and consistent in style.

    Tool Count4/5

    At 19 tools the surface is on the heavier side but justified by a genuinely broad domain spanning session management, webview automation, IPC inspection, device enumeration, window control, and logging. Each tool maps to a distinct capability rather than padding.

    Completeness4/5

    Coverage is strong: connection lifecycle (driver_session/setup), interaction, keyboard, JS eval, element discovery, screenshots, waits, window control, IPC execution/monitoring/events, and logging. Minor gaps like navigation/history or attribute-only queries are workable via execute_js.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources