Skip to main content
Glama
hypothesi

MCP Server Tauri

by hypothesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ipc_execute_command

[Tauri Apps Only] Execute Tauri IPC commands (invoke Rust backend functions). Requires active driver_session. This is Tauri-specific IPC, not browser APIs.

Instructions

[Tauri Apps Only] Execute Tauri IPC commands (invoke Rust backend functions). Requires active driver_session. This is Tauri-specific IPC, not browser APIs. Plugin commands (plugin:mcp-bridge|*) are routed through the bridge; all other commands are executed via the webview using window.TAURI_INTERNALS.invoke, which keeps the application's Tauri capability rules in force. For Electron IPC or browser APIs, use appropriate tools for those frameworks.

Input Schema

NameRequiredDescriptionDefault
argsNo
commandYes
windowIdNoWindow label to target (defaults to "main") for app commands
appIdentifierNoApp port or bundle ID to target. Defaults to the only connected app or the default app if multiple are connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / windowId
      Added value: +{
+  "description": "Window label to target (defaults to \"main\") for app commands",
+  "type": "string"
+}
  2. Addedv0.11.1

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the non-read-only, non-destructive, non-open-world profile, and the description adds real behavioral context: plugin:mcp-bridge|* commands route through the bridge while others go through window.__TAURI_INTERNALS__.invoke, and Tauri capability rules stay enforced. It does not describe return payloads or failure modes, minor given the routing detail it supplies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the critical '[Tauri Apps Only]' qualifier and keeps the routing/output distinctions compact. Dense in clauses but essentially no filler; each clause carries routing or scoping information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-trivial execution tool with no output schema it covers the important behavioral constraints (driver_session, capability enforcement, routing). The remaining gap is that the 'args' parameter is unexplained, but everything an agent needs to select and route the call is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: windowId and appIdentifier are documented, but 'command' and especially 'args' are bare. The description clarifies the plugin:mcp-bridge|* command naming convention, but says nothing about the args structure, leaving a required-adjacent parameter undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (execute Tauri IPC commands / invoke Rust backend functions) and gates scope up front with '[Tauri Apps Only]'. It explicitly distinguishes itself from browser APIs and Electron IPC, so an agent can separate it from siblings like webview_execute_js without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use condition (Tauri apps, active driver_session required) and a when-not (not browser APIs, not Electron IPC). The alternative is only gestured at ('use appropriate tools for those frameworks') rather than named, which is the one gap keeping it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools