warp-command-runner
Related Servers
Alternatives to warp-command-runner
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceThe terminal AI agents can drive: a cross-platform desktop terminal (macOS/Linux/Windows, MIT) that runs a local MCP server. Spawn tabs/panes, run commands with structured output, read screens and full scrollback, take scrolling screenshots, record sessions with secret redaction, switch identity profiles. Auto-registers with Claude Code / Codex / Gemini CLI on install.15-
- AlicenseAqualityCmaintenanceGives MCP-compatible AI agents a full local terminal over stdio, enabling shell command execution, file reads and writes, content search, background processes, and stateful tmux sessions with variable capture, auditing, and a configurable command denylist. Requires no deployment or cloud setup.15MIT
- AlicenseNot gradedqualityBmaintenanceLocal macOS MCP bridge that gives ChatGPT shell, unrestricted filesystem access, real PTY sessions, background jobs, and read-only stored Codex history. ChatGPT stays the reasoning layer; the bridge makes no model calls.55MIT
- AlicenseNot gradedqualityCmaintenanceEnables macOS users to securely connect AI assistants such as Notion AI, Claude, and Cursor to their local files and terminal through an MCP server protected by a Bearer token and Cloudflare Tunnel.MIT
- AlicenseNot gradedqualityDmaintenanceExposes an interactive terminal over MCP, enabling remote shell command execution, file operations, and directory management via ChatGPT or Claude Desktop.2MIT
- AlicenseAqualityCmaintenanceMCP server that gives AI agents real interactive terminal sessions for running REPLs, SSH, database clients, and any interactive CLI with clean text output and smart completion detection.787 npm20MIT
TDQS
Scored across 40 tools
Several execution tools heavily overlap: execute_command, execute_with_auto_retrieve, execute_and_parse, execute_with_streaming, and execute_pipeline all run commands, while get_command_output and auto-retrieve both fetch output. Descriptions provide some guidance, but an agent still faces unclear boundaries for choosing the right runner.
Most tools follow a predictable snake_case verb_noun pattern such as execute_command, list_templates, save_workspace_profile, and delete_ssh_profile. Minor deviations like ssh_execute, self_check, and shell_shim_status keep it from being fully consistent.
With 40 tools, the surface is heavy for a command-runner server and includes many niche capabilities beyond core command execution, such as clipboard access, notifications, Warp event emission, and shell-shim status. The set feels over-expanded rather than tightly scoped.
The surface covers command execution, output retrieval, templates, sessions, workspace profiles, SSH profiles, environment snapshots, file watches, and health checks. Minor gaps remain, such as no explicit template update/get operation and no obvious command cancellation/kill tool, but these are workable.