MCP Server Mode

Overview

Browse can run as an MCP (Model Context Protocol) server, letting editors communicate with it natively instead of spawning shell commands.

browse --mcp

Use --json alongside --mcp for structured responses:

browse --mcp --json

Note: Requires npm install @modelcontextprotocol/sdk alongside browse.

Cursor

Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "browse": {
      "command": "browse",
      "args": ["--mcp"]
    }
  }
}

After saving, restart Cursor. Browse will appear as an available MCP tool.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "browse": {
      "command": "browse",
      "args": ["--mcp"]
    }
  }
}

Windsurf

Add to your Windsurf MCP configuration:

{
  "mcpServers": {
    "browse": {
      "command": "browse",
      "args": ["--mcp"]
    }
  }
}

MCP vs CLI

Both modes use the same persistent daemon — no performance difference. Choose MCP if your editor supports it natively, CLI if you want universal compatibility.