MCP server for browser automation with AI agent
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-runbook-ai-browser-agent": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for browser automation with AI agent
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
This server is missing a description.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser
Browser automation with Puppeteer for web scraping and testing
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP server for Firecrawl — search, scrape, and interact with the web. Supports both cloud and self-hosted instances. Features include web search, scraping, page interaction, batch processing, and LLM-powered content analysis.
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for io.github.runbook-ai/browser-agent and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server that provides browser automation capabilities through a Chrome extension. It allows terminal-based agents like Claude Code to interact with any website through your live browser session.
Part of the Runbook AI ecosystem. Join the Discord community to provide your feedback and get involved in the development!
https://github.com/user-attachments/assets/a43fba64-bc40-4ef6-9840-e100203e2cf5
Most browser-based MCP tools (like chrome-devtools-mcp) blow up your LLM context window by sending the entire DOM after every browser action.
Runbook AI is different:
eval() or shady scripts (enforced by the Chrome extension sandbox).Add to your MCP settings configuration:
{
"mcpServers": {
"runbook-ai": {
"command": "npx",
"args": ["-y", "runbook-ai-mcp@latest"]
}
}
}
Install the Runbook AI extension from Chrome Web Store.
Enable MCP in the extension settings opened from extension side panel.
Set LLM API key, and model name, base URL. Use of Gemini 3 Flash (gemini-3-flash-preview) is recommended. Get your free API key from Google AI Studio.
By default the extension has access to all websites. If you want to limit the access, go to Chrome Extension Details, and add individual sites to Site access setting.
Open Chrome and keep the extension side panel open.
Start the MCP server (it will automatically start when invoked by your MCP client).
The server exposes a single tool:
browser-agentRun a task in Chrome browser with AI and automation capabilities.
Parameters:
prompt (string, required): The task prompt for the AI agent to executeExample:
{
"name": "browser-agent",
"arguments": {
"prompt": "Go to google.com and search for 'MCP protocol'"
}
}
# Install dependencies
npm install
# Build
npm run build
# Run in development mode
npm run dev
# Run tests
npm test
When a tool is invoked:
Contributions are welcome! Feel free to send out a PR.