FlashDesk

Control another PC's desktop from Claude Code via MCP — screenshot, mouse, keyboard, SSH, file transfer. For GUI work SSH can't reach on a remote machine; the remote PC approves each connection. Not Remote Control of your own Claude session.

Documentation

MCP: Control FlashDesk from your AI tools

FlashDesk implements MCP (Model Context Protocol), an open standard for connecting AI tools to external applications. AI tools such as Claude, ChatGPT, Cursor, and Windsurf can view the screen, control the mouse and keyboard, transfer files, and run SSH commands on a remote device through natural language.

Overview

MCP (Model Context Protocol) is an open standard that lets AI tools call into external applications directly, without custom scripting or a dedicated integration. Any MCP-compatible AI tool running on the same PC as FlashDesk can register FlashDesk as a local MCP server and use it right away.

Important: MCP support is off by default and must be enabled in FlashDesk settings on the device the AI tool runs on. The remote screen window is shown normally during an MCP-driven session, not hidden.

What you can do

  • List saved connections and check connection status.
  • Get a live screenshot of the remote screen.
  • Move the mouse, click, scroll, and type on the remote device.
  • Read and set the clipboard.
  • List, upload, and download files and folders.
  • Run SSH commands on the remote device.
  • Start, stop, and check the status of screen recording.

Supported AI tools

FlashDesk works with any MCP-compatible AI tool, including:

  • Claude Desktop and Claude Code
  • ChatGPT desktop app and Codex CLI
  • Cursor
  • Windsurf
  • VS Code with GitHub Copilot Chat

Each tool has its own place to register a local MCP server — typically a settings file or a CLI command. Web-only AI chat interfaces generally support remote MCP servers only, not a local one like FlashDesk's; use the corresponding desktop app or CLI instead.

How it works

ItemDescription
--mcp-serverThe flag that starts FlashDesk as a local MCP server. This process only bridges requests to FlashDesk; it never becomes a Host or a Viewer by itself.
Local onlyThe MCP server communicates over local standard input/output. It is never exposed to the network.

Operational notes

  • MCP support is off by default and must be enabled on the device the AI tool runs on.
  • The remote screen window is shown normally during an MCP-driven session, the same as a normal connection.
  • File transfer and SSH command execution performed through MCP are not confirmed individually. Consider what you want to allow an AI tool to do before enabling MCP.
  • SSH commands run through MCP require the destination device's SSH key to already be saved on the device the AI tool runs on.