← Back to directory

Selenium MCP Server

Community

MCP server for Selenium WebDriver – browser automation for AI agents.

GitHub source repository ↗

★ 425 Stars Category · Browser Popular Source revision 363ecf0f7195

52FMRS · D

Reliability

6/20

Security and permissions

8/20

Maintenance

8/20

Documentation

16/20

Setup experience

14/20

This MCP server provides a comprehensive set of browser automation tools, supporting major browsers, and can be invoked by AI agents via natural language. It's community-maintained, not official, but well-documented and easy to install. Best for developers and testers; be aware of potential security risks and website detection. No official client list is provided, but generic configuration is supported.

Read the FMRS scoring method →

This is a Model Context Protocol (MCP) server that wraps Selenium WebDriver, enabling AI agents to control browsers through natural language instructions, performing navigation, clicks, input, screenshots, and more. It supports Chrome, Firefox, Edge, and Safari. No manual scripting is needed; agents can call the APIs to complete automation tasks.

Tools

start_browser

Launches a browser session.

navigate

Navigates to a URL.

interact

Performs a mouse action (click, double-click, right-click, hover) on an element.

send_keys

Types text into an element, clearing the field first.

get_element_text

Gets the text content of an element.

get_element_attribute

Gets an attribute value from an element.

press_key

Presses a keyboard key.

upload_file

Uploads a file via a file input element.

take_screenshot

Captures a screenshot of the current page.

close_session

Closes the current browser session.

execute_script

Executes JavaScript in the browser for advanced interactions.

window

Manages browser windows and tabs.

frame

Switches focus to a frame or back to the main page.

alert

Handles browser alert, confirm, or prompt dialogs.

add_cookie

Adds a cookie.

get_cookies

Gets cookies.

delete_cookie

Deletes cookies.

diagnostics

Gets browser diagnostics captured via WebDriver BiDi (console, errors, network).

Setup

Installation steps:

Goose (Desktop): Paste in browser address bar: goose://extension?cmd=npx&arg=-y&arg=%40angiejones%2Fmcp-selenium%40latest&id=selenium-mcp&name=Selenium%20MCP&description=automates%20browser%20interactions.
Goose (CLI): Run goose session --with-extension "npx -y @angiejones/mcp-selenium@latest".
Claude Code: Run claude mcp add selenium -- npx -y @angiejones/mcp-selenium@latest.
For Cursor, Windsurf, etc.: Add config {"mcpServers":{"selenium":{"command":"npx","args":["-y","@angiejones/mcp-selenium@latest"]}}}.
Via Smithery: npx -y @smithery/cli install @angiejones/mcp-selenium --client claude.
Global install: npm install -g @angiejones/mcp-selenium, then run mcp-selenium.

claude_desktop_config.json

{"mcpServers":{"selenium":{"command":"npx","args":["-y","@angiejones/mcp-selenium@latest"]}}}

Generate and validate client config

Fit and risk

Best for

Developers and testers who want AI-assisted browser automation.
Scenarios requiring headless browsers for integration testing or crawling.
Users who prefer natural language commands over manual scripting.
Teams already using Selenium and looking to integrate AI agents.

Not for

Not suitable for scenarios requiring fine-grained control over browser internals (though execute_script exists).
Not suitable for tasks that don't need browser automation, like pure API testing.
Not ideal for production environments requiring official support or enterprise guarantees, as it's community-maintained.
Safari users need extra setup and lack headless mode, which may not fit all automation needs.

Required permissions

Network access to download browser drivers and communicate with browsers.
Local filesystem access for file uploads and screenshot saves.
Potential system permissions (e.g., `sudo safaridriver --enable`).
Execution permissions to run npx commands.

Risks and side effects

Browser automation may be detected by websites, leading to IP bans or ToS violations.
Headless mode can be recognized by some sites, affecting test validity.
The server itself is not malicious, but executing arbitrary JavaScript via execute_script poses security risks if the agent is instructed maliciously.
Dependency on npx may download unspecified versions, introducing supply chain risks.
Misuse could accidentally submit forms, delete data, or perform destructive actions.
Safari configuration requires admin privileges, which may modify system settings.

Troubleshooting

Ensure Chrome or Firefox is installed and chromedriver is on PATH (for tests).
If Safari fails to launch, run `sudo safaridriver --enable` and enable 'Allow Remote Automation' in Safari settings.
Check that the npx command resolves the package; consider pinning a version.
If browser fails to start, check firewall or proxy blocking.
Review returned errors to verify parameters (locator strategy, timeouts).
Check server logs in the MCP client for connection status.

Use cases

Ask an AI agent to open Chrome, navigate to a URL, and take a screenshot.

Automate data extraction from web pages, such as getting texts and attributes.

Run cross-browser tests to verify web app behavior.

Handle authenticated sessions and cookie management.

Run headless automation for continuous testing or scraping.

Supported clients

GooseFull support

Claude CodeFull support

CursorFull support

WindsurfFull support

Related MCP servers

Compare with other MCP servers