Tauri MCP
Gives an agent visibility into a running Tauri v2 application: inspect state, drive actions, read logs.
What it does
Gives an agent visibility into a running Tauri v2 application: inspect state, drive actions, read logs. Narrow to one framework, and the right choice if that is your framework — desktop apps are otherwise opaque to automation. Verify it matches your Tauri major version before wiring it in.
Install
npx -y @hypothesi/tauri-mcp-server
Client configuration
Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.
{
"mcpServers": {
"tauri": {
"command": "npx",
"args": [
"-y",
"@hypothesi/tauri-mcp-server"
]
}
}
}
Use it for
Developing a Tauri desktop app with agent support for its runtime
Skip it if
Electron or web apps; different runtime, different tooling
When to use it
Reach for this when the task needs desktop inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.
Other TypeScript servers
- Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
- Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
- Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude