What is a #chromium MCP server?
An MCP server tagged #chromium implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access chromium-related tools, data, or APIs.
4 #chromium MCP Servers & Clients
Every MCP server and client below is tagged #chromium — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to chromium tools.
All
Browserbase MCP Server
browserbase
Allow LLMs to control a browser with Browserbase and Stagehand
Added 2 years ago
Chromium Bridge
dashi96
MCP bridge between Chromium browsers and Claude Code — browser automation tools + Claude chat panel for browsers where the official Claude in Chrome extension doesn't work (Arc, Vivaldi, …)
Added 9 days ago
PA
Pinako Ai Bridge
teleomorph
Pinako AI Bridge is the MCP server that connects Pinako, a Chromium extension for tab, window, library, and bookmark management, to local AI clients (Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Roo Code, Continue.dev, and any HTTP MCP client). Because the bridge runs in
Added 2 months ago
GDD (Giggly-Dazzling-Duckling)
Cap-of-tea
AI-controlled browser farm: run N isolated Chromium instances with 36 MCP tools for multi-device testing, screenshots, device emulation, network control, and console diagnostics.
Added 2 months ago
Frequently asked questions
Common questions about MCP servers and clients tagged #chromium
How many #chromium MCP servers and clients are there?
mcp.so currently lists 4 MCP servers and clients tagged #chromium.
How do I install a #chromium MCP server?
Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.