Fuel Any Agent

Gasoline is an open-source MCP server that implements the Model Context Protocol — a standard for connecting AI assistants to external tools. Any MCP-compatible tool can tap into your browser state. Zero dependencies. Localhost only.

Supported Tools

Tool	Config Location	Guide
Claude Code	`.mcp.json` (project root)	Setup →
Cursor	`~/.cursor/mcp.json`	Setup →
Windsurf	`~/.codeium/windsurf/mcp_config.json`	Setup →
Claude Desktop	OS-specific config file	Setup →
Zed	`~/.config/zed/settings.json`	Setup →
VS Code + Continue	`~/.continue/config.json`	Below

How MCP Mode Works

Gasoline runs as a dual-mode server by default:

HTTP server — background process for the browser extension
MCP protocol — stdio channel for your AI tool
Auto-managed — your AI tool starts and stops the server

What MCP tools does Gasoline provide?

Gasoline exposes 5 composite tools — each with multiple sub-modes controlled by a single parameter. This reduces decision space by 79% compared to individual tool calls.

Tool	What it does	Sub-modes
`observe`	Real-time browser state	errors, logs, network, websocket_events, websocket_status, actions, vitals, page
`analyze`	Data analysis and insights	performance, api, accessibility, changes, timeline
`generate`	Code generation from captured data	reproduction, test, pr_summary, sarif, har
`configure`	Session and noise management	store, noise_rule, dismiss, clear
`query_dom`	Live DOM inspection	CSS selector queries

observe

Monitor browser state in real time. Use the what parameter to select:

Mode	Returns
`errors`	Console errors with deduplication and noise filtering
`logs`	All console output (configurable limit)
`network`	HTTP requests — filter by URL, method, status range
`websocket_events`	WebSocket messages — filter by connection ID, direction
`websocket_status`	Active WebSocket connections and stats
`actions`	User interactions (click, input, navigate, scroll, select)
`vitals`	Core Web Vitals — FCP, LCP, CLS, INP
`page`	Current page URL, title, viewport

analyze

Derive insights from captured data. Use the target parameter:

Target	Returns
`performance`	Performance snapshot with regression detection against baselines
`api`	Auto-inferred API schema (OpenAPI stub or gasoline format)
`accessibility`	WCAG audit results with caching
`changes`	Compressed state diff since a named/auto checkpoint
`timeline`	Merged session timeline (actions + network + errors)

generate

Generate code artifacts from your session. Use the format parameter:

Format	Output
`reproduction`	Playwright script reproducing user actions
`test`	Playwright test with network/error assertions
`pr_summary`	Markdown performance impact summary
`sarif`	SARIF accessibility report (standard format)
`har`	HTTP Archive export

configure

Manage session state and noise filtering. Use the action parameter:

Action	Effect
`store`	Persistent key-value storage (save/load/list/delete/stats)
`noise_rule`	Manage noise filtering rules (add/remove/list/auto_detect)
`dismiss`	Quick one-off noise dismissal by regex pattern
`clear`	Clear all browser logs

Custom Port

If port 7890 is occupied:

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

Update the extension’s Server URL in Options to match.

VS Code with Continue

Add to ~/.continue/config.json:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": ["gasoline-mcp"]
        }
      }
    ]
  }
}

How do I verify Gasoline is connected?

Restart your AI tool
Gasoline server ignites automatically
Extension popup shows “Connected”
Ask your AI: “What browser errors do you see?”