Remote Terminal

Route tool calls to appropriate module

List batch scripts saved in database. Browse saved scripts with filtering and sorting options. Use this to find scripts to reuse or manage.

Get batch script details and content by ID. Returns complete script information including source code. Use this to view a script before executing or editing it.

Save a batch script to database (without executing). Saves script for later reuse. Automatically deduplicates based on content hash. Does NOT execute the script - use execute_script_content_by_id to run it.

Execute a saved batch script by ID. Loads script from database and executes it on the remote server. Increments usage counter and tracks execution in batch_executions table.

Delete a batch script from database (requires confirmation). First call without confirm shows script details and warning. Second call with confirm=true actually deletes. This is a hard delete - execution history is preserved but script content is lost.

Helper tool to create a batch (shell) script from command list. Useful for AI to quickly build properly formatted scripts. Example: commands = [ {"description": "Network interfaces", "command": "ip link show"}, {"description": "Routing table", "command": "ip route show"}, {"description…

Check status of a long-running command. OUTPUT_MODE: Same options as execute_command - "auto": Smart decision based on output size - "full": Get complete output (for completed commands) - "preview": Peek at first/last lines - "summary": Ju…

Get full unfiltered output of a command. WARNING: Uses more tokens than filtered output.

Send Ctrl+C to a running command. Use when user wants to stop a long-running command.

List tracked commands from current session with status. Shows commands in CommandRegistry (in-memory, max 50). Useful for checking what's currently running or was recently executed in this session. For historical commands from database, use list_command_history instead.

List command execution history from database with flexible filters. Query persistent command history across all servers and sessions. Useful for: - Reviewing what commands were executed on a server - Finding commands from specific dates or time periods - Debugging by examining command history - Aud…

Start a new command conversation to track related commands. A conversation groups commands by goal (e.g., "configure wifi", "install docker"). This enables rollback of entire workflows and recipe creation from successful sequences. IMPORTANT - ACTIVE CONVERSATION DETECTION: - If conversation alrea…

Resume a paused conversation. Use this when: - New Claude dialog started and previous conversation still in progress - Switched back to server with paused conversation - Want to continue previous work RETURNS: - conversation_id: Resumed conversation ID - goal: Original goal summary - message: Conf…

End a conversation and mark its final status. STATUS OPTIONS: - 'success': Goal achieved successfully - 'failed': Goal not achieved - 'rolled_back': Commands were undone IMPORTANT: Status should be determined by USER feedback, not just command exit codes. A command can succeed technically but fail…

Get all commands from a conversation. USAGE FOR ROLLBACK: - Set reverse_order=true to get commands in undo sequence - Check has_errors and backup_file_path fields - Use this data to generate undo commands RETURNS: Array of command objects with: - id, sequence_num: Identification - command_text: Or…

List conversations with optional filters. Useful for: - Finding previous work on similar goals - Reviewing conversation history - Identifying successful patterns for recipes FILTERS: - server_identifier: Limit to specific server - status: Filter by 'in_progress', 'paused', 'success', 'failed', 'ro…

Update command status (for rollback tracking). Call this after undoing a command to mark it as 'undone'. This prevents re-attempting undo on already undone commands. USAGE: - Execute undo command via SSH - If successful, call update_command_status(command_id, 'undone')

Open the web terminal in a browser tab. If a terminal tab is already open, closes it and opens a fresh one. If the web server is not running, starts it first. Use this when the terminal tab has been lost or closed.

List all configured servers with their details. Shows server status markers: - [CURRENT]: Currently connected server - [DEFAULT]: Default server (auto-connects when no server specified) Returns: Server names, hosts, ports, users, descriptions, tags, and status markers.

Select and connect to a server by name, IP, or tag. ⚠️ CRITICAL CLAUDE WORKFLOW: When this tool returns 'open_conversations' in the response, Claude MUST: 1. STOP and present the information to the user 2. ASK the user to choose ONE of these options: - Resume specific conversation: "resume conve…

Add a new server configuration

Remove a server configuration

Update an existing server configuration

Get the currently connected server information

Set default server (shown in list_servers with [DEFAULT] marker). The default server is the preferred server for operations that don't specify a server. When you execute commands without an active connection, Claude will automatically connect to the default server. Note: Use list_servers to see wh…

Check the connection status of the remote terminal

Create a reusable recipe from a successful conversation. A recipe is a documented, reusable command sequence extracted from a successful conversation. Recipes can be executed later on any compatible server. USAGE: - Call after a conversation ends successfully - Provide clear name and description -…

List all available recipes. Useful for: - Browsing available automation recipes - Finding recipes for specific tasks - Reviewing recipe history RETURNS: List of recipes with: - id, name, description - command_count - times_used, last_used_at - created_at, created_by

Get detailed recipe information including command sequence. Use this to: - View complete recipe details - See exact command sequence - Check prerequisites and success criteria RETURNS: - Full recipe details - Complete command sequence - Usage statistics

Execute a saved recipe on current or specified server. Handles both shell commands and MCP tool calls automatically.

Delete a recipe (nard delete - not recoverable). USAGE: - First call without confirm=true to see recipe details - Second call with confirm=true to actually delete - Deleted recipes are hidden but preserved in database IMPORTANT: This requires confirmation to prevent accidental deletion.

Create a recipe from a command list (no conversation required). Use this to: - Build recipes manually without executing first - Create recipes from documentation - Combine commands from multiple sources COMMAND TYPES: 1. Shell: {"sequence": 1, "command": "ls -la", "description": "List"} 2. MCP: {"…

Update an existing recipe in-place (preserves ID and usage stats). Allows modifying any recipe fields while keeping the same recipe ID. Only updates fields you specify - all other fields remain unchanged. USAGE: - Specify recipe_id and any fields you want to update - Fields not specified will rema…

Upload a file from local machine to remote server via SFTP

Download a file from remote server to local machine via SFTP

List contents of a remote directory

Get detailed information about a remote file or directory

Smart directory upload with automatic compression and progress tracking. Automatically decides whether to use compression and background mode based on transfer characteristics.

Smart directory download with automatic compression and progress tracking. Automatically decides whether to use compression and background mode based on transfer characteristics.