Ermöglicht es AI-Assistenten, Webbrowser, lokale Electron-Anwendungen sowie mobile Apps auf iOS und Android zu automatisieren.
Auch bekannt als webdriverio/mcp, @wdio/mcp
- Stars
- 44
- Tools
- 42
- Downloads, 30 Tage
- —
- Neueste Version
- 4.1.0
- Letzter Commit
- 14. Nov. 2026
- Lizenz
- MIT
Was ist WebDriverIO MCP?
WebDriverIO ist ein MCP server. Ermöglicht es AI-Assistenten, Webbrowser, lokale Electron-Anwendungen sowie mobile Apps auf iOS und Android zu automatisieren. Er stellt 42 Tools bereit, etwa upload_app, list_apps, enable_tools.
Zusammenfassung generiert aus dem README des Projekts
Über WebDriverIO MCP server
Die Automatisierung von Webbrowsern, mobilen Anwendungen und lokalen Electron-Apps ist mit diesem MCP server möglich. Er bietet eine einheitliche Schnittstelle, damit AI-Assistenten mit Chrome, Firefox, Edge und Safari sowie mit iOS- und Android-Geräten interagieren können. Entwickler können ihn nutzen, um Tests in lokalen Umgebungen durchzuführen oder sich mit Cloud-Providern wie BrowserStack, Sauce Labs, LambdaTest, TestingBot und Digital.ai Testing zu verbinden.
Um diesen Server zu nutzen, kannst du ihn via npx oder als globales npm package installieren. Er verwendet primär stdio transport für Subprocess-Clients, unterstützt aber auch HTTP transport auf einem angegebenen Port für Clients, die keine Subprozesse starten können. Für die mobile Automatisierung ist ein lokaler Appium server sowie spezifische Platform-Driver wie xcuitest für iOS oder uiautomator2 für Android erforderlich. Für Cloud-basiertes Testing musst du Zugangsdaten wie Benutzernamen und Access Keys über Umgebungsvariablen oder deine Client-Config bereitstellen.
Was du damit machen kannst
- 1Webbrowser-Testing automatisierenSteuere eine AI an, um Aktionen in verschiedenen Webbrowsern wie Chrome oder Safari auszuführen.
- 2Mobile Anwendungen testenWeise eine AI an, automatisierte Workflows auf iOS-Simulatoren oder Android-Emulatoren auszuführen.
- 3Tests in der Cloud ausführenFühre automatisierte Browser- und Mobile-Sessions auf Remote-Realgeräten über Cloud-Services aus.
- 4Mit lokalen Desktop-Apps interagierenNutze einen AI-Assistenten, um lokale, auf Electron basierende Softwareanwendungen zu steuern.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du WebDriverIO MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenWebDriverIO MCP in Claude Code installieren
$ claude mcp add mcp -- npx -y @wdio/mcpWebDriverIO MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@wdio/mcp"]}'WebDriverIO MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP in Codex installieren
$ codex mcp add mcp -- npx -y @wdio/mcpWebDriverIO MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@wdio/mcp"]
WebDriverIO MCP in Gemini CLI installieren
$ gemini mcp add -s user mcp npx -- -y @wdio/mcpWebDriverIO MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP tools 42
Erkannt aus dem READMEupload_applist_appsenable_toolsstart_sessionattach_sessionlaunch_chromeclose_sessionemulate_deviceopen_web_extensionnavigatesnapshotget_elements
| upload_app | — | |
| list_apps | — | |
| enable_tools | — | |
| start_session | — | |
| attach_session | — | |
| launch_chrome | — | |
| close_session | — | |
| emulate_device | — | |
| open_web_extension | — | |
| navigate | — | |
| snapshot | — | |
| get_elements | — |
Alle 42 Tools anzeigenWeniger Tools anzeigen
get_accessibility_treeget_screenshotget_tabsscrollexecute_scriptexecute_electron_scripttrigger_electron_deeplinkmockget_mock_callsmanage_mockswitch_tabswitch_frameclick_elementset_valueselect_optionpress_keyperform_actionsget_cookiesset_cookiedelete_cookiestap_elementswipedrag_and_dropget_contextsswitch_contextget_app_staterotate_devicehide_keyboardset_geolocationquery_docs
| get_accessibility_tree | — | |
| get_screenshot | — | |
| get_tabs | — | |
| scroll | — | |
| execute_script | — | |
| execute_electron_script | — | |
| trigger_electron_deeplink | — | |
| mock | — | |
| get_mock_calls | — | |
| manage_mock | — | |
| switch_tab | — | |
| switch_frame | — | |
| click_element | — | |
| set_value | — | |
| select_option | — | |
| press_key | — | |
| perform_actions | — | |
| get_cookies | — | |
| set_cookie | — | |
| delete_cookies | — | |
| tap_element | — | |
| swipe | — | |
| drag_and_drop | — | |
| get_contexts | — | |
| switch_context | — | |
| get_app_state | — | |
| rotate_device | — | |
| hide_keyboard | — | |
| set_geolocation | — | |
| query_docs | — |
Konfiguration
BROWSERSTACK_ACCESS_KEYBROWSERSTACK_USERNAMEDIGITALAI_ACCESS_KEYDIGITALAI_CLOUD_URLSAUCE_ACCESS_KEYSAUCE_USERNAMETESTINGBOT_KEYTESTINGBOT_SECRETTESTMU_ACCESS_KEYTESTMU_USERNAME
| Name | Beschreibung | Typ |
|---|---|---|
| BROWSERSTACK_ACCESS_KEY | — | |
| BROWSERSTACK_USERNAME | — | |
| DIGITALAI_ACCESS_KEY | — | |
| DIGITALAI_CLOUD_URL | — | |
| SAUCE_ACCESS_KEY | — | |
| SAUCE_USERNAME | — | |
| TESTINGBOT_KEY | — | |
| TESTINGBOT_SECRET | — | |
| TESTMU_ACCESS_KEY | — | |
| TESTMU_USERNAME | — |
Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertNicht geprüft
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehenWebDriverIO MCP Server
A Model Context Protocol (MCP) server that enables AI assistants to interact with web browsers, local Electron applications, and mobile applications using WebdriverIO. Automate Chrome, Firefox, Edge, Safari, Electron, iOS, and Android through a unified interface.
Installation
Add the following configuration to your MCP client settings:
Standard config (works in most clients):
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp@latest"
]
}
}
}
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS),
%APPDATA%\Claude\claude_desktop_config.json (Windows), or ~/.config/Claude/claude_desktop_config.json (Linux):
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp@latest"
]
}
}
}
claude mcp add wdio-mcp -- npx -y @wdio/mcp@latest
Add to your VS Code settings.json or cline_mcp_settings.json file:
{
"mcpServers": {
"wdio-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wdio/mcp@latest"
]
}
}
}
Go to Cursor Settings → MCP → Add new MCP Server, or create .cursor/mcp.json:
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp@latest"
]
}
}
}
Use the Codex CLI:
codex mcp add wdio-mcp npx "@wdio/mcp@latest"
Or edit ~/.codex/config.toml:
[mcp_servers.wdio-mcp]
command = "npx"
args = ["@wdio/mcp@latest"]
Go to Advanced settings → Extensions → Add custom extension, or run:
goose configure
Or edit ~/.config/goose/config.yaml:
extensions:
wdio-mcp:
name: WebDriverIO MCP
cmd: npx
args: [ -y, "@wdio/mcp@latest" ]
enabled: true
type: stdio
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp@latest"
]
}
}
}
Edit Zed settings (~/.config/zed/settings.json):
{
"context_servers": {
"wdio-mcp": {
"source": "custom",
"command": "npx",
"args": [
"-y",
"@wdio/mcp@latest"
]
}
}
}
code --add-mcp '{"name":"wdio-mcp","command":"npx","args":["-y","@wdio/mcp@latest"]}'
⚠️ Restart Required: After adding the configuration, fully restart your MCP client to apply the changes.
Option 2: Global Installation
If you prefer to install globally:
npm install -g @wdio/mcp
Then use wdio-mcp as the command:
{
"mcpServers": {
"wdio-mcp": {
"command": "wdio-mcp"
}
}
}
📖 Need help? Follow the MCP install guide.
HTTP Transport (for non-subprocess clients)
By default the server uses stdio (subprocess) transport. For clients that cannot launch subprocesses (e.g. llama.cpp, OpenAI Codex secure mode), enable HTTP transport:
npx @wdio/mcp --http --port 3000
| Flag | Default | Description |
|---|---|---|
--http |
— | Enable HTTP transport mode |
--port |
3000 |
Port to listen on |
--allowedHosts |
localhost,127.0.0.1,::1 |
Allowed Host header values (DNS rebinding protection) |
--allowedOrigins |
(none — browser clients blocked) | Allowed Origin values for CORS. Use * to allow all. |
Then point your MCP client at http://localhost:3000/mcp.
Prerequisites For Mobile App Automation
- Appium Server: Install globally with
npm install -g appium - Platform Drivers:
- iOS:
appium driver install xcuitest(requires Xcode on macOS) - Android:
appium driver install uiautomator2(requires Android Studio)
- iOS:
- Devices/Emulators:
- iOS Simulator (macOS) or physical device
- Android Emulator or physical device
- For iOS Real Devices: You'll need the device's UDID (Unique Device Identifier)
- Find UDID on macOS: Connect device → Open Finder → Select device → Click device name/model to reveal UDID
- Find UDID on Windows: Connect device → iTunes or Apple Devices app → Click device icon → Click "Serial Number" to reveal UDID
- Xcode method: Window → Devices and Simulators → Select device → UDID shown as "Identifier"
Start the Appium server before using mobile features:
appium
# Server runs at http://127.0.0.1:4723 by default
Cloud Providers
Run browser and mobile app tests on cloud real devices and browsers without any local setup. Currently supports BrowserStack, Sauce Labs, LambdaTest, TestingBot, and Digital.ai Testing.
Prerequisites
Set your provider credentials as environment variables or in your MCP client config:
export BROWSERSTACK_USERNAME=your_username
export BROWSERSTACK_ACCESS_KEY=your_access_key
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": ["-y", "@wdio/mcp@latest"],
"env": {
"BROWSERSTACK_USERNAME": "your_username",
"BROWSERSTACK_ACCESS_KEY": "your_access_key"
}
}
}
}
export SAUCE_USERNAME=your_username
export SAUCE_ACCESS_KEY=your_access_key
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": ["-y", "@wdio/mcp@latest"],
"env": {
"SAUCE_USERNAME": "your_username",
"SAUCE_ACCESS_KEY": "your_access_key"
}
}
}
}
| SAUCE_USERNAME | Sauce Labs username (required) |
| SAUCE_ACCESS_KEY | Sauce Labs access key (required) |
The data center is set per-session via the region parameter in start_session (defaults to eu-central-1).
export TESTMU_USERNAME=your_username
export TESTMU_ACCESS_KEY=your_access_key
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": ["-y", "@wdio/mcp@latest"],
"env": {
"TESTMU_USERNAME": "your_username",
"TESTMU_ACCESS_KEY": "your_access_key"
}
}
}
}
| TESTMU_USERNAME | LambdaTest username (required) |
| TESTMU_ACCESS_KEY | LambdaTest access key (required) |
export TESTINGBOT_KEY=your_key
export TESTINGBOT_SECRET=your_secret
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": ["-y", "@wdio/mcp@latest"],
"env": {
"TESTINGBOT_KEY": "your_key",
"TESTINGBOT_SECRET": "your_secret"
}
}
}
}
| TESTINGBOT_KEY | TestingBot key (required) |
| TESTINGBOT_SECRET | TestingBot secret (required) |
export DIGITALAI_CLOUD_URL=https://your-cloud.example.com
export DIGITALAI_ACCESS_KEY=your_access_key
{
"mcpServers": {
"wdio-mcp": {
"command": "npx",
"args": ["-y", "@wdio/mcp@latest"],
"env": {
"DIGITALAI_CLOUD_URL": "https://your-cloud.example.com",
"DIGITALAI_ACCESS_KEY": "your_access_key"
}
}
}
}
| DIGITALAI_CLOUD_URL | Digital.ai cloud host, e.g. https://your-cloud.example.com (required) |
| DIGITALAI_ACCESS_KEY | Digital.ai access key (required) |
The access key is sent via the digitalai:options capability (mobile) or the flat digitalai:accessKey capability (web).
Report pass/fail status: WebdriverIO defaults to the BiDi protocol, over which Digital.ai's cloud cannot observe command failures — so reports default to "Passed". To make the cloud reflect actual pass/fail, opt in to classic WebDriver per session:
start_session({
provider: 'digitalai', platform: 'browser', browser: 'chrome', os: 'Windows 10',
capabilities: { 'wdio:enforceWebDriverClassic': true }
})
(Pure client-side assertion failures still report as "Passed" — only failures that reach the cloud as WebDriver command errors are detected.)
Mobile (Appium): configure your Digital.ai project for Appium-server execution and pick its default Appium version via the project's "Manage default Appium server version" setting — the version is chosen at the project level (and tracks the versions your cloud supports), so this MCP does not pin one. See Appium Server Test Execution.
Browser Sessions
Run a browser on a specific OS/version combination:
// BrowserStack
start_session({
provider: 'browserstack',
platform: 'browser',
browser: 'chrome', // chrome | firefox | edge | safari
browserVersion: 'latest', // default: latest
os: 'Windows', // e.g. "Windows", "OS X"
osVersion: '11', // e.g. "11", "Sequoia"
reporting: {
project: 'My Project',
build: 'v1.2.0',
session: 'Login flow'
}
})
// Sauce Labs
start_session({
provider: 'saucelabs',
platform: 'browser',
browser: 'chrome',
os: 'Windows', // combined with osVersion → platformName
osVersion: '11', // e.g. "11", "15" (numbered Mac naming)
region: 'eu-central-1', // default: eu-central-1
reporting: {
build: 'v1.2.0',
session: 'Login flow'
}
})
// LambdaTest
start_session({
provider: 'testmu',
platform: 'browser',
browser: 'chrome',
os: 'Windows', // combined with osVersion → platformName
osVersion: '11', // e.g. "11", "Sequoia" (optional)
reporting: {
project: 'My Project',
build: 'v1.2.0',
session: 'Login flow'
}
})
// TestingBot
start_session({
provider: 'testingbot',
platform: 'browser',
browser: 'chrome',
os: 'Windows', // combined with osVersion → platformName (default: Windows 11)
osVersion: '11',
reporting: {
build: 'v1.2.0',
session: 'Login flow'
}
})
// Digital.ai
start_session({
provider: 'digitalai',
platform: 'browser',
browser: 'chrome',
os: 'Windows', // combined with osVersion → digitalai:osName (optional)
osVersion: '11',
reporting: {
session: 'Login flow' // → digitalai:testName (flat capability, not nested)
}
})
Provider-specific
os/osVersionbehavior:
- BrowserStack —
osandosVersionmap to separatebstack:options.os/bstack:options.osVersionfields.- Sauce Labs / LambdaTest / TestingBot —
osandosVersionare combined into the W3CplatformNamecapability (e.g.,os: 'Windows'+osVersion: '11'→platformName: 'Windows 11'). These providers useplatformNamevalues like"Windows 11","MacOS Sequoia", or"Linux". TestingBot defaults toWindows 11whenosis omitted.- Digital.ai —
osandosVersionare combined into the flatdigitalai:osNamecapability (NOTplatformName), e.g.os: 'Windows'+osVersion: '11'→digitalai:osName: 'Windows 11'.
Mobile App Sessions
Test on cloud real devices. First upload your app (or use an existing app URL):
// BrowserStack: returns bs:// URL
upload_app({ provider: 'browserstack', path: '/path/to/app.apk' })
// Sauce Labs: returns storage:filename= reference
upload_app({ provider: 'saucelabs', path: '/path/to/app.apk' })
// LambdaTest: returns lt:// URL
upload_app({ provider: 'testmu', path: '/path/to/app.apk' })
// TestingBot: returns tb:// URL
upload_app({ provider: 'testingbot', path: '/path/to/app.apk' })
// Digital.ai: returns cloud:<package-or-bundle> reference
upload_app({ provider: 'digitalai', path: '/path/to/app.apk' })
// Start a session
start_session({
provider: 'browserstack',
platform: 'android',
app: 'bs://abc123...',
deviceName: 'Samsung Galaxy S23',
platformVersion: '13.0'
})
// Sauce Labs native app
start_session({
provider: 'saucelabs',
platform: 'android',
app: 'storage:filename=myapp.apk',
deviceName: 'Samsung.*',
platformVersion: '16'
})
// LambdaTest native app
start_session({
provider: 'testmu',
platform: 'android',
app: 'lt://abc123...',
deviceName: 'Pixel 7',
platformVersion: '13'
})
// TestingBot native app
start_session({
provider: 'testingbot',
platform: 'android',
app: 'tb://abc123...',
deviceName: 'Pixel 7',
platformVersion: '13'
})
// Digital.ai native app — devices are selected via a deviceQuery
start_session({
provider: 'digitalai',
platform: 'android',
app: 'cloud:com.example.app',
deviceQuery: "@os='android' and @version='14' and @name='.*Pixel.*'"
// or omit deviceQuery and pass deviceName / platformVersion to build one
})
Mobile Browser Sessions
Run a browser on a cloud mobile device — real device or emulator/simulator — without uploading an app:
// BrowserStack — Chrome on Android emulator
start_session({
provider: 'browserstack',
platform: 'android',
browser: 'chrome',
deviceName: 'Google Pixel 7',
platformVersion: '13'
})
// Sauce Labs — Safari on iOS simulator
start_session({
provider: 'saucelabs',
platform: 'ios',
browser: 'safari',
deviceName: 'iPhone 15',
platformVersion: '18',
region: 'eu-central-1'
})
// LambdaTest — Chrome on Android emulator
start_session({
provider: 'testmu',
platform: 'android',
browser: 'chrome',
deviceName: 'Pixel 7',
platformVersion: '13'
})
// TestingBot — Chrome on Android emulator
start_session({
provider: 'testingbot',
platform: 'android',
browser: 'chrome',
deviceName: 'Pixel 7',
platformVersion: '13'
})
// Digital.ai — Chrome on an Android device (real or emulator; selected via a deviceQuery)
start_session({
provider: 'digitalai',
platform: 'android',
browser: 'chrome',
deviceName: 'Pixel 7',
platformVersion: '13'
// or omit deviceName / platformVersion and pass deviceQuery directly, e.g.
// deviceQuery: "@os='android' and @emulator='true'" to force an emulator
})
Note: Mobile browser sessions do not require
app,appPath, ornoReset. The provider launches a browser directly on the selected device — real or emulator/simulator.
Use list_apps to see previously uploaded apps:
list_apps({ provider: 'browserstack' })
list_apps({ provider: 'saucelabs', sortBy: 'app_name' })
list_apps({ provider: 'testmu' })
list_apps({ provider: 'testingbot' })
list_apps({ provider: 'digitalai' })
list_apps({ provider: 'browserstack', organizationWide: true })
Local Tunnel
To test against URLs that are only accessible on your local machine or internal network, enable a local tunnel:
// Auto-start tunnel (provider manages lifecycle)
start_session({
provider: 'saucelabs',
platform: 'browser',
tunnel: true // auto-starts tunnel before session
})
// Use an already-running tunnel
start_session({
provider: 'saucelabs',
platform: 'browser',
tunnel: 'external' // uses existing tunnel
})
The tunnel parameter replaces the deprecated browserstackLocal, saucelabsLocal, and testmuLocal params. Set it to true to auto-start the tunnel (stopped automatically after the session), or 'external' to use a tunnel already running on your machine.
Note: With
tunnel: truethe provider downloads and manages the tunnel binary for you. Fortunnel: 'external'you run it yourself — thewdio://saucelabs/local-binary,wdio://testmu/local-binary, andwdio://testingbot/local-binaryresources provide download URLs and setup instructions. The TestingBot Tunnel is a single cross-platform Java JAR (requires Java 11+) rather than a per-platform binary.
Reporting Labels
All session types support reporting labels that appear in the provider dashboard:
| Field | Description |
|---|---|
reporting.project |
Group sessions under a project name |
reporting.build |
Tag sessions with a build/version label |
reporting.session |
Name for the individual test session |
Cloud Provider Tools
| Tool | Description |
|---|---|
upload_app |
Upload a local .apk or .ipa to the provider; returns an app URL/reference |
list_apps |
List apps previously uploaded to the provider's app storage |
Both tools require a provider parameter ('browserstack', 'saucelabs', 'testmu', 'testingbot', or 'digitalai').
Features
Browser Automation
- Session Management: Start and close browser sessions (Chrome, Firefox, Edge, Safari) with headless/headed modes
- Navigation & Interaction: Navigate URLs, click elements, fill forms, and retrieve content
- Page Analysis: Get visible elements, accessibility trees, take screenshots
- Cookie Management: Get, set, and delete cookies
- Scrolling: Smooth scrolling with configurable distances
- Attach to running Chrome: Connect to an existing Chrome window via
--remote-debugging-port— ideal for testing authenticated or pre-configured sessions - Connect to existing WebDriver endpoints: Reuse an already-running Selenium-compatible WebDriver endpoint, such as a framework-managed browser or a desktop webview automation bridge (like Tauri)
- Device emulation: Apply mobile/tablet presets (iPhone 15, Pixel 7, etc.) to simulate responsive layouts without a physical device
- Session Recording: All tool calls are automatically recorded and exportable as runnable WebdriverIO JS
Mobile App Automation (iOS/Android)
- Native App Testing: Test iOS (.app/.ipa) and Android (.apk) apps via Appium
- Touch Gestures: Tap, swipe, long-press, drag-and-drop
- App Lifecycle: Launch, background, terminate, check app state
- Context Switching: Seamlessly switch between native and webview contexts for hybrid apps
- Device Control: Rotate, lock/unlock, geolocation, keyboard control, notifications
- Cross-Platform Selectors: Accessibility IDs, XPath, UiAutomator (Android), Predicates (iOS)
Available Tools
The server lists only the tools that fit the current session: browser sessions get the page tools below, mobile sessions the gestures and device tools, Electron sessions the Electron tools. Rarely used groups (mocks, cookies, device emulation, extensions, attaching, the raw element list, cloud app uploads) are listed after the agent calls enable_tools, so their definitions aren't sent with every request. With several live sessions, tools are listed for the union of their platforms. Set WDIO_MCP_TOOLS=all to list everything up front.
Set WDIO_MCP_NETWORK_LOGS to configure the default Chromium network/performance log capture mode for start_session: none (default, off), failures (Network.loadingFailed and Network.responseReceived entries with HTTP status >= 400), or all (every Chromium performance log entry). Individual sessions can override this default via start_session({ networkLogs: 'none' | 'failures' | 'all' }).
| Tool | Description |
|---|---|
enable_tools |
Add a group of tools: mocks, cookies, device, extensions, attach, elements, cloud-apps |
Session Management
| Tool | Description |
|---|---|
start_session |
Start a browser, local Electron application, or mobile app session; attach: true retains the existing Chrome CDP connection mode. Optional name and onExisting: "close" | "keep" (keep runs it alongside existing sessions; the new session is not made the default) |
attach_session |
Attach to an existing remote WebDriver/Appium session by sessionId without creating a new session; optional name and onExisting. With only a name, looks up a live session |
launch_chrome |
Launch a new Chrome instance with remote debugging enabled (for use with start_session({ attach: true })) |
close_session |
Close or detach from the default session, or the one named by the optional session target (supports detach: true to disconnect without terminating) |
emulate_device |
Emulate a mobile/tablet device preset (viewport, DPR, UA, touch); requires BiDi session |
open_web_extension |
Install a web extension through WebDriver BiDi and open one of its extension pages so normal page tools can drive its UI |
WebDriverIO MCP Fragen
Wie füge ich WebDriverIO MCP zu Claude Code hinzu?
Führe claude mcp add mcp -- npx -y @wdio/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich WebDriverIO MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet WebDriverIO MCP?
Er stellt 42 Tools bereit, darunter upload_app, list_apps, enable_tools, start_session, attach_session.
Welche Plattformen kann ich automatisieren?
Du kannst Chrome, Firefox, Edge, Safari, Electron, iOS und Android automatisieren.
Wie aktiviere ich HTTP transport für Clients, die keine Subprozesse starten können?
Du kannst HTTP transport aktivieren, indem du den Befehl mit dem --http flag ausführst und einen Port angibst.
Kann ich Tests auf Cloud-Providern ausführen?
Ja, der Server unterstützt BrowserStack, Sauce Labs, LambdaTest, TestingBot und Digital.ai Testing.