-
securityA
license-
qualityEnables browser automation using the Selenium WebDriver through MCP, supporting browser management, element location, and both basic and advanced user interactions.
Last updated a month ago
663
374
MIT
Why this server?
This server directly enables browser automation using the Selenium WebDriver, which is a perfect fit for 'pure Selenium'.
Why this server?
This is a 'TypeScript implementation of an MCP server' and provides tools for 'browser automation', directly matching both 'TypeScript' and the functionality of Selenium.
Why this server?
This server bridges Claude Desktop with Selenix for 'browser automation and testing', making it highly relevant to Selenium's purpose.
Why this server?
This server automatically generates 'TypeScript Page Object classes' and Cypress test suites, which aligns with 'TypeScript' and browser automation/testing, even if it uses Cypress instead of Selenium.
Why this server?
This server provides 'advanced browser automation capabilities', which is the primary function of Selenium, allowing control and interaction with browsers.
Why this server?
This is a 'powerful MCP server for browser automation' using Playwright and Chrome DevTools Protocol, offering similar capabilities to Selenium for web automation tasks.
Why this server?
This server enables 'AI-powered browser automation' using Playwright across multiple browsers, providing a modern alternative to Selenium for similar use cases.
Why this server?
This Chrome DevTools Protocol MCP server enables 'direct browser automation with auto-discovery of interactive elements', which is a fundamental aspect of Selenium-like tools.
Why this server?
Based on Puppeteer and Chrome DevTools Protocol, this server focuses on 'advanced browser debugging' and interaction, which is a core part of working with browser automation tools like Selenium.