$ loading_
Drive real local browsers across multiple sessions without cloud or API keys.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "apex-browser-mcp" yet — see the docs or source repo.
Use apex-browser-mcp to drive Chrome, Chromium, and WebKit to open the same page, record whether it loads correctly, and compare the behavior across the three engines.
A result summary for each browser session plus a comparison of differences.
Use apex-browser-mcp to attach to my currently running Chrome session, continue the page check there, and tell me whether the connection succeeded.
A connection status report and continued browser actions in the attached session.
Use apex-browser-mcp to create two local browser sessions, open the staging site in one and the production site in the other, then capture screenshots and label each session.
Execution results for two independent browser sessions and notes for each screenshot.
Developers or testers can directly drive real Chrome, Chromium, WebKit, and Safari locally to verify page behavior across engines. It fits testing workflows that do not want cloud services or API keys.
When an issue only reproduces in the current browser environment, users can attach to a running Chrome session and continue operating there. This helps avoid repeated sign-ins or environment reinitialization.
When multiple pages or environments need to be handled at once, users can control local browsers in parallel with multiple sessions. This is useful for comparing different sites, versions, or workflow states.
It is a local multi-session MCP server for driving real Chrome, Chromium, WebKit, and Safari browser engines. It also supports attaching to a running Chrome instance.
No. The description explicitly says it requires no API keys and no cloud services.
The provided material does not include installation steps, dependencies, or configuration details. Please see the source repository.
Control a headless local browser for navigation, interaction, screenshots, and debugging.
Automate browser tasks, capture console logs, and take screenshots for web workflows.
Control a real local browser for web automation, extraction, and screenshots.
Automate browser tasks, inspect pages, run scripts, and capture diagnostics.
Control your signed-in Chrome browser for web automation and screenshots via MCP.
Automate real browser tasks tab by tab while keeping the current session.