give your agent a Mac mini.
Different providers. Different MCPs. One persistent computer your agent can own — apps, files, shell, browser, native macOS and full desktop control.
machine mac mini
state persistent
control MCP
agent welcome home
Not remote hands.
Your agent's Mac.
Persistent
Apps stay installed. Files stay put. Accounts, browser sessions, projects and permissions survive between jobs.
Mac-native
Shell, apps, desktop, native services and admin-capable control. A computer the agent can actually use, not a disposable sandbox.
Human optional
Humans can screen-share into the same machine. They don't need to stand by and click for the agent.
Different providers.
Different MCPs.
One Mac.
MacMCP doesn't bet on one host or one automation stack. Choose where the Mac lives. Compose the MCPs that are best at each job. Keep one durable machine identity above both.
Hyperbox Scaleway
MacStadium AWS your Mac
MCP stack
MacOS-MCP mac-mcp
iMCP macminid + more
→ mac x
Use the best tool
for the job.
Structured first
Shortcuts and native APIs when macOS already knows exactly what the agent means.
See + act
Accessibility and semantic desktop control for real apps and workflows.
Everything else
Terminal, files, local services and browser control when they're the simplest route.
Mac X. Mac Y. Mac Z. Different providers and different capability stacks behind one agent-facing control plane.
mac.use("x")
mac.capabilities("x")
mac.provision(requirements)
# choose provider + MCP stack
Bring one.
Or make one.
Your Mac
Connect Apple hardware you already own and give an agent a durable home.
Hosted Mac
Provision from the provider that fits the workload, availability and price.
Mac X, Y, Z
Add machines as agents, ventures and workloads earn them. Provider stays an implementation detail.
Mac X is already taking MCP calls.
Hyperbox is the first reference machine. MacMCP is the layer above it.