Skip to content
Sparky coding

Enabling Full-stack Automated AI Debugging

Pouring fuel on the AI development fire

Now You're Cooking

Sparky waving Welcome! Sparky is here to help you fire up your AI-powered browser debugging.

One command. Your AI agent can see your browser.

npx gasoline-mcp

Gasoline MCP is a browser extension + local MCP server that streams real-time browser data to autonomous coding agents. Console errors, failed API calls, uncaught exceptions, WebSocket traffic, live DOM state — your AI sees it all and fixes issues without you lifting a finger.

Smart Teams Cook With Gasoline MCP

Sparky says: No more copy-paste debugging. Just code, fix, and ship.

No debug port required. Other tools need Chrome launched with --remote-debugging-port, which disables security sandboxing and breaks your normal browser workflow. Gasoline MCP uses a standard extension — your browser stays secure and unmodified.

Single binary, zero runtime. No Node.js, no Python, no Puppeteer, no package.json. One Go binary that runs anywhere. No supply chain risk. No node_modules.

Captures what others can't. WebSocket messages, full request/response bodies, user action recording, Web Vitals with regression detection, API schema inference, and Playwright test generation from real browser sessions — features no other MCP browser tool offers.

Works with every MCP tool. Claude Code, Cursor, Windsurf, Zed, Claude Desktop, VS Code + Continue. Switch AI tools without changing your debugging setup.

Enterprise-safe by design. Binds to 127.0.0.1 only. Auth headers are stripped automatically. No telemetry, no accounts, no cloud. Audit the source — it's AGPL-3.0.

Sparky cooking with gasoline

How Gasoline MCP Compares

Gasoline MCP Chrome DevTools MCP BrowserTools MCP Cursor Browser
Console logs
Network errors
Network bodies
WebSocket events
User action recording
DOM queries
Screenshots
Web Vitals✅ LCP, CLS, INP, FCP
Regression detection✅ Automatic
API schema inference✅ OpenAPI from traffic
Accessibility audits✅ WCAG + SARIF
Session checkpoints✅ Named + auto
Noise filtering✅ Auto-detect
Test generation✅ Playwright
Reproduction scripts✅ From actions
PR summaries✅ Perf impact
HAR export
Zero dependencies✅ Single Go binary❌ Node.js + Chrome flags❌ Node.js + Puppeteer❌ Electron
Vendor neutral✅ Any MCP tool⚠️ Any MCP tool⚠️ Any MCP tool❌ Cursor only
No debug port❌ --remote-debugging-port❌ --remote-debugging-portN/A
Privacy✅ Localhost only✅ Local⚠️ Optional cloud❌ Cursor servers
Performance overhead< 0.1ms~5ms~5msUnknown

Full comparison →

Enterprise Ready — Zero Data Leakage

Sparky with shield

No browser data is ever shared with any AI provider. Gasoline MCP runs entirely on your machine:

  • Localhost only — the server binds to 127.0.0.1, unreachable from the network
  • No cloud, no accounts, no telemetry — nothing phones home, ever
  • Auth headers stripped — tokens and API keys are automatically redacted
  • Open source (AGPL-3.0) — audit every line your security team cares about

Your browser logs stay on your hardware. The AI reads a local file via stdio. At no point does debugging data touch a third-party server — making Gasoline MCP safe for regulated environments, proprietary codebases, and enterprise security policies.

Full Security Details →

Ecosystem Neutral — No Vendor Lock-In

Gasoline MCP implements the open Model Context Protocol standard. Swap AI tools without changing your debugging setup:

  • Claude Code.mcp.json in project root
  • Cursor~/.cursor/mcp.json
  • Windsurf~/.codeium/windsurf/mcp_config.json
  • Claude Desktop — OS-specific config
  • Zed~/.config/zed/settings.json
  • VS Code + Continue~/.continue/config.json

Not tied to Anthropic. Not tied to Cursor. Not tied to anyone. If your agent speaks MCP, Gasoline MCP fuels it.

The Pipeline

[ Browser ] → [ Extension ] → [ localhost:7890 ] → [ Any MCP AI ]
                                    ↕
                              Stays on your machine
  1. The extension passively captures your browser activity
  2. Data flows to a local server — never the internet
  3. Your AI tool reads it via MCP (stdio, not network)
  4. Nothing leaves your machine — private by architecture

What Gets Captured

  • Console Logsconsole.log(), .warn(), .error() with full arguments
  • Network Errors — Failed API calls (4xx/5xx) with response bodies
  • Exceptions — Uncaught errors with full stack traces
  • WebSocket Events — Connection lifecycle and message payloads
  • Network Bodies — Request/response payloads for API debugging
  • User Actions — Click, type, navigate, scroll recording with smart selectors
  • Web Vitals — LCP, CLS, INP, FCP with automatic regression detection
  • Live DOM — Query the page with CSS selectors via MCP
  • Accessibility — WCAG audits with SARIF export
  • API Schema Inference — Auto-discover OpenAPI from captured traffic
  • Session Checkpoints — Save state, diff changes, detect regressions over time
  • Test Generation — Playwright tests and reproduction scripts from actions
  • Noise Filtering — Auto-detect and dismiss irrelevant errors
  • Context API — Annotate errors with window.__gasoline_mcp

Zero Bloat, Zero Risk

  • Single binary — Go. No Node.js, no Python, no runtime deps.
  • < 0.1ms overhead — Per console intercept. Your browsing stays fast.
  • 20MB memory cap — The extension never bloats your browser.
  • Zero network calls — The binary never connects to the internet.
  • No dependencies — No supply chain risk. One binary, auditable.