ai-remote
Related Servers
Alternatives to ai-remote
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceSelf-hostable remote terminal assistance over MCP. Agents create one-command connection invitations, execute commands, and manage interactive sessions on user-authorized macOS, Linux, and Windows computers without requiring an SSH daemon.7102Apache 2.0
- AlicenseAqualityBmaintenanceLocalBridge MCP is a bridge between an online AI chats and your computer. Most online AI chats can reason, and write code, but they normally cannot touch the local files, terminals, and scripts that make real work happen. This gives a trusted assistant a controlled doorway into a machine you own, so it can inspect files, edit text, search a project, run tests, use Git, and operate a shell.173Apache 2.0
- FlicenseNot gradedqualityBmaintenanceP2P dev-machine MCP for phone-driven coding agents: hot reload, builds, deploys.5-
- AlicenseNot gradedqualityBmaintenanceEnables remote control of a Windows, Linux, or macOS computer directly from an AI chat client over a self-hosted MCP endpoint, providing file management, terminal command execution, and system status monitoring through a relay-and-agent architecture secured by OAuth and device pairing.38 npmISC
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to securely control a remote Windows/Linux PC via MCP and REST, executing shell commands and driving coding-agent CLIs like Claude, Cursor, and Codex.1-
- 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.151,428 npm1MIT
This server cannot be deployed
TDQS
Scored across 2 tools
The tools are mostly distinct: list_hosts is read-only discovery, while use_host changes session default. There is some overlap because use_host also returns system_info, but the purposes remain separable.
Both tools follow a clear verb_noun snake_case pattern: list_hosts and use_host. The convention is consistent and predictable.
Two tools is too thin for a remote-host management server. A useful surface would likely include commands to connect, execute, inspect, or manage host pairings.
The surface only supports listing hosts and setting a default. There is no way to execute commands on a host, pair/unpair hosts, disconnect, or perform the apparent core remote operations, leaving significant dead ends.