Browser Automation MCP Server
Click on "Deploy 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., "@Browser Automation MCP ServerCompare the visual layout of https://example.com and https://staging.example.com"
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.
Browser Automation MCP Server
This TypeScript project spins up a Model Context Protocol (MCP) server that exposes three tooling primitives tailored for automation: browser-driven flows, API health checks, and visual comparisons. It listens on STDIO, so any MCP-aware agent (Claude, Cursor, LangChain, etc.) can start the Node process and negotiate tools/list + tools/call automatically.
Setup
npm installnpm run build
Related MCP server: QA Testing MCP Server
Running the server
Execute npm run start (or node build/server.js directly). The server already binds to STDIO, so configure your MCP client to launch the same command and keep the subprocess running while the agent is issuing tool requests.
Tool catalogue
Tool | Description | Inputs | Outputs |
| Navigates a Chromium tab, runs scripted actions (click/fill/assert), and optionally returns a final screenshot. |
|
|
| Hits any HTTP endpoint to verify status and capture response snippets. |
| HTTP |
| Captures two pages at the same viewport and runs pixelmatch to flag visual regressions. |
| Pixel mismatch ratio, diff image (base64 PNG), baseline dimensions. |
Example tool call payloads
Browser automation
{
"url": "https://example.com/login",
"actions": [
{"type": "fill", "selector": "#username", "value": "test"},
{"type": "fill", "selector": "#password", "value": "secret"},
{"type": "click", "selector": "#submit"},
{"type": "waitForSelector", "selector": "#welcome"}
],
"finalScreenshot": true
}Image comparison
{
"baselineUrl": "https://example.com/home?baseline=1",
"targetUrl": "https://example.com/home?baseline=2",
"threshold": 0.04
}Debugging & exploration
Use the MCP Inspector to validate the server before wiring it to a client. Run npx @modelcontextprotocol/inspector node build/server.js, open the Inspector UI, and review the tools tab, send sample arguments, and inspect logs. The Inspector also proxies your server so you can replicate production-style connections locally.
This server cannot be deployed
Maintenance
Related MCP Connectors
Browser-based QA for AI-built software. Test pages with real browsers via agents.
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
Web search, browser automation, scraping, crawling and CAPTCHA solving for AI agents.
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to perform automated web testing by controlling a Chrome browser to navigate, interact with pages, capture screenshots, extract console logs, and simulate mobile devices for responsive design testing.7-
- FlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive web application testing including visual, functional, performance, accessibility, and SEO analysis using browser automation without requiring API keys.7-
- AlicenseNot gradedqualityCmaintenanceProvides 66 tools for browser automation using Selenium WebDriver, enabling AI agents to navigate, interact, capture screenshots, assert conditions, manage cookies, handle tabs, execute HTTP requests, record sessions, and more.12 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to capture screenshots, scrape structured page content, and run automated visual checks on live websites via a headless Chromium browser.3MIT