MCP server that bridges local apps with Selenix for browser automation.
Connect Claude Desktop to Selenix via the Model Context Protocol. Chat with Claude to create, run, debug, and manage browser automation tests — just like using the built-in AI Assistant, but powered by Claude. []( Selenix desktop app installed Claude Desktop installed Node.js 18 or later Before using any setup method below, enable the bridge inside Selenix: 2. Go to System Settings (gear icon in…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Connect Claude Desktop to Selenix via the Model Context Protocol. Chat with Claude to create, run, debug, and manage browser automation tests — just like using the built-in AI Assistant, but powered by Claude. []( Selenix desktop app installed Claude Desktop installed Node.js 18 or later Before using any setup method below, enable the bridge inside Selenix: 2. Go to System Settings (gear icon in the sidebar) 3. Scroll to the MCP Server section 4. Set Enable MCP Server to Yes This starts a local…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.