Agent Browser

What is Agent Browser?

Agent Browser is a centralized MCP server manager that eliminates the need to configure each MCP server in every client. Instead of adding a new server individually in Cursor, Windsurf, Claude, and every other client, you connect your clients once to Agent Browser, and it manages all your Server-Sent Events (SSE) MCP servers from a single place.

How to use Agent Browser?

Install Agent Browser via Homebrew (macOS/Linux), Scoop (Windows), or direct download from GitHub Releases, then run the executable. Access the web UI at http://localhost:8080/ui/ to view connection status, add new MCP server connections, remove existing connections, and monitor connection health in real-time. Cursor auto-detects Agent Browser; for other MCP clients, add it as an SSE endpoint at http://localhost:8087/sse.

Key features of Agent Browser

• Centralized management of SSE MCP servers
• Single configuration point for all MCP clients
• Real-time connection health monitoring
• Web UI for viewing, adding, and removing servers
• Automatic detection by Cursor

Use cases of Agent Browser

• Streamline onboarding when switching between multiple MCP clients (Cursor, Windsurf, Claude)
• Avoid reconfiguring every client whenever an MCP server URL or credential changes
• Monitor the health of multiple MCP server connections from one dashboard

FAQ from Agent Browser

How is Agent Browser different from configuring MCP servers directly in each client?

Without Agent Browser, you must add each new server in Cursor, Windsurf, Claude, and every other client individually, then update all clients whenever a server changes. With Agent Browser, you add the server once in the Agent Browser UI and update it once when it changes.

What are the runtime requirements for running Agent Browser?

Agent Browser is a standalone executable available for macOS (Intel and Apple Silicon), Linux (x86_64, ARM 64-bit, ARM 32-bit), and Windows (64-bit, 32-bit, ARM 64-bit). No additional runtime or dependencies are required to run the binary.

Which MCP transport does Agent Browser support?

Agent Broker manages Server-Sent Events (SSE) MCP servers for you. Future plans include adding A2A and ACP protocol support along with protocol auto-detection.

Where does Agent Broker expose its API?

The web UI is available at http://localhost:8080/ui/, and the SSE endpoint for other MCP clients is at http://localhost:8087/sse. A REST API with Swagger UI documentation is also available (see API.md).