| name | feather-mcp-live-sessions |
| description | Use when an agent should inspect or control a running Feather desktop session through MCP. |
Feather MCP Live Sessions
Preconditions
- Feather desktop must be running.
- Settings > Security > MCP Access must be enabled.
- Start the MCP server with
feather mcp for stdio clients, or feather mcp --transport http for localhost HTTP clients.
Workflow
- Discover sessions with
feather://sessions or feather_list_sessions.
- Pull a full snapshot with
feather_session_snapshot before sending commands.
- Read narrow resources when possible:
feather://sessions/{id}/configfeather://sessions/{id}/logsfeather://sessions/{id}/performancefeather://sessions/{id}/debuggerfeather://sessions/{id}/pluginsfeather://sessions/{id}/assetsfeather://sessions/{id}/observers
- Use explicit tools before the escape hatch. Reserve
feather_send_command for advanced runtime commands and strip app IDs, API keys, MCP tokens, and secret fields from inputs.
- If the bridge is unavailable, say that the desktop bridge is unavailable and give the exact local command or setting needed.
Safety
Never expose app IDs, API keys, bearer tokens, or MCP bridge tokens in notes, tool arguments, resources, or generated artifacts.
References
- Read
references/workflow.md for MCP session discovery, resource selection, command safety, and unavailable-bridge handling.
