BrowserHere MCP Server

by 1ts-browserhere Your server? Claim it

answering

BrowserHere is answering right now. Last checked 1 min ago.

Control a real browser from AI agents: navigate, click, type, screenshot, read the page.

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

748 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check BrowserHere every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add browserhere --transport http https://browserhere.1ts.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://browserhere.1ts.app/mcp

~/.codex/config.toml

[mcp_servers.browserhere]
url = "https://browserhere.1ts.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "browserhere": {
      "url": "https://browserhere.1ts.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "browserhere": {
      "type": "http",
      "url": "https://browserhere.1ts.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://browserhere.1ts.app/mcp	streamable-http	sign-in	586 ms	1 min ago

Alternatives to BrowserHere

same job, measured the same way

Ikenga iyke (control bridge)

by royalti-io

Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.

53 installs/wk local only

Ikenga iyke (control bridge)

by ikenga

Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.

local only

BRYG

by flexiblepackage

Drives a real Chromium browser: navigate, click, type, read pages, OCR, QR, network capture

198 installs/wk local only

Remote Browser MCP Server from MCPBundles

by mcpbundles

Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video

answering

PilotGentic

by pilotgentic

macOS desktop control for Claude: click, type, screenshot, AX tree, browser control, agentic loops.

5 installs/wk local only

terminal-use

by computer-agent-labs

Lets AI agents drive a real terminal: type, press keys, click, read the screen, take screenshots.

85 installs/wk local only

Browser MCP

by mrfentmen

Control a local headless Chrome browser: open pages, read titles, and take screenshots.

604 installs/wk local only

Browser MCP

by shreyas-profile

Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.

answering

BrowserHere — questions

Answers built from our own checks of this server.

Why is there no tool list for BrowserHere?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is BrowserHere working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 748 ms. The bar chart above shows every period we have measured.

How do I connect BrowserHere?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to BrowserHere?

No API key is involved. BrowserHere answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is BrowserHere?

It answers our handshake in 748 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.