
Selenium Mcp
io.github.pshivaprPublished by GitHub account pshivaprv0.4.6Updated Oct 24, 2026
Selenium Tools for MCP
Overview
A local MCP server that exposes Selenium WebDriver so an assistant can drive real browsers: navigate pages, click and type, manage cookies and windows, and take
- What you can do
- Open, navigate, refresh, resize and close browser sessions, and read the current URL, title and page source across Chrome, Firefox, Safari and Edge. Find elements and interact with them: click, type, clear, hover, double-click, right-click, drag and drop, upload files, and read text or attributes. Manage cookies and windows, including switching between windows and frames. Run advanced actions such as JavaScript execution, screenshots, dropdown selection, key presses, scrolling and form submission. Check element state (displayed, enabled, selected) and wait for elements or page states.
- When to use it
- Useful when an assistant should perform real browser automation: end-to-end web testing, form filling, scraping pages that need a live browser, or generating Selenium test code from an observed flow.
- Requirements
- Runs locally over stdio, typically started with npx from the npm package. Needs Node.js 18 or higher and an installed browser (Chrome, Firefox, Safari or Edge); WebDrivers are managed automatically. The manifest declares an optional API key variable, though the README does not describe using one.
Installation
In SourceWeft
- Open Selenium Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[Add to Cursor] [Add to VS Code] [Add to Claude] [Add to ChatGPT] [Add to Codex] [Add to Gemini]
Selenium MCP Server
This is a server implementation that bridges the gap between MCP clients (AI assistants) and Selenium WebDriver. It exposes Selenium WebDriver's functionalities as MCP tools, allowing AI models to utilize them for tasks like:
- Browser management (launching, navigating, closing browsers)
- Element interaction (clicking, typing, finding elements)
- Web scraping and automated testing
- Advanced operations like screenshots, cookie management, and JavaScript execution
In essence, the selenium webdriver mcp setup allows AI assistants to leverage the power of Selenium Webdriver for web automation, by communicating with a dedicated Selenium MCP server via the Model Context Protocol. This facilitates tasks such as automated web interactions, testing, and data extraction, all controlled by AI.
[Image]🚀 Overview
A Model Context Protocol (MCP) server for Selenium that provides comprehensive Selenium WebDriver automation tools for AI assistants and applications. This server enables automated web browser interactions, testing, and scraping through a standardized interface.
Built with TypeScript and modern ES modules, it offers type-safe browser automation capabilities through the Model Context Protocol.
✨ Key Features
- Multi-Browser Support: Chrome, Firefox, Safari, and Edge browser automation
- Comprehensive Element Interaction: Click, type, hover, drag & drop, file uploads
- Advanced Navigation: Forward, backward, refresh, window management
- Wait Strategies: Intelligent waiting for elements and page states
- Type Safety: Full TypeScript implementation with Zod validation
🤝 Integration
MCP Client Integration
Configure your MCP client to connect to the Selenium server:
Standard Configuration (applicable to Windsurf, Warp, Gemini CLI etc)
Installation in VS Code
Update your mcp.json in VS Code with below configuration
NOTE: If you're new to MCP servers, follow this link Use MCP servers in VS Code
Example 'stdio' type connection
Example 'http' type connection
After installation, the Selenium MCP server will be available for use with your GitHub Copilot agent in VS Code.
To install the Selenium MCP server using the VS Code CLI
To install the package using either npm, or Smithery
Using npm:
Using Smithery
To install Selenium MCP for Claude Desktop automatically via [smithery badge]
Claude Desktop Integration
Add to your Claude Desktop configuration:
Screenshot
Prompts
An example prompt to start AI Agent interaction:
Using selenium mcp tools, navigate to <https://parabank.parasoft.com/> click the 'Register' link and signup using dynamic test data and click register. Then generate selenium tests in <YOUR_FAVOURITE_PROGRAMMING_LANGUAGE> using pom, create tests using cucumber features, steps and execute the tests.
Note: For more prompts, look at examples directory of the project
🛠️ MCP Available Tools
Browser Management Tools
Cookie Management Tools
Window Management Tools
Element Interaction Tools
Element State Validation Tools
Frame Management Tools
Advanced Action Tools
Scrolling Tools
Form Interaction Tools
Element Locator Strategies
id: Find by element IDcss: Find by CSS selectorxpath: Find by XPath expressionname: Find by name attributetag: Find by HTML tag nameclass: Find by CSS class name
📋 Requirements
- Node.js: Version 18.0.0 or higher
- Browsers: Chrome, Firefox, Safari, or Edge installed
- WebDrivers: Automatically managed by selenium-webdriver
- Operating System: Windows, macOS, or Linux
🚦 Development
Getting Started
Clone the repository
Install dependencies
Build the project
Running the Server
Production Mode
Development Mode (with auto-reload)
Direct Execution
Using as CLI Tool
After building, you can use the server as a global command:
📝 License
MIT License - see LICENSE file for details.
🤝 Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/AmazingFeature) - Commit your changes (
git commit -m 'Add some AmazingFeature') - Push to the branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Badges/Mentions
Built with ❤️ for the Model Context Protocol ecosystem
Source: README.md at commit bc06d84
Tools
0Version history
1- v0.4.6LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts