What is Agent Browser

Agent Browser is a centralized tool that allows users to manage multiple MCP servers from a single interface, eliminating the need for individual configurations for each client.

Use cases

Use cases for Agent Browser include streamlining the development process by reducing configuration time, managing server connections for various clients, and ensuring consistent updates across multiple applications.

How to use

To use Agent Browser, access the web UI at http://localhost:8080/ui/. From there, you can view connection statuses, add or remove MCP server connections, and monitor connection health in real-time.

Key features

Key features include the ability to manage all MCP server connections in one place, real-time monitoring of connection health, and simplified server updates across multiple clients.

Where to use

Agent Browser is ideal for developers and teams working with multiple MCP servers, particularly in environments that require efficient server management and real-time data monitoring.

Agent Browser

Overview

Agent Browser eliminates the need to configure each MCP server in every client. Connect your clients once to Agent Browser, and it will manage all your Server-Sent Events (SSE) MCP servers for you.

Usage

Access the web UI at http://localhost:8080/ui/ to:

• View connection status of your MCP servers
• Add new MCP server connections
• Remove existing connections
• Monitor connection health in real-time

Installation

Package Managers

macOS and Linux

brew tap cob-packages/homebrew-agent-browser
brew install cob-packages/agent-browser/agent-browser
agent-browser

Windows

scoop bucket add agent-browser https://github.com/cob-packages/scoop-agent-browser
scoop install agent-browser
agent-browser

Client Integration

Cursor

After installing and running Agent Browser, Cursor will automatically detect and connect to it. No additional configuration needed.

Other MCP Clients

Add Agent Browser as an SSE endpoint in your MCP client configuration:

{
  "Agent Browser": {
    "url": "http://localhost:8087/sse"
  }
}

Once your client is connected to Agent Browser, you can add or remove MCP servers without touching your client configurations.

Project Structure

/cmd             - Application entry points
/internal
  /app           - Core application setup with Fx
  /backend       - Database and persistence layer
  /config        - Configuration management
  /cursor        - Cursor integration
  /events        - Event bus for internal communication
  /log           - Logging utilities
  /mcp           - MCP server implementation
  /web           - Web server and UI
/scripts         - Build and utility scripts
/out             - Compiled binaries (git-ignored)

API Documentation

The Agent Browser exposes a REST API for integration. For details on accessing the API documentation, using Swagger UI, or integrating with tools like Postman, see API.md.

Future Direction

Protocol Support Implementation

We plan to expand Agent Browser to support additional protocols alongside MCP.

Future Tasks

• [ ] Add A2A protocol support
• [ ] Add ACP protocol support
• [ ] Implement protocol auto-detection

      Client
         │
         ▼
   Agent Browser
    /    │    \
   /     │     \
  ▼      ▼      ▼
 MCP    A2A    ACP  ...

Relevant Files

• /internal/mcp - MCP protocol implementation
• /internal/web - Web server and UI components
• /internal/config - Configuration management

Development

Prerequisites

• Go 1.21 or later
• Bash (for setup scripts)

Setup and Run

# Clone the repository
git clone https://github.com/faintaccomp/agent-browser.git
cd agent-browser

# Install development tools
make setup

# Build and run
make run

The application will be available at http://localhost:8080.

Support

For issues or inquiries: cobrowser.xyz