ChatToComputerMCP
Supports Cloudflare Tunnel as an alternative connection provider on macOS, exposing the local MCP server to cloud AI clients without a public inbound port.
Provides Git capabilities within approved local workspaces, enabling repository inspection and Git workflows alongside file search, editing, and terminal commands.
Connects ChatGPT to approved local workspaces through OpenAI Secure MCP Tunnel, allowing ChatGPT to discover workspaces and invoke scoped file, Git, and command tools.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
⭐ If this project helps you, a GitHub Star helps more developers discover it.
📑 Contents
Related MCP server: gpt-web-agent
💡 About
ChatGPT can plan a task in the cloud—but how does it actually work on your Mac or Windows computer? ChatToComputerMCP closes that gap. It is a free, open-source local-computer MCP bridge built for cloud-based AI chat conversations, especially ChatGPT, and other compatible MCP clients such as Claude.
Instead of needing a separate paid computer-access plugin for common development workflows, connect ChatToComputerMCP and let your AI chat inspect and edit approved local files, search code, use Git, and (when you opt in) run terminal commands. For these workflows, it is an open-source alternative to the paid Remote Desktop Commander connector. It is not a feature-for-feature replacement for its entire desktop-control or system-management toolset, nor an official ChatGPT plugin.
Designed for multiple conversations, not just one: approve multiple independent workspaces and allow 4–16 simultaneous command jobs (default 8), with per-directory conflict protection and targeted task cancellation. This is bounded command concurrency—not unlimited parallelism, complete per-client identity isolation, or a remote GUI desktop.
ChatToComputerMCP runs locally on your own computer. It is not an AI model, a hosted computer, or an IDE replacement.
ChatGPT / Claude / another compatible MCP client
│ authenticated tunnel
▼
ChatToComputerMCP
macOS / Windows GUI
│
approved folders
┌──────────┼──────────┐
▼ ▼ ▼
Repo A Repo B Project C
scoped local tools and command sessionsThe user approves which folders exist as workspaces. MCP clients cannot grant themselves new directory access. The path guard is application-level containment, not a shell sandbox.
✨ At a glance
Capability | What it does |
Paid-plugin alternative | Use ChatGPT or another compatible cloud AI chat with your own open-source local tools for common file, Git and shell workflows—without a separate paid computer-access plugin. |
Multiple workspaces | One default workspace plus up to 12 user-approved, named, non-overlapping roots. |
Scoped MCP operations |
|
Concurrent commands | One shared configurable 4–16 command budget (default 8); overlapping cwd trees are rejected. |
Task controls | Command IDs, bounded output, status and targeted cancellation. |
Native GUI | Mac: Overview, Workspaces, Connection, Tasks, Activity. Windows: connection, workspace and task management. |
Connection providers | OpenAI Secure MCP Tunnel on Mac/Windows; Cloudflare alternative on Mac. |
Local installation | npm ships native source and pinned vendor binaries; installation compiles locally. |
Optional background mode | macOS login LaunchAgent, crash recovery, optional always-on and explicit auto-connect. |
🚀 Quick start
1. Install from npm
Requires Node.js 20+ and macOS with Xcode Command Line Tools/Swift or Windows with .NET 8 SDK and Windows PowerShell.
npx --yes chat-to-computer-mcp@latest installThis builds and installs locally. It does not start a service, enable shell access or replace an existing FileMCP installation.
2. Open the desktop app
npx --yes chat-to-computer-mcp@latest open3. Approve a workspace and connect
Use the desktop Workspaces page to select a default directory, add approved folders and review tool permissions. Next follow Connect ChatGPT with Secure MCP Tunnel to create a Tunnel ID and runtime key, connect the app, and add the server in ChatGPT.
4. Work from your AI chat
For example: “Show my approved workspaces, open the second repository and investigate its failing tests.” The connected client can then use the scoped tools you approved.
Installing the app does not secretly configure ChatGPT, Claude or other third-party clients. MCP connector availability and authorization depend on the individual client.
🔌 Connect ChatGPT with Secure MCP Tunnel
This is the recommended connection path for ChatGPT. ChatToComputerMCP runs the private MCP server locally and bundles tunnel-client, so you do not need to open a public inbound port or install a second tunnel process.
Create a Tunnel: In OpenAI Platform → Tunnel settings, create/reuse a Secure MCP Tunnel and associate it with the ChatGPT workspace where you will use it. Copy the
tunnel_…ID. Creating requires Tunnels Read + Manage.Create a restricted runtime API key: Use the OpenAI Platform, not your ChatGPT subscription, to create a key with Tunnels Read + Use. Your ChatGPT workspace must independently allow custom MCP Plugins. Keep this API key private.
Connect the native app: In ChatToComputerMCP Connection, choose OpenAI Secure MCP Tunnel, enter the Tunnel ID and Runtime API key, then Save connection → Connect. Wait for Connected. The app securely stores the key in the OS credential store and manages the bundled tunnel client itself.
Add it in ChatGPT: Open ChatGPT Plugins → + → Add custom MCP server, select Connection: Tunnel and choose/paste the same Tunnel ID. Review the authentication/risk warnings, create the Plugin, and verify its discovered tools.
Test a tool call: Start a new ChatGPT chat, select the Plugin with
@and ask it to list the files in your approved default workspace without modifying them. Check that Activity in the local app records the actual call.
Important: Do not paste http://127.0.0.1:8008/mcp into ChatGPT for the Tunnel route—it is only the local server address. If your Tunnel is missing from ChatGPT, check its ChatGPT workspace association and your Tunnels Read + Use role.
Full illustrated-by-steps guides: English connection guide · 中文连接教程. The full guides cover permissions, Platform vs ChatGPT accounts, Cloudflare Tunnel (macOS), OAuth and troubleshooting. Official references: OpenAI Secure MCP Tunnel and Connect an MCP Plugin in ChatGPT.
📦 Installation and CLI
# Persistent global CLI (optional)
npm install -g chat-to-computer-mcp
chat-to-computer-mcp install
chat-to-computer-mcp open
chat-to-computer-mcp statusCommand | Purpose |
| Build into a versioned per-user app directory. |
| Build again after the installed app exits; keep the previous version as backup. |
| Open the installed native app. |
| Show installed app path and, on Mac, LaunchAgent status. |
| Mac: optional login launch and abnormal-exit recovery. |
| Mac: relaunch even after normal Quit (explicit opt-in). |
| Mac: connect the tunnel on login if no conflicting legacy service is active. |
| Mac: disable only the new independent service. |
Optional macOS keep-alive
chat-to-computer-mcp launchagent enable
chat-to-computer-mcp launchagent status
chat-to-computer-mcp launchagent disableThis is a per-user login agent, not a system daemon available before login. Auto-connect is off by default. The Mac GUI also offers next-login options without restarting another running app. See Install guide.
🗂 Workspace workflow
Select the default workspace (direct MCP tools remain scoped to it).
Use Add folders… to approve extra existing directories; names and IDs persist.
Review shell, Git push and other privileged permissions before saving.
Set a global 4–16 concurrent-command limit shared by all workspaces.
Save changes and reconnect before newly granted/revoked permissions take effect.
Inspect jobs and cancel only the selected long-running session under Tasks.
Removing a workspace does not delete its files. Parent/child workspace overlaps and canonical symlink aliases are refused. See Multi-workspace permissions.
🖥 Desktop experience
Page | Key controls |
Overview | Connection summary, active workspace and permissions |
Workspaces | Add, rename, remove and reveal folders; command capacity; privileged tools; optional login agent |
Connection | Tunnel provider, endpoint and credentials, connect/disconnect and OAuth actions |
Tasks | Running command sessions, workspace context, refresh and targeted cancellation |
Activity | Redacted logs, copy, clear and connection diagnostics |
The Windows client provides its own native WPF settings and task controls; its actual Windows GUI execution remains a separate release test, not a result inferred from Mac compilation.
🧭 Architecture
A loopback-only MCP server exposes approved tools.
The outbound tunnel connects supported remote clients to the local endpoint.
Each workspace has a canonicalizing resolver and mutation controls.
A shared command-admission budget counts asynchronous and synchronous jobs.
Commands run with the user's OS privileges; cwd collision checks do not confine absolute paths.
Sessions expose IDs, bounded output and target-specific cancellation.
This version does not yet provide cryptographically verified per-conversation identity or durable subprocess reattachment across an application crash. The current Mac development build records private durable request-ID receipts to prevent replay after restart; an interrupted receipt requires checking actual effects, NOT assuming the process resumed. Both identity and true reattachment remain roadmap items.
🔧 MCP tool examples
Discover user-approved workspaces:
{"name":"list_workspaces","arguments":{}}Operate in a separately approved workspace:
{
"name":"workspace_call",
"arguments":{
"workspace_id":"approved-workspace-id",
"tool_name":"read_file",
"arguments":{"relative_path":"README.md"}
}
}Ordinary read_file, grep, git_status and other direct calls continue to operate in the default workspace. Clients cannot create a new scope through MCP.
🔒 Permissions and security
Shell execution is disabled unless opted in and inherits the user's OS access.
Folder containment covers normal tool operations, not arbitrary shell commands.
API keys belong in macOS Keychain or Windows Credential Manager, not npm or the repo.
Installing does not touch the old
local.filemcpservice, credentials, proxy or tunnel.Per-client authenticated identities and durable task recovery remain future work.
Locally compiled Mac apps are not automatically Apple Developer ID signed or notarized.
Read SECURITY.md and Architecture before enabling commands for less-trusted clients.
🧪 Platform verification
Check | macOS | Windows |
Native source build | Passed | Windows x64 runner build passed |
Multiple workspaces | Scoped tests passed | Windows x64 integration passed |
Command capacity/cancel | 8/12/16 and MCP regressions passed | Windows x64 integration passed |
Native GUI | 150 layout-state checks passed | Windows x64 WPF smoke passed |
npm tarball → installed app | Clean-HOME local Swift build passed | Clean Windows install pending |
The Windows x64 CI actually ran on a GitHub-hosted Windows runner. ARM64 packages were built but not run on native ARM64 hardware; device-specific upgrade and restart acceptance remains unverified at the owner's direction. The current roadmap lists the remaining release gates.
🛠 Build and test
# macOS source tree
bash build_macos_app.sh
bash tests/test_swift_ui.sh
bash tests/test_swift_workspace_scope.sh
bash tests/test_swift_agent_tools.sh
bash tests/test_swift_runtime.sh
# Installer/package
npm test
npm pack --dry-run --jsonWindows: build windows/FileMCP.Windows.sln with .NET 8, then execute the native Windows runtime and GUI tests on Windows.
Automated future npm releases use GitHub Actions OIDC trusted publishing, without long-lived publish tokens.
🔗 Related projects
From the same maintainer, these are complementary—not automatically integrated—developer tools:
iterate-skill — iterative AI code review and fixes in coding assistants.
iterate-harness — the headless iterate review and verification engine.
iterate-plugin — iterate dashboards and controls in the dsh client.
GlassPane — separate macOS runtime UI verification.
ChatToComputerMCP gives compatible AI conversations an approved local execution path; it is not a component of the iterate review loop and does not claim a shared runtime or configuration.
❓ FAQ
Does it replace ChatGPT or Claude? No. It offers local tools to a compatible MCP client.
Can it replace the paid Remote Desktop Commander connector? For common local file management, code search, Git and opt-in command workflows, it can be a free, open-source alternative. It does not promise every Remote Desktop Commander feature, identical UI controls or the same client integrations. Some cloud MCP services may have their own charges.
Can multiple AI chats run commands at once? Yes, in disjoint working directories within the shared limit. This is not complete isolation from the host OS.
Can I use it after restarting my Mac? Optionally, a macOS LaunchAgent starts it at user login. It is not a pre-login system daemon.
Is the Windows version fully verified? Windows projects compile with a Windows-targeting SDK; real-device tests are still pending.
Does installation change my existing FileMCP? No. The new app is independent, and conflicting auto-connect is blocked.
📚 Documentation
Guide | Focus |
Tunnel setup, Platform API key, ChatGPT Plugins and verification | |
System requirements, CLI, background service | |
Client, tunnel, host runtime and workspace scopes | |
Permission and path guarantees | |
Native controls | |
npm OIDC, version tags and release procedure | |
Build, connection and permissions | |
Verified vs outstanding | |
Legacy compatibility and safe rollback | |
FileMCP source lineage |
🤝 Contributing and license
Contributions are welcome. Read CONTRIBUTING.md, keep changes reviewable and run platform-appropriate tests. Submit sensitive security issues privately as instructed in SECURITY.md.
ChatToComputerMCP is derived from anhnv02/file-mcp and retains applicable copyright, source notices and the Apache License 2.0.
Independent community project. Not affiliated with or endorsed by OpenAI, Anthropic or the original FileMCP maintainers.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Use your own Windows, Mac or Linux computer from ChatGPT, Claude, Cursor or Gemini CLI: run commands, read, write and search files, run long processes. Your computer only makes an outgoing connection (no open ports or VPN). Read-only mode, allowed folders, blocked commands and an action log keep you in control. Free plan available.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables remote AI agents to read, patch, and (opt-in) execute commands in a local workspace, with all actions approved locally and fully audited.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables a browser-based AI assistant to read code, edit files, run tests, inspect failures, and keep task checkpoints on a local project.24 npmMIT

Flyto2 Runtimeofficial
AlicenseNot gradedqualityBmaintenanceGives ChatGPT secure access to your local machine over MCP, letting it read and edit files, run commands, tests, and Git within approved workspaces.1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI chatbots to act like coding agents on your own computer by executing code, editing files, running terminal commands, and performing Git operations through a secure cloud bridge. Supports token-based pairing, path sandboxing, and configurable approval for destructive actions.MIT