sopioai/sopio-browser-mcp-server repository overview

⁠Sopio Browser MCP Server

HTTP + WebSocket relay and Model Context Protocol (MCP) server for Sopio Browser MCP⁠. Use it with the Chrome extension so MCP clients (Cursor, Claude Desktop, custom agents) can read and control tabs in your real, logged-in browser.

Docker Hub: sopioai/sopio-browser-mcp-server⁠

⁠What it does

• Exposes a session-scoped MCP endpoint: POST /mcp/<sessionId>
• Relays commands between MCP clients and the Chrome extension over WebSocket
• Serves the session dashboard and health endpoints on one port

⁠Architecture

MCP client  ↔  HTTP  ↔  this server  ↔  WebSocket  ↔  Chrome extension  ↔  tabs

The extension owns a stable sessionId (UUID). Point your MCP client at:

http://<host>:3000/mcp/<your-session-id>

⁠Quick start

docker run -d --name sopio-browser-mcp \
  -p 3000:3000 \
  -e NEXT_PUBLIC_APP_URL=https://your-public-url.example \
  -e LISTEN_HOSTNAME=0.0.0.0 \
  sopioai/sopio-browser-mcp-server:latest

Install the Chrome extension⁠ from the Chrome Web Store, open the popup, copy your session ID, then connect your MCP client.

For manual installs, builds are also available on GitHub Releases⁠.

⁠Environment variables

⁠Health checks

• GET /health or GET /healthz → ok
• GET /api/relay-stats → { "liveSessions": N }

⁠MCP tools (examples)

list_tabs, tab_navigate, tab_activate, capture_screenshot, capture_html, capture_text, script_execute_js, input_mouse_click, input_type_text, and more.

⁠Requirements

• Chrome extension (not included in this image) — Chrome Web Store⁠
• MCP client with Streamable HTTP transport

⁠Links

• Chrome extension: https://chromewebstore.google.com/detail/lnkakehkofmpjmehkchhfpgeophlafoi/⁠
• Source: https://github.com/sopio-ai/sopio-browser-mcp⁠
• Home: https://browser-mcp.sopio.ai⁠

⁠License

Apache-2.0