Chrome Actuator
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Chrome Actuatorcreate a new tab and navigate to github.com, then take a snapshot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Chrome Actuator
Unofficial companion: drive the Chrome window you already have open from an agent (tested with Grok Build). New work lands in a pink Actuator tab group in the current session, not a new Chrome window.
tabs_create → snapshot → press @e12 / fill @e5 "text" → settlev1 is an actuator, not a side-panel chatbot. The agent stays in the terminal.
The extension sees the page, assigns @eN refs, and clicks/types. Your cookies
and logins stay in Chrome.
Not affiliated with, endorsed by, or sponsored by xAI. "Grok" and "Grok Build" are xAI marks, used here only to describe compatibility. See NOTICE.
Status
Phases 0–3 are in. pnpm gauntlet covers unit tests, the content-script
actuator, and a live Chromium tab driven through native messaging.
Phase | What | State |
0 | Workspace, stable extension id, side panel | done |
1 | Native messaging heartbeat | done |
2 | snapshot / press / fill on a real tab | done |
3 | Agent plugin + | done |
Related MCP server: monkeysee
Load the extension
cd /path/to/chrome-actuator
pnpm install
pnpm --filter @chrome-actuator/extension buildOpen
chrome://extensionsEnable Developer mode
Load unpacked →
packages/extension/distPin the extension and click it (or
Cmd+Shift+G)
Then register the native host (once) and fully quit Chrome:
node packages/host/dist/install.js--trust on the plugin install lets the agent operate this Chrome profile.
Only do that if you trust the agent.
grok plugin install ./packages/plugin --trustSide panel should say connected once the MCP host is running.
pnpm gauntlet # unit + L3 + live native-messaging L4Stable unpacked id (from the committed manifest key): lgkcgenkjaalkfnpmglgpfclkaokblfj
Decisions we will not reopen
Brain in the agent, body in Chrome. No in-extension LLM loop in v1.
Native messaging, not WebSocket, not Playwright, not agent-device-the-binary.
agent-device contract only (
snapshot/press/fill).No
chrome.debuggerin v1 (no yellow infobar).Independent implementation. Do not copy another vendor's brand, marks, or reverse-engineered internals into this tree.
Layout
packages/shared protocol, snapshot grammar, target parser
packages/extension MV3 side panel + service worker
packages/host MCP + native host
packages/plugin Grok Build plugin (compatibility layer)Tests
pnpm --filter @chrome-actuator/shared testLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityFmaintenanceEnables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.20239MIT
- Alicense-qualityBmaintenanceEnables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.11MIT
- Flicense-qualityCmaintenanceDrive your real, signed-in Chrome browser from any MCP client, enabling browser automation such as navigation, clicking, typing, and screenshots through standard MCP tools.1
- Alicense-qualityAmaintenanceEnables AI assistants to control Chrome browser operations such as navigation, reading pages, taking screenshots, managing tabs, and more via a Chrome extension and native messaging.MIT
Related MCP Connectors
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Eyes and hands on real Windows PCs — observe, click, type via Glasswarp API.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xlreon/chrome-actuator'
If you have feedback or need assistance with the MCP directory API, please join our Discord server