Chrome API MCP Server

Created By
needsupporta year ago
A Chrome browser control MCP server for AI assistants to directly interact with and control Chrome via Chrome DevTools Protocol
Overview

What is Chrome Control API?

Chrome Control API is a streamlined API designed for controlling the Chrome browser via the Chrome DevTools Protocol, enabling AI assistants to interact directly with Chrome.

How to use Chrome Control API?

To use the Chrome Control API, import the API in your JavaScript project, create an instance of the ChromeAPI class, and utilize its methods to manage tabs, navigate, interact with the DOM, and analyze page content.

Key features of Chrome Control API?

  • Tab management (create, list, close)
  • Navigation (go to URL, back, forward, reload)
  • DOM interaction (find elements, click, type text)
  • Page content analysis (extract structure, find content sections)
  • Intelligent search handling (automatically find and use search fields)
  • Screenshot capture (full page or specific elements)
  • JavaScript execution
  • Network traffic monitoring

Use cases of Chrome Control API?

  1. Automating web testing and interactions for applications.
  2. Building AI assistants that can navigate and extract information from web pages.
  3. Enhancing browser automation tasks for developers and testers.

FAQ from Chrome Control API?

  • Can I control multiple tabs at once?

Yes! The API allows you to manage multiple tabs simultaneously.

  • Is the Chrome Control API free to use?

Yes! The API is open-source and free to use.

  • What programming language is required?

The API is designed for use with JavaScript and TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
needsupport
Star
0
Language
TypeScript
License
-
Tags

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