Skip to main content
Glama
deenesjakoruzh
luigimasango-dev

browser-tools-mcp

by luigimasango-dev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

browser-tools-mcp

Persistent, headed Chromium browser control for OpenCode/Claude Code, in the style of Claude Code's browser tool. Built 2026-08-05 because OpenCode had no native browser tool and custom-scraper (plain HTTP) can't read JS-heavy or login-walled pages.

Architecture

The MCP server process is the singleton browser manager. Because OpenCode keeps the stdio server alive for the whole CLI session, the browser survives across agent turns. If the browser crashes or the window is closed, the next tool call transparently relaunches it (server/browser.js).

Launch config: headless: false, slowMo: 100, viewport 1280x800, desktop Chrome UA, --disable-blink-features=AutomationControlled.

Related MCP server: chrome-mcp

Files

  • server/server.js — MCP entrypoint, registers the five tools + schemas.

  • server/browser.js — singleton browser/context/page manager + relaunch logic.

  • server/tools.js — the operations (interactable tree, targeting, highlight, screenshots).

  • server/_self_verify.js — standalone scenario test: npm run verify.

  • shots/ — screenshots from browser_inspect.

  • USAGE.md — agent-facing rules (wired into OpenCode instructions).

Tools

Tool

Purpose

browser_navigate(url)

Load a URL; returns final URL + title.

browser_inspect()

Screenshot + interactable element tree with numeric targets.

browser_click(target)

Click by inspect number, CSS selector, or visible text.

browser_fill(target, value)

Type into a field by number/selector/text.

browser_request_human(message)

Pause flow and surface a question to the human.

Element targeting matches the Claude Code convention: browser_inspect assigns each interactable element a numeric target, tagged in the DOM as data-bt-target so later actions resolve the exact same element (visible- filtered indices would drift against unfiltered .nth() on pages with hidden inputs). Elements are highlighted briefly before clicking so the user sees the action.

Verification

npm run verify        # navigate -> inspect -> click -> fill -> crash-recovery

Verified 2026-08-05: example.com navigate/inspect/click, Google fill by target, and relaunch-after-kill all pass; all five tools registered and responded over the real MCP stdio protocol.

Operational notes

  • Headed means a desktop. The Chromium window needs an interactive session to launch; on a headless/disconnected box the launch fails — report that rather than pretending.

  • Isolated browser. This is NOT Luigi's logged-in Chrome (that's chrome-bridge). No logged-in sessions, no extensions, full write access.

  • Human-gated. No logins/orders/sends without explicit instruction; browser_request_human means STOP until the human answers.

  • Registered in ~/.config/opencode/opencode.jsonc as the browser-tools MCP server; usage rules wired into instructions via USAGE.md.

This server cannot be installed

A
license - permissive license
-
quality - not tested
C
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • gotham-browser

    gotham-os
    F
    license
    -
    quality
    B
    maintenance
    Enables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.

  • chrome-mcp

    Mehmoodqureshi
    A
    license
    B
    quality
    A
    maintenance
    Enables controlling a real Chrome browser from MCP hosts like Claude, with extension-based or CDP fallback, supporting tabs, navigation, interaction, and page reading tools.
    33
    265
    5
    MIT

  • codex-browser

    sj18259360196-source
    A
    license
    -
    quality
    B
    maintenance
    Enables Codex to control a visible Chromium browser via MCP tools for navigation, page inspection, and interaction, while keeping sensitive steps like login and captcha under the user's control.
    3
    1
    MIT

View all related MCP servers

Related MCP Connectors

  • browser-mcp

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

  • Tap

    Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.

  • sncro

    Live browser debugging for AI assistants — DOM, console, network via MCP.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/luigimasango-dev/browser-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server