ai-remote
Related Servers
Alternatives to ai-remote
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocalBridge 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 gradedqualityCmaintenanceEnables 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-
- AlicenseNot gradedqualityCmaintenanceControl another PC's desktop from Claude Code via MCP — screenshot, mouse, keyboard, SSH, file transfer. For GUI work SSH can't reach on a remote machine; the remote PC approves each connection. Not Remote Control of your own Claude session.MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP gateway that gives an AI client control of a real headed Chromium desktop and persistent workspace, with file, shell, process, and code-editing tools routed through a single control lease. Includes server-side read-only observation, server-enforced human takeover, and pause/stop controls so a person can watch, intervene, and hand control back.5Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables controlling your own Linux desktop machines from any MCP-capable LLM client, with opt-in agent capabilities for shell, filesystem, processes, screenshots, system info, and input injection.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to securely connect to a paired Windows machine through a self-hosted Cloudflare relay and use its local filesystem and command-execution tools over Streamable HTTP and WebSocket.78 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.