ReMCP
Related Servers
Alternatives to ReMCP
- AlicenseNot gradedqualityAmaintenanceEnables cloud agents to securely operate local machine resources (files, commands, screenshots) via standard MCP protocol.MIT
Related Servers
- 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 npm21GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityCmaintenanceEnables remote command execution and SFTP file upload or download from any MCP client without a local SSH client, SCP, or PuTTY installed. Supports password or private key authentication with SHA256 host fingerprint verification, timeouts, output limits, and multiple configured server instances.590 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to safely access user-local filesystems, apply validated patches, inspect git state, and run persistent jobs on outbound-connected local runners through a stateless Cloudflare control plane.8-
- AlicenseNot gradedqualityBmaintenanceEnables a remote MCP client to access narrowly scoped local filesystem resources and process capabilities through a loopback-only bridge. Supports guarded file reads, searches, and mutations, authenticated transport, and private reachability via OpenAI Secure MCP Tunnel.1AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceConnects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.2MIT
TDQS
Scored across 7 tools
Each tool covers a distinct domain—UI control, filesystem, terminal sessions, pixel capture, system/runtime state, structured documents, and plain-text reads—and the descriptions explicitly cross-reference one another to resolve edge cases. The few adjacent tools (read_file vs. manage_files, view_image vs. control_computer) have clear usage guidance that prevents misselection.
All seven tool names follow the same verb_noun snake_case convention: control_computer, manage_files, run_terminal, view_image, manage_system, manage_documents, read_file. There are no mixed casing styles, vague single-word verbs, or unpredictable patterns.
Seven tools is a well-scoped size for a computer-automation server; each tool maps to a major capability area without bloat. Even the specialized read_file and view_image tools serve frequent standalone tasks and earn their place.
The set covers the core lifecycle of local computer interaction: UI observation/control, file operations, terminal sessions, system state, structured document editing, and pixel capture. No obvious dead ends or missing major operations are apparent for the stated scope.