#chrome-extension

A chrome extension bridge that allows you to connect to a mcp server to use global window object.

Cursor Model Context Protocol (MCP) extension for Chrome - with comprehensive test coverage

Chrome Extension MCP Server implemented in Go - For Model Context Protocol to interact with Chrome extensions

Pick any element on any webpage and send its HTML, CSS, React props, console logs, and network context to Claude Code, Cursor, or Windsurf via MCP — in one click.

Open-source MCP server with 40+ browser automation tools, YAML workflow engine, and installable domain knowledge packs. Includes Chrome extension for real DOM access, REST API, and Svelte dashboard. Works with Claude Code, Cursor, Claude Desktop, and any MCP client.

Let AI agents like ChatGPT & Claude use real-world local/remote tools you approve via browser extension + optional MCP server

Developer tool suite enabling Claude Desktop, Claude Code, and other MCP hosts like Cursor, to interact with claude.ai in Chrome browsers.

Rip any YouTube transcript. Clean text, structured JSON, or Markdown for AI agents.

100-tool browser automation for AI agents via MCP. Screenshots, DOM inspection, network capture, form filling, cookie management, tab orchestration, session recording, and structured data extraction via Chrome extension. One-command setup: npx crawlio-browser init auto-configures 14 MCP clients.recording + 1 compiler) with framework-aware intelligence, typed evidence infrastructure, and confidence-tracked findings — captures what static crawlers can't see.

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)