Mac Developer Bridge MCP
An MCP bridge that lets ChatGPT operate your Mac: shell, files, terminal sessions, Codex history and background Chrome.
- 56 ★ on the repository
- Last commit
Broad access
Why this level
- The bridge runs with macOS user privileges and has no sandbox or command list: shell, any file, deletion.
- Chrome mode controls tabs with your signed-in sessions, and keys and credentials are reachable through the shell.
Install
- Works in
Manual install
git clone https://github.com/alexanderradahl/mac-developer-bridge.git && cd mac-developer-bridge && ./menubar/build.shThe README quick start builds the menu bar app, which you launch with Start and use to copy the ChatGPT setup. Workspaces can use `install.sh` instead.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The bridge runs with macOS user privileges and has no sandbox or command list: shell, any file, deletion.
- Chrome mode controls tabs with your signed-in sessions, and keys and credentials are reachable through the shell.
This is third-party code. Review the repository files before installing.
What it does
Mac Developer Bridge gives an MCP client the permissions of your macOS user. ChatGPT stays the only agent and does the reasoning, while the Mac is the execution environment. The bridge itself calls no OpenAI models. Tools come in groups. Shell: `shell_exec` for one-off commands and `shell_start` for long background jobs with logs. Files: read, write, move, permissions and diff application through `git apply`. Interactive terminals with a real pty. Reading stored Codex threads without starting a new model turn. An optional background Chrome mode drives tabs of the real profile without taking focus. An audit log and a kill switch come included.
Who it is for. macOS developers who want to run work on the local machine from ChatGPT and accept the risk of unrestricted access.
Good fit when
- Yesterday's Codex session must be found, its repository opened and the work finished from ChatGPT.
- Tests, builds and Git run on the home Mac while the model in chat reads the results.
- A long process starts in the background and its log tail is checked later.
- A page in an already signed-in Chrome must be filled in without grabbing the window.
Not a fit when
- An isolated environment is needed: the bridge has no sandbox and no command allowlist.
- The Mac holds production keys and data that a remote agent must not reach.
- Work happens on Windows or Linux, while the bridge targets macOS.
Example request
Find yesterday's Codex session, open its repository, fix the failing CI, push the result and tell me what changed.MCP
- Transport
- http
- Authentication
- OAuth
Environment variables
MAC_DEV_BRIDGE_FULL_ACCESS_ACK- Full access acknowledgement: when set, the bridge skips the unlock file check.
Limitations
You need macOS, Node.js 18 or newer, `cloudflared` with your own tunnel and developer mode in ChatGPT. Workspaces have an option through OpenAI Secure MCP Tunnel. The bridge is unofficial and unaffiliated with OpenAI and Cloudflare. No allowlist of commands or paths exists, so limiting privileges is up to you. The background Chrome extension is loaded by hand as an unpacked extension and enabled separately. The author asks you to read SECURITY.md before launch. An unlock file checked before every call adds protection, but the acknowledgement environment variable bypasses it.
How to disable. Stop the bridge with `scripts/disable.sh`: it shuts down the server, background jobs, terminals and child MCP servers. Then remove the LaunchAgent and the Chrome extension.
FAQ
How does the bridge differ from a local agent?
There is no second reasoning loop: ChatGPT stays the agent and the Mac only executes commands. The bridge itself calls no models.
How do I shut the bridge down fast?
Run `scripts/disable.sh`. It stops the front end, the bridge, background jobs and terminal sessions, then verifies the processes ended.
What does background Chrome mode see?
Tabs from the real profile with your sessions. The mode is off by default, and the `MDB` tab group is built separately and holds eight tabs by default.
What is needed to run it?
macOS, Node.js 18 or newer, `cloudflared`, a hostname with a tunnel and developer mode in ChatGPT. Workspaces can use `install.sh` with OpenAI Secure MCP Tunnel.
Does the bridge read Codex history?
Yes, through read-only `codex app-server` methods. The bridge never starts a `turn/start` model turn.
Discussion
No questions or reviews yet.
Related
MCP serversA Codex skill hands planning and review to ChatGPT over a local MCP bridge and keeps execution and checks in Codex
CodexPro
codexpro
A local MCP server that gives ChatGPT in developer mode tools for reading, searching, editing and checking the repositories you allow
An MCP server on your machine that lets ChatGPT and Claude edit code, run tests and check Git in a local repository
A self-hosted MCP server that gives ChatGPT and other clients access to code on your machine: read, edit, search and run commands
A terminal and browser client opens a chat between an Anthropic model and any MCP server so its tools can be tested.
A plugin with skills for building TypeScript MCP servers and MCP apps: the agent scaffolds, edits, debugs and verifies them
README in short
The bridge exposes local tools over MCP through a tunnel, with no reasoning of its own: ChatGPT makes every decision. An audit log, unlock and kill switch support unattended use. Detailed OAuth and Cloudflare setup steps are in DEPLOY.md.