spring-ai-chrome-mcp-server

Provides an MCP server that allows an AI agent to control a Chrome browser instance and perform web-browsing actions (open browser/tabs, navigate, click links, input text, extract page text, take screenshots, manage cookies).

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ DevTools mcp browser-automation chrome web-interaction agent-tools screenshot text-extraction

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

The README indicates browser/cookie operations but does not describe authentication, sandboxing, or secret/cookie isolation. MCP is run via local stdio (no TLS/auth controls described), so security depends on deployment environment. Risk of handling sensitive cookies/PII and of unsafe web content interaction if not sandboxed.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You need agent-driven, interactive browser actions and you can run the MCP server locally/in a controlled environment.

Avoid When

You need formal auth, strict rate-limit controls, or comprehensive operational/error-contract documentation.

Use Cases

• Automated research workflows that require interacting with live web pages
• Testing/validation of UI flows via scripted browser interactions
• Summarizing content from pages after navigation/search
• Collecting page metadata (title, text, screenshots) for downstream processing

Not For

• Highly sensitive tasks where handling private credentials/cookies is required without strong isolation
• Use in untrusted browsing contexts without sandboxing
• Production systems needing strict reliability guarantees or documented operational guarantees

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication mechanism is described in the provided README; MCP is configured via local stdio command args.

Pricing

Free tier: No

Requires CC: No

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ State management matters: browsers are tracked by browser ID and tabs by index; the agent must track and pass the correct IDs/indices.
⚠ Navigation/click actions depend on page load timing; without explicit waits (not documented), actions may fail or operate on the wrong page state.
⚠ Cookie/session handling may persist across operations unless explicitly cleared; agents should be careful about cross-task contamination.

Alternatives

Playwright/Selenium driven directly from your agent/runtime Browserless/automation SaaS (if you require managed infrastructure) Headless scraping tools for static content (where JS execution is unnecessary)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for spring-ai-chrome-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.