Agentbridge
Let your coding agent drive Classic Mac OS 7–9 apps and files through a shared-folder bridge without manual emulator babysitting.
Overview
AgentBridge is a MCP server for the Build phase that controls Classic Mac OS (System 7–9) from AI agents via a shared-folder protocol.
What is this MCP server?
- Stdio MCP package classic-mac-mcp on npm (v1.0.2)
- Shared-folder protocol between modern agents and System 7–9 hosts
- GitHub source at SeanFDZ/agentbridge for self-hosted setups
- Purpose-built for retro Mac automation from Claude Code, Cursor, and similar agents
- MCP server version 1.0.2
- Single npm stdio package identifier classic-mac-mcp
- Targets System 7 through Mac OS 9 hosts
Community signal: 22 GitHub stars.
What problem does it solve?
You cannot safely or repeatably operate legacy Mac software from a modern agent without a dedicated bridge protocol.
Who is it for?
Indie builders and archivists who still ship or test on System 7–9 and want Claude Code or Cursor to drive those sessions.
Skip if: Teams that only target modern macOS, iOS, or web apps with no Classic Mac footprint.
What do I get? / Deliverables
After you install the stdio MCP server, your agent can trigger Classic Mac actions through the shared folder instead of manual emulator steps.
- Registered stdio MCP server classic-mac-mcp in your agent
- Agent-callable control path to the Classic Mac host via shared folder
- Repeatable automation recipes for legacy Mac tasks
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the value is wiring an external runtime (vintage Mac) into your agent toolchain. Integrations fits a stdio MCP server that speaks a custom host protocol rather than shipping product UI.
How it compares
Vintage-host integration MCP, not a browser automation or cloud infra server.
Common Questions / FAQ
Who is AgentBridge for?
Solo builders, preservationists, and retro-dev fans who need AI agents to control Classic Mac OS through a documented shared-folder bridge.
When should I use AgentBridge?
Use it during Build when you are integrating agent tooling with emulated or physical System 7–9 machines for testing, media workflows, or legacy app maintenance.
How do I add AgentBridge to my agent?
Add the npm stdio MCP entry for classic-mac-mcp (v1.0.2), point it at your agent’s MCP config, and configure the shared folder path both on the host Mac and in your bridge settings per the GitHub repo.