Chrome Control
Let AI agents use your real Chrome over MCP: each agent in its own tabs and coloured tab group, beside you, and cleaned up when done. Native messaging + Chrome DevTools Protocol, Windows/Linux/macOS,
- Transport
- stdio
- Status
- Local
エージェントを強化
このサーバーを追加
Install from the publisher. Not a PlugMCP endpoint.
RepositoryPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
PlugMCP で実行
キーとログ付きでコピーをホスト。
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
起動Server facts
Local- Transport
- stdio
- License
- MIT
- Last checked
- 2026-11-08
- Stars
- 2
- Tools
- —
- Uptime
- —
Overview
About Chrome Control
Let AI agents use your real Chrome over MCP: each agent in its own tabs and coloured tab group, beside you, and cleaned up when done. Native messaging + Chrome DevTools Protocol, Windows/Linux/macOS, works with any MCP client.
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Questions
How do I install Chrome Control?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Chrome Control need an API key?
No required environment variable is listed on this record.
What transport does Chrome Control use?
Chrome Control runs locally over stdio.
When was Chrome Control last checked?
Last checked 2026-11-08. Let AI agents use your real Chrome over MCP: each agent in its own tabs and coloured tab group, beside you, and cleaned up when done. Native messaging + Chrome DevTools Protocol, Windows/Linux/macOS, works with any MCP client.
From the publisher
Documentation
README is not crawled yet. Open the repository
Let AI agents use your real Chrome over MCP: each agent in its own tabs and coloured tab group, beside you, and cleaned up when done. Native messaging + Chrome DevTools Protocol, Windows/Linux/macOS, works with any MCP client.