Spring AI Chrome MCP Server

Created By
qoxogusa year ago
Overview

What is Spring AI Chrome MCP Server?

Spring AI Chrome MCP Server is a server that interacts with the Chrome browser, allowing users to automate various browser tasks.

How to use Spring AI Chrome MCP Server?

To use the server, you can send commands to open the browser, perform searches, navigate to URLs, and manage tabs. For example, you can instruct it to open a browser, search for a term, summarize a blog, or check the exchange rate.

Key features of Spring AI Chrome MCP Server?

  • Open and manage multiple browser instances.
  • Perform Google searches and navigate to specific URLs.
  • Take screenshots and extract page text.
  • Close tabs and browsers programmatically.

Use cases of Spring AI Chrome MCP Server?

  1. Automating web scraping tasks.
  2. Conducting research by summarizing web content.
  3. Managing multiple browser sessions for testing purposes.

FAQ from Spring AI Chrome MCP Server?

  • Can I run multiple browsers at the same time?

Yes! You can manage multiple browser instances using unique IDs.

  • Is there a limit to the number of tabs I can open?

No, you can open as many tabs as your system resources allow.

  • What programming language is used for this project?

The project is developed in Java.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qoxogus
Star
0
Language
Java
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