FreeRemoteDesktop
Related Servers
Alternatives to FreeRemoteDesktop
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that enables AI-assisted coding through workspace-scoped tools for file reading/editing, command execution, jobs, Git, LSP, media, browser, and desktop workflows. It enforces OAuth, workspace ACL, trust policies, and file/secret guards so owners can safely grant inspect, edit, or trusted capabilities.559 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables web-based AI chat clients and local IDEs to securely operate a user's own machine through an OAuth-gated MCP endpoint, covering file read/write/edit, whitelisted shell execution, search, read-only Git, SQLite, browser automation, DevTools debugging, background tasks, localhost fetching, ports, clipboard, notifications, and Postman control. Its 38 tools are governed by configurable allowed folders, a strict command whitelist, rate limits, and caller blocking, so remote AI assistants get scoped access without unrestricted shell privileges.-
- AlicenseNot gradedqualityAmaintenanceEnables web-based AI clients like Claude, ChatGPT, and Grok to securely operate a local machine through an OAuth-gated MCP endpoint, covering files, shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, ports, clipboard, notifications, and Postman. Exposes 38 governed tools with a strict command whitelist, folder allowlisting, and rate limiting so browser chats can build projects, inspect databases and local APIs, and manage long-running jobs without granting unrestricted shell access.MIT
- AlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 OAuth-gated tools over one MCP endpoint, letting web-based AI chat clients read and edit files, run whitelisted shell commands, search, and use Git, SQLite, browser automation, DevTools, background tasks, ports, clipboard, notifications, and localhost services on the user's own machine. It also allows local IDEs and automation tools to connect directly over localhost for offline, low-latency access.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Windows users to securely bridge compatible cloud LLM MCP services to local applications, allowing discovery and per-app authorization so approved desktop apps can be started or closed via MCP tool calls. It blocks high-risk system tools and stores connection tokens with Windows DPAPI encryption.6Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to securely operate on a local workstation through MCP by exposing file, shell, and workspace management tools.10MIT
TDQS
Scored across 19 tools
Most tools target clearly distinct resources or capability areas: jobs, filesystem, command execution, GUI, and browser. The main possible confusion is read_text_file versus read_lines, and to a lesser extent capture_screen versus browser_screenshot, but their descriptions make the contexts reasonably clear.
Names are predominantly snake_case and action-oriented, with clear namespaced prefixes for GUI and browser operations. Minor deviations such as job_history and desktop_status use noun-first phrasing, but the overall convention remains readable and predictable.
Nineteen tools is somewhat large, but the server covers several distinct capability families: jobs, filesystem, command execution, desktop GUI, and browser automation. Each tool appears to earn its place within those areas rather than being redundant bloat.
The surface covers core workflows for file reading/writing/listing/searching, command execution, job running/history, screen capture, GUI input, and browser interaction. Some gaps exist, such as no explicit file delete/move operations and limited browser navigation/history controls, but agents can generally work around them or the omissions are consistent with the safety-first design.