Chrome Extension MCP Server (Go Version)

Created By
fujirona year ago
Chrome Extension MCP Server implemented in Go - For Model Context Protocol to interact with Chrome extensions
Overview

What is Chrome Extension MCP Server (Go Version)?

This project is a Go implementation of the Model Context Protocol (MCP) server for Chrome Extension API, enabling Claude to interact with Chrome browser extensions.

How to use Chrome Extension MCP Server?

To use the server, install the Chrome extension and run the server either from source or using a binary. Configure the MCP server for Claude by adding the necessary details to the configuration file.

Key features of Chrome Extension MCP Server?

  • WebSocket server for Chrome extension communication
  • Support for Model Context Protocol (MCP)
  • Various Chrome browser operations including tab management, DOM manipulation, CSS injection, and more.

Use cases of Chrome Extension MCP Server?

  1. Enabling AI to perform browser operations through extensions.
  2. Managing browser tabs and extensions programmatically.
  3. Capturing screenshots and manipulating web page content.

FAQ from Chrome Extension MCP Server?

  • What is the purpose of this server?

It allows Claude AI to interact with Chrome extensions and perform various browser operations.

  • How do I install the Chrome extension?

You can install it using Docker or manually by loading the unpacked extension in Chrome.

  • Is this project open source?

Yes, it is available on GitHub under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fujiron
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

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)

a day ago