"An MCP for controlling a browser using a Chrome extension" matching MCP servers:

Enables coding agents to add a bounded semantic-judgment layer for routing, ranking, extraction, verification, and escalation, returning typed signals and review recommendations.

Provides over 1,000 creative ways to decline requests across four categories (polite, humorous, professional, and creative). The MCP server wraps a REST API to help users craft professional rejections through natural language interactions.

A validation layer for AI coding assistants that enforces explicit LLM evaluations on plans, code diffs, and tests to ensure safer and higher-quality code.

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

Enables AI coding agents to discover, understand, and fix product issues (UX inconsistencies, accessibility violations, quality problems) identified by Skippr's browser extension through natural language commands.

Enables OpenCode to control a real browser through a local extension bridge, supporting navigation, DOM reading, clicking, typing, form filling, scrolling, dragging, screenshots, and more.

Lets several AI clients drive one shared, signed-in Chrome at the same time, giving each session its own background tabs and tab group with per-tab leases so mutations queue while reads overlap. Exposes a full Chrome DevTools-style toolset plus Claude's 31-member browser toolset, along with an HTTP endpoint that turns Messages API tool_use blocks into tool_result blocks.

Enables daily check-in, points and task queries for Huawei Cloud Developer Growth Center via a Chrome extension and Node.js bridge.

A paid remote MCP server for checking extension compatibility and generating structured receipts, audit logs, and reviewer-ready evidence.

A minimal reproduction repository designed to demonstrate and test Chrome extension loading within the Playwright MCP server. It evaluates specific configuration settings required for successful extension injection and page modification.

An MCP server that connects AI agents to a running Chrome tab via the Chrome DevTools Protocol (CDP), enabling runtime debugging and page inspection.

Enables AI agents to attach to Chrome tabs, set breakpoints, inspect scope variables, evaluate expressions, and step through code using Chrome DevTools Protocol for runtime debugging.

Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.

Enables AI coding agents to inspect and operate Chrome as a developer, including reading DevTools console/network data, evaluating JavaScript, and managing unpacked extensions during an edit-test-debug loop.

Enables searching and retrieving content, module information, and Twig template snippets from a-blog cms via its GET API.

Enables browser automation and inspection by connecting to an already-running Chrome/Chromium over the DevTools protocol, with page-scoped routing so multiple clients can control separate tabs concurrently.

Lets coding agents control and inspect a live Chrome browser via the Model-Context-Protocol, providing advanced browser debugging, performance insights, and reliable automation.

Enables MCP clients like Claude Desktop to automate and interact with claude.ai via a Chrome extension and WebSocket relay.

An MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.

Lets AI coding assistants control and inspect a live Chrome browser through MCP, enabling reliable automation, debugging, and performance analysis using Chrome DevTools.

Enables MCP clients to drive individually named Chrome profiles, providing tools for tabs, navigation, page interaction, screenshots, JavaScript evaluation, console logs, and network inspection over stdio without a TCP port.

A fork of Chrome DevTools MCP that adds Streamable HTTP transport for multiple AI agents to concurrently control and inspect a live Chrome browser via the Model Context Protocol.

Enables coding agents to control and inspect a live Chrome browser, providing reliable automation, debugging, performance insights, screenshots, network analysis, and console messages through MCP.

MCP server for Redmine that enables interaction with issues, wiki pages, and time entries through natural language.

Exposes foldkit's 7-prime spine, 7 κ-bands, and 6 fold operations as native tools and resources for MCP clients like Claude Code, Claude Desktop, Cursor, Cline, and Windsurf.

Exposes VS Code diagnostic problems like errors and warnings in real-time to AI agents via the Model Context Protocol. It enables AI tools to see compilation and linting issues directly from the problems panel to provide context-aware debugging and automated fixes.

Enables AI agents to inspect a running VS Code webview or extension host in real time, exposing DOM, console, state-store, performance, and message-traffic data over a stdio connection. Tool activation is config-driven, so MobX, Redux, Zustand, or Apollo store tools and backend-side tools appear only when the corresponding adapters are wired up.

Enables MCP clients to drive your already-open Chrome browser like a human, using 45 tools for navigation, perception, capture, and trusted input that pages receive as genuinely user-generated.

Enables AI assistants to inspect Chrome Web Store status, metrics, ratings, and reviews, and to upload, publish, roll back, or adjust rollout of extension versions, with human confirmation for changes that affect users.

A token-optimized MCP server that groups Chrome Devtools tools into 8 semantic operations, reducing context window tokens by 69.5% while preserving full functionality.