The pieces that separate this from "run a shell command" are the operational ones: `check_interactive` catches commands that need a TTY before they block, environment snapshots let you diff what a script actually changed, and streaming keeps long builds visible. The setup cost is real and macOS-specific — signing is not optional if you want execution to work.
Warp Command Runner is an MCP server that gives any MCP client a real terminal: execute commands, chain them into pipelines, stream long builds, save reusable templates, watch files, and reach remote hosts over SSH. One binary, any client — the extra value shows up when Warp is your terminal.
- Core execution — `execute_command`, `execute_with_auto_retrieve` for the common case, `execute_pipeline` for chained steps with failure modes, `execute_with_streaming` for long builds, plus `get_command_output`, `preview_command`, `suggest_command`, `list_recent_commands` and `self_check`
- Templates — `save_template`, `run_template` with variables, `list_templates`, `delete_template`
- Environment intelligence — `get_environment_context` probes git, venv, Node and Docker state; `execute_and_parse` returns structured JSON; `capture_environment` and `diff_environment` snapshot and compare your real shell environment
- Workspace profiles — `save_workspace_profile`, `load_workspace_profile`, `list_workspace_profiles`, `delete_workspace_profile`
- Sessions and safety — `open_terminal_tab`, `send_to_session`, `list_sessions`, `close_session`, `cleanup_sessions`, and `check_interactive`, which classifies a command for TTY needs before it hangs on `vim` or `psql`
- File watching and remote — `add_file_watch`, `remove_file_watch`, `list_file_watches`, `ssh_execute`, `save_ssh_profile`, `list_ssh_profiles`, `delete_ssh_profile`
- Clipboard and Warp integration — `copy_to_clipboard`, `read_from_clipboard`, `set_notification_preference`, `focus_warp_session`, `emit_warp_event`, `shell_shim_status`
macOS, and a build signed with your own code-signing identity — the five keystroke-routing tools including `execute_command` only work from a signed bundle, and `build.sh` auto-detects a single Apple Development or Developer ID identity. Find yours with `security find-identity -v -p codesigning`. Upgrading matters here too: rebuild with the same identity, or macOS treats it as a new app, your TCC grants stop applying, and `execute_command` returns error 1002. Register it in Warp's `~/.warp/.mcp.json`, Claude Desktop's config, or any other MCP client's settings.
Build from source — clone the repository and build it, then point your client at the binary