MCP Browser
Let your coding agent drive a real macOS WKWebView browser over HTTP MCP when headless automation misses rendering, cookies, or Apple Silicon-native behavior.
Overview
MCP Browser is a MCP server for the Build phase that lets AI agents control a native macOS WKWebView browser over local HTTP with bearer authentication.
What is this MCP server?
- Native macOS 14+ Apple Silicon app with embedded WKWebView
- Streamable HTTP MCP at http://127.0.0.1:8833/mcp with bearer token auth
- Per-launch regeneratable bearer token from Settings → Connection
- Settings → MCP Clients tab can patch Claude Desktop and Codex configs automatically
- Signed DMG distribution from GitHub releases (v1.0.1)
- Version 1.0.1
- Endpoint http://127.0.0.1:8833/mcp
- Transport: streamable-http
Community signal: 1 GitHub stars.
What problem does it solve?
Coding agents often cannot reproduce real Safari-class rendering and session state when every browser tool is headless or remote-only.
Who is it for?
Mac-based indie builders validating web flows, auth cookies, and UI behavior through Claude Code or Codex with minimal MCP wiring.
Skip if: Windows or Linux developers, headless CI-only pipelines, or teams that need cloud browser farms instead of a single-user Mac app.
What do I get? / Deliverables
After install, your agent posts MCP JSON-RPC to localhost:8833 and drives an on-machine browser with a rotatable bearer token.
- Agent-controlled browsing in a native WKWebView session
- Regeneratable local bearer token for MCP authentication
- Optional auto-patched MCP client config for Claude Desktop and Codex
Recommended MCP Servers
Journey fit
Browser control for agent-driven builds lands in Build where integrations connect your product experiments to real user-agent surfaces. A local HTTP MCP endpoint that steers WKWebView is an integration layer between agents and the live web stack on Mac.
How it compares
Local WKWebView browser MCP on macOS, not a remote Playwright cloud or a pure scraping skill.
Common Questions / FAQ
Who is MCP Browser for?
MCP Browser is for solo builders on macOS 14+ Apple Silicon who want agents to drive a real local browser via MCP HTTP.
When should I use MCP Browser?
Use it during Build integrations when you need authentic page rendering, cookies, or manual-site debugging steered from Claude Desktop, Codex, or Cursor.
How do I add MCP Browser to my agent?
Download the latest signed DMG, install to /Applications, open Settings → Connection for the bearer token and http://127.0.0.1:8833/mcp endpoint, or use Settings → MCP Clients to patch Claude Desktop and Codex.