🤖 MCP Selenium Grid

Created By
Falamarcaoa year ago
(DO NOT USE, NOT READY) A Model Context Protocol (MCP) server that enables AI Agents to request and manage Selenium browser instances through a secure API. Perfect for your automated browser testing needs! 🚀
Overview

what is MCP Selenium Grid?

MCP Selenium Grid is a Model Context Protocol (MCP) server that allows AI Agents to request and manage Selenium browser instances through a secure API, designed for automated browser testing.

how to use MCP Selenium Grid?

To use MCP Selenium Grid, clone the repository, set up the environment with required dependencies, and start the server using the provided commands. You can also run tests using pytest.

key features of MCP Selenium Grid?

  • Secure API for managing Selenium browser instances
  • Easy setup with Docker and Kubernetes support
  • Automated testing capabilities with unit, integration, and end-to-end tests

use cases of MCP Selenium Grid?

  1. Automating browser testing for web applications.
  2. Managing multiple browser instances for parallel testing.
  3. Integrating with AI Agents for enhanced testing workflows.

FAQ from MCP Selenium Grid?

  • Is MCP Selenium Grid ready for production use?

No, it is currently not ready for production use as indicated in the project description.

  • What are the prerequisites for using MCP Selenium Grid?

You need to have uv, Docker, K3s, and kubectl installed to set up the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Falamarcao
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago