Claude Chrome MCP

Created By
durapensaa year ago
Developer tool suite enabling Claude Desktop, Claude Code, and other MCP hosts like Cursor, to interact with claude.ai in Chrome browsers.
Overview

What is Claude Chrome MCP (CCM)?

Claude Chrome MCP (CCM) is a developer tool suite that enables integration between Claude Desktop, Claude Code, and other MCP hosts like Cursor with claude.ai in Chrome browsers.

How to use Claude Chrome MCP?

To use Claude Chrome MCP, install the Chrome extension, set up the MCP server in Claude Desktop, and utilize the CLI tool for direct browser control.

Key features of Claude Chrome MCP?

  • Chrome Extension for debugging and interaction with claude.ai
  • MCP Server for exposing Chrome capabilities to clients
  • Command-line interface for managing Claude sessions and tabs

Use cases of Claude Chrome MCP?

  1. Creating and managing Claude.ai tabs in Chrome.
  2. Sending messages and retrieving responses from Claude sessions.
  3. Debugging and executing scripts in the browser environment.

FAQ from Claude Chrome MCP?

  • Is the Chrome extension required for all functionalities?

Yes, the extension is necessary for interacting with claude.ai pages.

  • Can I use the CLI tool without the MCP server?

No, the CLI tool requires the MCP server to function properly.

  • What programming languages are supported?

The project is primarily built with JavaScript and includes TypeScript support for API definitions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
durapensa
Star
1
Language
JavaScript
License
GPL-3.0 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)

5 hours ago
Alloy

2 days ago