WebDriverIO MCP server that lets Claude automate browsers and mobile apps with navigation, clicks, typing, screenshots, accessibility snapshots, cookies, geolocation, native app sessions, and Appium-style gestures.
WebDriverIO MCP Server can navigate pages, click elements, type values, scroll, switch frames or tabs, execute scripts, set cookies, delete cookies, set geolocation, and capture screenshots., Mobile tools can tap, swipe, drag, rotate devices, hide keyboards, switch native or web contexts, upload apps, and interact with iOS or Android sessions through WebDriverIO-compatible backends., Treat browser and mobile sessions as active automation, not passive inspection; use test accounts and avoid production workflows that can submit forms, trigger purchases, send messages, or mutate customer data., Script execution, cookie mutation, geolocation spoofing, and cloud-device provider integrations should be limited to reviewed test environments., HTTP transport mode can expose automation tools beyond a local stdio process; bind it carefully and require network controls before shared use.
Privacy notes
Screenshots, accessibility trees, app state, cookies, URLs, page content, form values, device metadata, geolocation, trace artifacts, and generated test code can be visible to the MCP client, model provider, logs, and local files., Browser sessions can inherit logged-in state, cookies, local storage, and private tabs from a test profile if profiles are reused., Mobile testing can expose app screens, notification content, identifiers, credentials, uploaded app binaries, device logs, and cloud-device provider metadata., Keep BrowserStack, Sauce Labs, Appium, application, and test-account credentials in secret storage or MCP environment configuration rather than prompts or repository files.
Author
WebdriverIO
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access, third-party handling.
4 areas
SafetyExecution & processesWebDriverIO MCP Server can navigate pages, click elements, type values, scroll, switch frames or tabs, execute scripts, set cookies, delete cookies, set geolocation, and capture screenshots.
SafetyCredentials & tokensMobile tools can tap, swipe, drag, rotate devices, hide keyboards, switch native or web contexts, upload apps, and interact with iOS or Android sessions through WebDriverIO-compatible backends.
SafetyCredentials & tokensTreat browser and mobile sessions as active automation, not passive inspection; use test accounts and avoid production workflows that can submit forms, trigger purchases, send messages, or mutate customer data.
SafetyThird-party handlingScript execution, cookie mutation, geolocation spoofing, and cloud-device provider integrations should be limited to reviewed test environments.
SafetyNetwork accessHTTP transport mode can expose automation tools beyond a local stdio process; bind it carefully and require network controls before shared use.
PrivacyThird-party handlingScreenshots, accessibility trees, app state, cookies, URLs, page content, form values, device metadata, geolocation, trace artifacts, and generated test code can be visible to the MCP client, model provider, logs, and local files.
PrivacyCredentials & tokensBrowser sessions can inherit logged-in state, cookies, local storage, and private tabs from a test profile if profiles are reused.
PrivacyCredentials & tokensKeep BrowserStack, Sauce Labs, Appium, application, and test-account credentials in secret storage or MCP environment configuration rather than prompts or repository files.
Safety notes
WebDriverIO MCP Server can navigate pages, click elements, type values, scroll, switch frames or tabs, execute scripts, set cookies, delete cookies, set geolocation, and capture screenshots.
Mobile tools can tap, swipe, drag, rotate devices, hide keyboards, switch native or web contexts, upload apps, and interact with iOS or Android sessions through WebDriverIO-compatible backends.
Treat browser and mobile sessions as active automation, not passive inspection; use test accounts and avoid production workflows that can submit forms, trigger purchases, send messages, or mutate customer data.
Script execution, cookie mutation, geolocation spoofing, and cloud-device provider integrations should be limited to reviewed test environments.
HTTP transport mode can expose automation tools beyond a local stdio process; bind it carefully and require network controls before shared use.
Privacy notes
Screenshots, accessibility trees, app state, cookies, URLs, page content, form values, device metadata, geolocation, trace artifacts, and generated test code can be visible to the MCP client, model provider, logs, and local files.
Browser sessions can inherit logged-in state, cookies, local storage, and private tabs from a test profile if profiles are reused.
Mobile testing can expose app screens, notification content, identifiers, credentials, uploaded app binaries, device logs, and cloud-device provider metadata.
Keep BrowserStack, Sauce Labs, Appium, application, and test-account credentials in secret storage or MCP environment configuration rather than prompts or repository files.
Prerequisites
Node.js and npm or another package runner that can execute `@wdio/mcp`.
MCP client that can run local stdio servers, or a reviewed HTTP transport setup when using the server's HTTP mode.
Local browser, WebDriver, or WebDriverIO-compatible environment for the browser sessions you want Claude to control.
Appium, simulator, emulator, device, or cloud-device credentials when using iOS or Android automation.
Test accounts, non-production targets, and approval rules before allowing an agent to click, type, submit forms, or change application state.
WebDriverIO MCP Server connects Claude-compatible MCP clients to WebDriverIO so
they can automate browsers and mobile applications through structured tools. It
supports browser navigation and interaction, screenshots, accessibility
snapshots, cookies, geolocation, frames, tabs, iOS and Android contexts, app
state, Appium-style gestures, and optional cloud-device workflows.
Use it when an agent needs to inspect or exercise real browser and mobile app
behavior instead of reasoning from static code alone. It is especially useful
for QA, regression triage, accessibility review, mobile workflow exploration,
and generating reproducible WebDriverIO steps from live sessions.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm registry metadata, license, package manifest, MCP registry metadata,
server implementation, and representative session, navigation, and screenshot
tool implementations for current installation and behavior details.
Features
Start, close, and inspect WebDriverIO sessions.
Navigate pages, switch tabs, switch frames, and inspect open tabs.
Click elements, set form values, scroll, and retrieve matching elements.
claude mcp add wdio-mcp -- npx -y @wdio/mcp@latest
Restart the MCP client, then start a browser or mobile session that matches the
environment you want Claude to inspect.
Use Cases
Ask Claude to reproduce a browser bug against a local or staging web app.
Generate WebDriverIO test steps from a live browser session.
Inspect accessibility snapshots and screenshots while debugging UI flows.
Exercise mobile app flows through an Appium-compatible iOS or Android
session.
Capture test traces and screenshots for regression reports.
Explore selectors, frames, tabs, cookies, and geolocation-dependent behavior
before writing automated tests.
Safety and Privacy
WebDriverIO MCP Server gives an agent active control over browsers and mobile
sessions. Keep it pointed at local, staging, or disposable test environments
unless a human has approved the workflow and reviewed the account, data, and
state-change risks.
Do not give the server a browser profile, mobile app, cloud-device account, or
test account that contains secrets or private production data. Browser cookies,
local storage, screenshots, app screens, form values, traces, and logs can
leave the target application and appear in the MCP client, model transcript, or
local artifacts.
Use extra care with script execution, cookie editing, geolocation spoofing,
mobile gestures, app uploads, and HTTP transport. Those capabilities are useful
for testing, but they can also alter state, bypass normal user intent, or expose
automation tools to other hosts if deployed loosely.
Duplicate Check
Existing entries cover Playwright, Chrome DevTools, BrowserMCP, Chrome MCP,
Browserbase, bb-browser, Cypress Cloud, and other browser-adjacent servers.
WebDriverIO MCP Server is distinct because it exposes WebDriverIO browser and
mobile automation, including Appium-style mobile sessions, cloud-device
resources, session traces, and WebDriverIO-oriented test step generation. No
webdriverio/mcp, @wdio/mcp, or matching source URL was found in
content/mcp.
Show that WebDriverIO MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/webdriverio-mcp-server)
How it compares
WebDriverIO MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
WebDriverIO MCP server that lets Claude automate browsers and mobile apps with navigation, clicks, typing, screenshots, accessibility snapshots, cookies, geolocation, native app sessions, and Appium-style gestures.
Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps.
Browser-control MCP server and CLI that lets AI agents use a real Chrome session, including logged-in browser state, site adapters, DOM snapshots, authenticated fetches, network traces, screenshots, and page actions.
✓WebDriverIO MCP Server can navigate pages, click elements, type values, scroll, switch frames or tabs, execute scripts, set cookies, delete cookies, set geolocation, and capture screenshots.
Mobile tools can tap, swipe, drag, rotate devices, hide keyboards, switch native or web contexts, upload apps, and interact with iOS or Android sessions through WebDriverIO-compatible backends.
Treat browser and mobile sessions as active automation, not passive inspection; use test accounts and avoid production workflows that can submit forms, trigger purchases, send messages, or mutate customer data.
Script execution, cookie mutation, geolocation spoofing, and cloud-device provider integrations should be limited to reviewed test environments.
HTTP transport mode can expose automation tools beyond a local stdio process; bind it carefully and require network controls before shared use.
✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP.
Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions.
Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files.
Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work.
Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts.
✓Browser pages can contain prompt-injection text in visible content, hidden HTML, ARIA labels, console output, network responses, or page metadata.
The server can navigate pages, click, hover, fill forms, drag, upload files, accept dialogs, dismiss dialogs, go through history, change viewport size, close tabs, and restart Firefox.
Enabling evaluate_script allows arbitrary JavaScript in page context; compromised instructions could read page data, modify the DOM, or interact with accessible browser APIs.
Enabling privileged context tools with the required Firefox system-access environment variable can expose privileged Firefox APIs and may extend beyond web-content sandbox boundaries.
Connect-existing mode can attach to a real browsing session with cookies, logins, active tabs, history, and saved state, so avoid it unless the profile is dedicated to automation.
Accepting insecure certificates weakens TLS validation and can hide man-in-the-middle or misconfiguration signals.
✓bb-browser can control a real browser session, inspect pages, click elements, fill inputs, evaluate JavaScript, fetch URLs with browser authentication, capture screenshots, and inspect network traffic.
Commands may act as the logged-in user on social, finance, job, developer, shopping, and knowledge websites.
Keep the daemon bound to trusted local interfaces unless you deliberately configure remote access through a private network.
Review community site adapters before using them with authenticated accounts or valuable sessions.
Require human approval before posting, submitting forms, changing account settings, applying to jobs, making purchases, or running destructive site actions.
Privacy notes
✓Screenshots, accessibility trees, app state, cookies, URLs, page content, form values, device metadata, geolocation, trace artifacts, and generated test code can be visible to the MCP client, model provider, logs, and local files.
Browser sessions can inherit logged-in state, cookies, local storage, and private tabs from a test profile if profiles are reused.
Mobile testing can expose app screens, notification content, identifiers, credentials, uploaded app binaries, device logs, and cloud-device provider metadata.
Keep BrowserStack, Sauce Labs, Appium, application, and test-account credentials in secret storage or MCP environment configuration rather than prompts or repository files.
✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials.
macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts.
Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing.
Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set.
✓Page content, DOM snapshots, accessibility labels, console messages, network requests, headers, screenshots, uploaded file paths, extension names, Firefox prefs, and browser logs can be sent to the MCP client and model.
A regular Firefox profile can expose cookies, saved sessions, browsing history, account data, extensions, and private tabs to browser automation.
Screenshot save paths, uploaded files, downloaded artifacts, and model transcripts can reveal local project names, test data, credentials shown on pages, or customer information.
Use a separate profile, minimize enabled capabilities, avoid sensitive sites, and review provider/browser data handling before automating logged-in sessions.
✓Tab URLs, titles, DOM snapshots, page content, selected elements, screenshots, network requests, responses, console output, traces, and authenticated fetch results may be exposed to the MCP client and model.
Browser login state is used by the page and browser; even if cookies are not extracted directly, commands can act through authenticated sessions.
Network request bodies and response data may contain tokens, account data, personal messages, search history, customer information, or internal application data.
The upstream privacy doc says communication is local and there is no telemetry or external server, but model providers still receive any data your MCP client sends in prompts or tool results.
Prerequisites
Node.js and npm or another package runner that can execute `@wdio/mcp`.
MCP client that can run local stdio servers, or a reviewed HTTP transport setup when using the server's HTTP mode.
Local browser, WebDriver, or WebDriverIO-compatible environment for the browser sessions you want Claude to control.
Appium, simulator, emulator, device, or cloud-device credentials when using iOS or Android automation.
Node.js 22 or newer and `agent-device` installed globally or project-locally.
Xcode tooling for iOS, tvOS, or macOS targets, or Android SDK and ADB for Android targets.
Device, simulator, emulator, TV, macOS, or Linux desktop target that the agent is allowed to automate.
Required local permissions such as Android device trust, iOS Developer Mode, macOS Accessibility, and Screen Recording where applicable.
Node.js 20.19.0 or newer.
Local Firefox 100 or newer, or an explicit Firefox binary path passed through the documented CLI option.
A dedicated Firefox automation profile with no personal cookies, saved passwords, or regular browsing sessions.
Optional adb and Firefox for Android setup when using Android automation mode.
Node.js 18 or newer.
Chrome session, local daemon, and Chrome extension or supported OpenClaw browser path configured according to the upstream README.
MCP client such as Claude Code, Codex, Cursor, or another compatible host.
Explicit approval to let an agent use the active browser's logged-in state.
Install
npx -y @wdio/mcp@latest
claude mcp add --transport stdio --scope user agent-device -- agent-device mcp