FlowDeck exposes its user-facing tools as an MCP server. flowdeck mcp lets you call those tools directly from the command line, which is how agent hosts that cannot hold a long-lived MCP connection (such as Cursor’s direct client) invoke FlowDeck’s blocking tools through a single foreground command.
flowdeck mcp call
Call a FlowDeck MCP tool by name and pass its arguments as a JSON object. The tool runs against the same active FlowDeck MCP server the app exposes, and the result is printed to stdout.
Options
When to use it
- Blocking tools:
flowdeck_ask_user and flowdeck_plan block until the user responds. From agent hosts whose direct MCP client has a short deadline, call them through flowdeck mcp call <tool> --json '<args>' as a single foreground command so the call can wait for a real human response.
- Task and worktree tools:
flowdeck_update_tasks, flowdeck_worktree_list, flowdeck_worktree_create, and flowdeck_worktree_delete can be invoked the same way when a host does not expose them as direct tools.
flowdeck mcp call is the required transport for flowdeck_ask_user and flowdeck_plan from agent hosts that cannot hold a long-lived MCP connection. Do not attempt a direct MCP call for either tool from such hosts.
