An MCP server that uses Selenium to interact with a WebDriver instance.
If you want an AI assistant working directly with Selenium, the selenium mcp server is the bridge. An MCP server that uses Selenium to interact with a WebDriver instance.
An MCP server that uses Selenium to interact with a WebDriver instance. Built using the MCP-Server-Starter template.
This server allows AI agents to control a web browser session via Selenium WebDriver, enabling tasks like web scraping, automated testing, and form filling through the Model Context Protocol.
Once connected, the assistant can call these 6 tools directly:
selenium_navigate — Navigates the browser to a specific URLselenium_findElement — Finds an element on the page using a CSS selectorselenium_click — Clicks an elementselenium_sendKeys — Sends keystrokes to an elementselenium_getPageSource — Retrieves the current page source HTMLDebugging — Use the MCP Inspector or standard Node.js debugging techniquesSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Browser automation servers are the ones people reach for when a site has no API — the assistant drives a real page instead of guessing at endpoints. Selenium sits in that group, and the shape of its toolset — selenium_navigate, selenium_findElement, selenium_click among others — tells you what it is really for. Worth comparing against the other browser automation servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| selenium_navigate | Navigates the browser to a specific URL. |
| selenium_findElement | Finds an element on the page using a CSS selector. |
| selenium_click | Clicks an element. |
| selenium_sendKeys | Sends keystrokes to an element. |
| selenium_getPageSource | Retrieves the current page source HTML. |
| Debugging | Use the MCP Inspector or standard Node.js debugging techniques. |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.