Filaxis
Related Servers
Alternatives to Filaxis
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to control real interactive shells, REPLs, and TUIs over stdio, supervise other agents, surface approval prompts, and verify outcomes without auto-approving or mistaking timeouts for success.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to keep persistent shell sessions open across turns—running tests, tailing logs, driving REPLs and holding SSH connections—alongside text-file tools, all bounded by person-controlled folder limits and a command blocklist. Runs locally on macOS, Linux and Windows with no telemetry or remote calls.Apache 2.0
- AlicenseAqualityBmaintenanceStateful, structured, safe shell sessions for AI agents, on real infrastructure.713Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to remotely execute shell commands and transfer files on SSH hosts, including jump-host tunneling, background tasks, resumable transfers, and optional approval of destructive commands, while SSH credentials remain in the local process. It runs over stdio or a streamable HTTP daemon and supports auditing, allow/deny lists, and multiple authentication methods.ISC
- AlicenseNot gradedqualityBmaintenanceEnables AI agents or human operators to spawn, monitor, drive, and hook into child terminal sessions—such as CLI tools, interactive shells, and polyglot runtimes—via POSIX pseudo-terminals, providing multiplexed control, event interception, and memory-bounded observability for orchestration.GPL 3.0
- AlicenseAqualityBmaintenanceEnables AI assistants to spawn and control persistent local shells, SSH sessions, REPLs, debuggers, and serial/UART devices with zero-loss output capture, timestamped history, and atomic expect matching for command execution and prompt synchronization.12MIT
TDQS
Scored across 15 tools
The execution-oriented tools (run_command, run_batch, spawn_and_observe, observe_stream) overlap conceptually, but their descriptions explicitly cross-reference each other and define crisp boundaries (one-shot vs batch vs background-with-readiness vs live tail). The stream family (observe_stream/read_stream/close_stream) and file family (read/edit/put/get) are cleanly separated. The only residual confusion is choosing between spawn_and_observe and observe_stream, which requires reading the fine print.
Every tool follows a snake_case verb_noun pattern (run_command, read_file, edit_file, put_file, get_file, push_ssh, list_layers, remove_layer). Compound verbs like spawn_and_observe and stop_and_verify are a minor stylistic variation but still fit the same convention. The get/put vs read/write vocabulary is used coherently per family.
15 tools map onto four coherent sub-domains: execution (4), files (4), streaming (3), and layers (4). Each tool serves a distinct role in one of these workflows, and the count sits within the well-scoped range for a remote shell/execution platform.
Core CRUD and lifecycle are covered: exec (run_command/run_batch), background lifecycle (spawn_and_observe/stop_and_verify), streaming (observe/read/close), files (read/edit/put/get), and layers (push_ssh/push_into/list/remove). Gaps remain: no directory-listing tool, no file delete, and no way to pop/switch back to a prior layer as default. These are largely workaroundable via run_command (ls/rm) or remove_layer, so coverage is strong but not complete.