1. Ignite the Server

npx gasoline-mcp

You’ll see: Gasoline server listening on http://localhost:7890

Leave this burning. No global install — npx handles everything.

2. Install the Extension

Grab it from the Chrome Web Store (search “Gasoline”). Click the icon in your toolbar — it should show Connected.

Load Unpacked (Development) 1. Clone the [repository](https://github.com/brennhill/gasoline) 2. Open `chrome://extensions` → enable **Developer mode** 3. Click **Load unpacked** → select the `extension/` folder

3. Connect Your AI Tool

Drop this config and your AI tool fires up Gasoline automatically:

Claude Code — .mcp.json in your project root:

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

See MCP Integration for Cursor, Windsurf, Claude Desktop, Zed, and more.

Restart your AI tool. From now on, the server ignites automatically.

Verify the Flame

Open your web app. Trigger an error:

console.error("Gasoline test — is the fire lit?")

Ask your AI: “What browser errors do you see?”

Available Tools

Your AI now has these at its disposal:

Tool What it does
get_browser_errors Console errors, network failures, exceptions
get_browser_logs All logs (errors + warnings + info)
clear_browser_logs Clear the log file
get_websocket_events WebSocket messages and lifecycle
get_websocket_status Connection states and rates
get_network_bodies Request/response payloads
query_dom Live DOM query with CSS selectors
get_page_info Page URL, title, viewport
run_accessibility_audit Accessibility violations

No MCP? No Problem.

Run standalone — Gasoline writes to ~/gasoline-logs.jsonl. Point your AI at the file.

npx gasoline-mcp

Next Steps