Suggests a terminal command based on the user's request

Executes a terminal command and captures its output. Preferred for quick commands (ls, git status, cat, echo, etc.) that don't need a visible terminal tab. Use open_terminal_tab only for long-running processes.

Executes a command and automatically waits for and returns its output. Preferred for quick commands that don't need a visible terminal tab. Use open_terminal_tab only for long-running processes like builds or servers.

Preview a command without executing it

Retrieve the output of a previously executed command

Execute a pipeline of commands with conditional logic (stop/continue/warn on failure)

Execute a command with real-time output streaming - ideal for long-running builds

Save a command template with variables for reuse

Execute a saved command template with variable substitution

List all saved command templates

Delete a saved command template by name

List recent commands from history with status, duration, and exit codes

Run health check on configuration, database, terminal, and recent error rates

Copy text to the macOS system clipboard

Read the current contents of the macOS system clipboard

Toggle macOS notification preferences for command completion alerts

Get current terminal environment context including git branch, active venv, node version, docker status, and working directory

Execute a command and return structured parsed output (supports git status, git log, docker ps, test results, ls -la, and JSON)

Capture a snapshot of the current shell environment variables with a named label

Compare two environment snapshots and show additions, removals, and changes

Save current project context as a named workspace profile (directory, commands, env vars, terminal preference). Optionally also writes a Warp-native launch config to ~/.warp/launch_configurations/ so the profile appears in Warp's launch UI.

Load a saved workspace profile to restore project context

List all saved workspace profiles

Delete a saved workspace profile

Open a new named terminal tab. ONLY use for long-running commands that need their own visible tab (builds, installs, servers, cloning repos). For quick commands, prefer execute_command or execute_with_auto_retrieve instead. If a session already exists, use send_to_session to reuse it.

Send a command to an existing named terminal session, reusing its tab. Always prefer this over opening a new tab when a relevant session already exists. Use list_sessions first to check for available sessions.

List all active terminal sessions. Check this before opening new tabs to avoid creating duplicates. Reuse existing sessions with send_to_session whenever possible.

Close a named terminal session and optionally close its tab. Use to clean up sessions that are no longer needed. Pass close_tab: true to also close the terminal tab.

Remove stale terminal sessions that have been inactive. Use periodically to clean up accumulated tabs. Sessions inactive longer than inactive_minutes (default: 30) are removed. Set close_tabs to true to also close the terminal tabs.

Set up a file system watcher that triggers a command when files change

Remove an active file system watcher

List all active file system watchers

Execute a command on a remote host via SSH (key-based authentication only)

Save an SSH connection profile for quick reuse

List all saved SSH connection profiles

Delete a saved SSH connection profile

Check if a command is interactive (requires TTY/stdin) before executing it. Returns safety level: safe, cautious, interactive, or blocked with suggestions for non-interactive alternatives

Focus an existing Warp pane by its session UUID via warp://session/. The UUID must be one Warp itself recognises (typically obtained from the optional shell shim's OSC 777 session_start event). Locally-minted UUIDs returned by open_terminal_tab are NOT valid here.

Build a printf invocation that emits an OSC 777 warp://cli-agent JSON event into Warp's notification UI. The returned printf must be executed inside a Warp pane (e.g. via execute_command) to take effect — our MCP stdout is the JSON-RPC channel and cannot directly write to Warp's PTY.

Report the status of the optional shell shim — socket path, whether the MCP server is listening, total events received, and the most recent events. The shim is opt-in (helper/install-shim.sh); when active inside a Warp pane it streams preexec/command_finished events to the MCP via a per-uid Unix socket. Observability surface in v6.0; execute_command auto-routing through shim events is deferred to v6.0.x.