rust-debug-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (e.g., info, debug) | info |
| TAURI_WS_URL | No | WebSocket URL for Tauri debug backend | ws://localhost:9002 |
| COMMANDER_WS_URL | No | WebSocket URL for Commander backend | ws://localhost:9002 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tauri_debug_commandA | Debug and inspect Tauri applications via WebSocket. MULTI-APP SUPPORT: This tool can connect to any Tauri app with a debug WebSocket endpoint.
QUICK REFERENCE:
FILTERING TASKS (avoid loading all tasks): { "command": "get_task", "params": { "task_id": 123 } } { "command": "get_tasks_by_status", "params": { "status": "working" } } { "command": "get_all_tasks", "params": { "status": "pending", "limit": 20 } } { "command": "get_all_tasks", "params": { "recent_only": true } } RESPONSE FORMAT: Add response_format: "concise" (default) or "detailed" to control verbosity.
APP LIFECYCLE COMMANDS:
CORE COMMANDS (all apps):
COMMANDER-SPECIFIC COMMANDS:
UI AUTOMATION COMMANDS:
EXAMPLES: { "command": "start_app", "app": "photon" } { "command": "start_app", "app": "photon", "params": { "command": "cargo tauri dev", "waitForConnection": true } } { "command": "kill_app", "app": "photon" } { "command": "kill_app", "app": "photon", "params": { "force": true } } { "command": "test_connection" } { "command": "test_connection", "app": "photon" } { "command": "get_task", "params": { "task_id": 42 } } { "command": "get_tasks_by_status", "params": { "status": "working" } } { "command": "get_all_tasks", "params": { "limit": 10 }, "response_format": "detailed" } { "command": "broadcast_to_frontend", "params": { "action": "execute_js", "payload": { "script": "document.title" } } } { "command": "get_snapshot" } { "command": "click", "params": { "uid": "e5" } } { "command": "fill", "params": { "uid": "e3", "value": "test@example.com" } } { "command": "take_screenshot", "params": { "full_page": true } } { "command": "get_console_logs", "params": { "types": ["error", "warn"], "limit": 50 } } RESPONSE: Returns { success: boolean, data?: unknown, error?: string } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another tool. The tool name clearly indicates its purpose, and the internal commands are well-documented.
With a single tool, naming consistency is inherently satisfied. The name 'tauri_debug_command' is descriptive and follows a clear, consistent pattern.
The server exposes only one tool despite covering a broad range of functionality (app lifecycle, tasks, system metrics, UI automation). This is a significant mismatch—the scope warrants multiple focused tools rather than a single oversized one.
The tool bundles a comprehensive set of commands covering app lifecycle, health checks, system metrics, task management (Commander-specific), sessions, UI automation, and more. It covers the main debugging workflows for Tauri apps, though some task mutation operations are absent, leaving minor gaps.