MCP server that gives AI agents real-time access to browser runtime errors, console logs, and page diagnostics via a Chrome Extension.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"browser-runtime-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Browser Runtime MCP Give AI agents real-time access to browser runtime errors, console logs, and page diagnostics. **The problem:** AI coding agents can read your source code but are blind to what actually happens in the browser — runtime errors, console warnings, failed API calls, CSS rendering issues. You end up copy-pasting DevTools output back and forth. **The solution:** A Chrome Extension captures browser events and streams them to a local MCP server. Your AI agent (Claude Code, Cursor, etc.) can query errors, console logs, and page state directly through MCP tools. ``` Browser tab → Chrome Extension → localhost MCP server → AI agent ``` ## Quick Start ### 1. Install the MCP server ```bash pip install browser-runtime-mcp ``` ### 2. Install the Chrome Extension Download the `extension/` folder from this repo, then: 1. Open `chrome://extensions` 2. Enable **Developer mode** 3. Click **Load unpacked** → select the `extension/` folder ### 3. Configure your AI tool **Claude Code** — add to `~/.claude/settings.json`: ```json { "mcpServers": { "browser-runtime-mcp": { "command": "browser-runtime-mcp", "args": [] } } } ``` **Other MCP clients** — run the server in stdio mode: ```bash browser-runtime-mcp ``` ### 4. Use it Open the extension popup on the site you want to debug and click **Enable capture on this site**. Capture is disabled by default and the allowlist is stored locally in Chrome. Then ask your AI agent: - "Are there any browser errors?" - "What's in the console logs?" - "What pages is the extension tracking?" ## MCP Tools | Tool | Description | |------|-------------| | `get_browser_errors` | Runtime errors with stack traces and DOM context | | `get_console_logs` | Console output (error/warn/log), filterable by level | | `get_page_info` | Tracked pages and buffer statistics | | `clear_buffers` | Clear all buffered data for a fresh start | ## How It Works ``` ┌─────────────────┐ postMessage ┌───────…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.