AI Commander
Related Servers
Alternatives to AI Commander
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn all-in-one self-hosted remote MCP server and gateway that lets AI clients access filesystem, terminal, background processes, and computer-use tools, and multiplex local stdio MCP servers over Streamable HTTP on Linux, Jetson, macOS, and Windows. It bundles revocable API keys, OAuth 2.0, and a read-only/coding safety switch so cloud and desktop assistants can safely drive remote machines.15861 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to execute host terminal commands, manage files and workspaces, and automate browsers through authenticated Streamable HTTP and SSE connections with configurable sandboxing.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients and agents to execute commands in real interactive PTY sessions, manage host filesystem operations, and access 15 MCP tools via Stdio, SSE, or REST with secure API-key authentication.-
- AlicenseNot gradedqualityBmaintenanceEnables cloud AI agents to access local STDIO MCP servers and their tools through a single authenticated Streamable HTTP endpoint, optionally tunneled via ngrok.39 npm1MIT

2ools MCP Serverofficial
AlicenseAqualityCmaintenanceRemote MCP server for 2ools—build, version, review, and export websites, web apps, and games from the AI chat you already use. This repository includes a credential-free stdio proxy and Dockerfile that forward introspection to the verified remote endpoint without mocking tools.431MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to remotely dispatch AI agents and use file/system tools on an Omarchy VM over authenticated Streamable HTTP, replacing SSH-based pipelines.1MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: job lifecycle tools, file transfer, screenshot, status, and list. The main overlap is between remote_exec and remote_job_start, but their descriptions strongly differentiate short-lived vs. detached long-running work, so an agent should rarely misselect.
The remote_job_* family is perfectly consistent, and remote_pull/remote_push/remote_exec/remote_screenshot follow a clear remote_ prefix pattern. The exceptions are session_status and list_machines, which break the prefix convention but are still readable and predictable.
11 tools is well-scoped for a remote machine management server. Each tool covers a distinct operation: shell execution, job lifecycle, file transfer, screenshots, and machine discovery/status, with no obvious redundancy or bloat.
The job lifecycle is complete (start, list, status, logs, cancel), and file transfer covers both directions. Minor gaps exist, such as no remote filesystem browsing or direct machine management beyond status checks, but these are workaroundable via remote_exec and are not core dead ends.