Remote Terminal MCP

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.

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

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: Original command - result_output: Command output - has_errors: Boolean from output analysis - error_context: Error details if has_errors=true - backup_file_path: Backup location if file was modified - status: 'executed' or 'undone'

Get the currently connected server information

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

Get detailed information about a remote file or directory

Check the connection status of the remote terminal

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

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 - Auditing command execution - Analyzing errors across multiple sessions Returns database records with integer IDs, command text, execution status, timestamps, error information, and conversation context when available. By default, shows commands from the currently connected server.

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', 'rolled_back' - limit: Max number to return (default 50)

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

List contents of a remote directory

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.

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.

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.

Remove a server configuration

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: Confirmation message

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.

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 conversation [ID]" - Start new conversation: "start new conversation for [goal]" - Run without conversation: "run commands without conversation" 3. Wait for user's explicit choice 4. Execute the choice (start_conversation, resume_conversation, or set no-conversation mode) 5. After user choice, ALL …

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 which server is currently marked as default.

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 already in progress on this server, returns warning - Use force=true to create new conversation anyway - Otherwise, resume existing conversation or end it first USAGE: - Start conversation before executing related commands - All subsequent execute_command calls with conversation_id use this conversation…

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')

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 remain unchanged - Preserves: recipe ID, created_at, times_used, last_used_at - Updates: any fields you provide IMPORTANT: This modifies the recipe in-place. The old version is not saved. If you want to keep both versions, use create_recipe_from_commands instead.

Update an existing server configuration

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

Upload a file from local machine to remote server via SFTP