ReMCP
Related Servers
Alternatives to ReMCP
- AlicenseNot gradedqualityCmaintenanceEnables cloud agents to securely operate local machine resources (files, commands, screenshots) via standard MCP protocol.MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables remote MCP clients to access local MCP servers and command-line tools over the web, with user approval required for every connection.1MIT

KMJ CodeBridgeofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely access authorized computers and VPSs for scoped file operations, Git operations, and administrator-defined quality gates through an outbound-polling gateway.2Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to connect to a local workspace over a public tunnel and lets them run shell commands and transfer files bidirectionally.262 npm20GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely reach and invoke tools on self-hosted machines through a remote gateway, using outbound-only device connections, OAuth or bearer authentication, per-device policies, and audit logging.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to safely access selected local files and trusted executables with policy control, audit, and rollback via a Windows control center.Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP clients to access a local computer through a controlled, permission-based tool surface for read-only or developer-mode file, process, and terminal operations.6MIT
TDQS
Scored across 7 tools
Each tool description explicitly routes away from its nearest neighbors (read_file vs manage_documents, view_image vs control_computer, run_terminal vs manage_system), which is unusually good. However, real overlaps remain: read_file admits it still does 'legacy .docx/.pdf extraction', manage_files has read/search operations, and control_computer's screen recording overlaps view_image's capture, so an agent can still misselect in those seams.
All names are snake_case verb_noun and readable, but the verb set is mixed (manage_*, run_, control_, read_, view_), giving four different verb families across seven tools. The three manage_* siblings form a clean group while the remaining four each use a different verb, a minor inconsistency rather than a real problem.
Seven tools is well within the ideal range and each maps to a coherent capability domain (terminal, OS, GUI, documents, files, text, pixels). The multi-operation design is deliberate, with each tool exposing a closed operation schema rather than spawning dozens of narrow tools.
The surface covers shell, system/runtime, desktop GUI, office documents, filesystem, plain text, and pixels — essentially the full native-computer-control lifecycle, including writes, edits, and captures. Minor gaps remain: no explicit HTTP/web or network fetch capability, and image writing/encoding beyond capture is not evident.