Selenix MCP Server
Run browser automation from your agent via Selenix so you can exercise flows and regressions without maintaining a separate test runner UI.
Overview
Selenix-MCP-Server is an MCP server for the Ship phase that connects local agents to Selenix for browser automation and testing workflows.
What is this MCP server?
- @selenix/mcp-server on npm (v1.0.7) with stdio transport
- Bridges local MCP clients to Selenix for browser automation
- YOUR_API_KEY env for authenticated Selenix access
- Web automation MCP, not a static scraper-only script
What problem does it solve?
E2E browser checks stall when only humans can drive the UI or when Selenium scripts live outside the agent toolchain.
Who is it for?
Builders shipping web apps who want MCP-driven browser sessions during test and launch prep.
Skip if: Pure API backends with no UI, or teams that ban cloud/browser automation for compliance reasons.
What do I get? / Deliverables
After install, your agent can invoke Selenix-backed browser automation tools over MCP for release and regression checks.
- MCP tools that drive Selenix browser sessions
- Agent-assisted smoke and regression runs
- Bridge from local dev agent to hosted browser automation
Recommended MCP Servers
Journey fit
Canonical shelf is Ship because browser automation is most valuable when verifying releases, E2E paths, and UI regressions before and after deploy. Testing subphase fits MCP bridges that drive real browsers for checks beyond unit tests.
How it compares
Selenium-class browser automation MCP, not a filesystem or database devtools server.
Common Questions / FAQ
Who is Selenix-MCP-Server for?
Solo developers and small teams using MCP agents who need Selenix-powered browser automation for staging and E2E validation.
When should I use Selenix-MCP-Server?
Use it in Ship/testing when you need the agent to open browsers, walk critical user flows, or debug UI behavior against real pages.
How do I add Selenix-MCP-Server to my agent?
Install @selenix/mcp-server from npm, set YOUR_API_KEY, add the stdio MCP server entry in Claude Code or Cursor config, and point sessions at your test URLs.