AI asistanlarının web tarayıcılarını, yerel Electron uygulamalarını ve iOS ile Android üzerindeki mobil uygulamaları otomatize etmesini sağlar.
Ayrıca bilinen adı webdriverio/mcp, @wdio/mcp
- Yıldızlar
- 44
- Araçlar
- 17
- İndirmeler, 30 gün
- —
- En son sürüm
- 4.1.0
- Son commit
- 15 Kas 2026
- Lisans
- MIT
WebDriverIO MCP nedir?
AI asistanlarının web tarayıcılarını, yerel Electron uygulamalarını ve iOS ile Android üzerindeki mobil uygulamaları otomatize etmesini sağlar. 17 araç sunar; örneğin start_session, close_session, navigate.
Özet, projenin README dosyasından oluşturuldu
WebDriverIO MCP sunucusu hakkında
Bu MCP server aracılığıyla web tarayıcılarını, mobil uygulamaları ve yerel Electron uygulamalarını otomatize etmek mümkündür. AI asistanlarının Chrome, Firefox, Edge ve Safari'nin yanı sıra iOS ve Android cihazlarıyla etkileşime girmesi için birleşik bir arayüz sunar. Geliştiriciler bunu yerel ortamlarda test çalıştırmak veya BrowserStack, Sauce Labs, LambdaTest, TestingBot ve Digital.ai Testing gibi bulut sağlayıcılarına bağlanmak için kullanabilirler.
Bu sunucuyu kullanmak için npx üzerinden veya global bir npm paketi olarak yükleyebilirsiniz. Temel olarak subprocess istemcileri için stdio transport kullanır, ancak subprocess başlatamayan istemciler için belirli bir port üzerinden HTTP transport'u da destekler. Mobil otomasyon için yerel bir Appium sunucusu ve iOS için xcuitest veya Android için uiautomator2 gibi platforma özel sürücüler gereklidir. Bulut tabanlı testler için kullanıcı adı ve erişim anahtarı gibi kimlik bilgilerini ortam değişkenleri veya istemci yapılandırmanız aracılığıyla sağlamanız gerekir.
Neler yapabilirsiniz
- 1Web tarayıcı testlerini otomatize edinBir AI'yı Chrome veya Safari gibi farklı web tarayıcılarında eylemler gerçekleştirmesi için yönlendirin.
- 2Mobil uygulamaları test edinBir AI'ya iOS simülatörleri veya Android emülatörleri üzerinde otomatize edilmiş iş akışları çalıştırması talimatını verin.
- 3Bulutta testleri yürütünBulut hizmetlerini kullanarak uzak gerçek cihazlar üzerinde otomatize edilmiş tarayıcı ve mobil oturumları çalıştırın.
- 4Yerel masaüstü uygulamalarıyla etkileşime geçinYerel Electron tabanlı yazılım uygulamalarını kontrol etmek için bir AI asistanı kullanın.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
WebDriverIO MCP nasıl yüklenir
Biçimler 10 Kas 2026 tarihinde doğrulandıCursor'a ekleGoose'a ekleWebDriverIO MCP'yi Claude Code içine yükleyin
$ claude mcp add mcp -- npx -y @wdio/mcpWebDriverIO MCP'yi Cursor içine yükleyin
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP'yi VS Code içine yükleyin
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP'yi VS Code CLI içine yükleyin
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@wdio/mcp"]}'WebDriverIO MCP'yi Claude Desktop içine yükleyin
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}WebDriverIO MCP'yi Codex içine yükleyin
$ codex mcp add mcp -- npx -y @wdio/mcpWebDriverIO MCP'yi Codex config.toml içine yükleyin
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@wdio/mcp"]
WebDriverIO MCP'yi Gemini CLI içine yükleyin
$ gemini mcp add -s user mcp npx -- -y @wdio/mcpWebDriverIO MCP'yi Gemini settings.json içine yükleyin
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@wdio/mcp"
]
}
}
}HostedMCP tarafından 16 Kas 2026 tarihinde başlatıldı
Bu komutu @wdio/mcp 4.1.0 için ağsız ve anahtarsız, yalıtılmış bir konteynerde çalıştırdık. Yanıt verdi ve 17 araç listeledi.
WebDriverIO MCP araçları 17
Sunucudan tools/list ile okundustart_sessionStarts a browser, Electron app or mobile app session (closes the active one unless onExisting: "keep"). Browsers run headless at 1280x800 by default; pass navigationUrl to open a page right away. attach: true connects to a running Chrome via CDP.
close_sessionCloses the session, or with detach: true disconnects and leaves it running. Attached sessions and Appium sessions with noReset are detached unless detach: false.
navigateLoads a URL in the current tab and waits for the page load event. Resets page state — DOM, JS runtime, timers, and frame context are destroyed. Use instead of clicking links when the target URL is known.
switch_tabSwitches to a tab by handle or 0-based index (see get_tabs). Later tools act on that tab.
switch_frameSwitches into an iframe (ref or selector), or back to the top page when selector is omitted. Later tools act inside the frame until you switch back. Returns the frame's elements.
scrollScrolls the page vertically by a pixel amount. Browser-only — for mobile scrolling use swipe. Only supports up/down; no horizontal scrolling.
click_elementClicks an element. On web pages the result lists what changed (new elements with refs, or the new page). In apps it does not: take a snapshot to see the new screen. Several steps in a row: perform_actions.
set_valueReplaces the text of an input or textarea. On web pages the result lists what changed (new elements with refs, or the new page). In apps it does not: take a snapshot to see the new screen. To fill several fields or fill and then click, use one perform_actions call.
select_optionSelects an option of a <select> by its text. The result lists what changed on the page. Several steps in a row: perform_actions.
press_keyPresses a key or combination in the focused element, e.g. Enter, Tab, Escape, Control+a. The result lists what changed on the page. Several steps in a row: perform_actions.
perform_actionsRuns several actions in one call, e.g. fill a form and submit it, on the page or app screen, and returns what each one changed on web pages. Steps the current session does not support are rejected before any step runs. Stops at the first failure, when a step loads a new page, or before a key press that follows a click, select, check or uncheck that changed the page (continue with the new refs). value is the text for fill, the option for select and the keys for press.
snapshotSalt okunurThe page or app screen as an accessibility tree with refs, e.g. `button "Save" [ref=e3]`. Pass refs to perform_actions for several steps, or to click_element/set_value/select_option for one. Default: interactive elements only, plain text is dropped; full: true shows it. find returns only the parts of the page that contain the text (with their refs); full: true includes all text; viewport: true limits it to what is on screen (not together with find).
| start_session | Starts a browser, Electron app or mobile app session (closes the active one unless onExisting: "keep"). Browsers run headless at 1280x800 by default; pass navigationUrl to open a page right away. attach: true connects to a running Chrome via CDP. | |
| close_session | Closes the session, or with detach: true disconnects and leaves it running. Attached sessions and Appium sessions with noReset are detached unless detach: false. | |
| navigate | Loads a URL in the current tab and waits for the page load event. Resets page state — DOM, JS runtime, timers, and frame context are destroyed. Use instead of clicking links when the target URL is known. | |
| switch_tab | Switches to a tab by handle or 0-based index (see get_tabs). Later tools act on that tab. | |
| switch_frame | Switches into an iframe (ref or selector), or back to the top page when selector is omitted. Later tools act inside the frame until you switch back. Returns the frame's elements. | |
| scroll | Scrolls the page vertically by a pixel amount. Browser-only — for mobile scrolling use swipe. Only supports up/down; no horizontal scrolling. | |
| click_element | Clicks an element. On web pages the result lists what changed (new elements with refs, or the new page). In apps it does not: take a snapshot to see the new screen. Several steps in a row: perform_actions. | |
| set_value | Replaces the text of an input or textarea. On web pages the result lists what changed (new elements with refs, or the new page). In apps it does not: take a snapshot to see the new screen. To fill several fields or fill and then click, use one perform_actions call. | |
| select_option | Selects an option of a <select> by its text. The result lists what changed on the page. Several steps in a row: perform_actions. | |
| press_key | Presses a key or combination in the focused element, e.g. Enter, Tab, Escape, Control+a. The result lists what changed on the page. Several steps in a row: perform_actions. | |
| perform_actions | Runs several actions in one call, e.g. fill a form and submit it, on the page or app screen, and returns what each one changed on web pages. Steps the current session does not support are rejected before any step runs. Stops at the first failure, when a step loads a new page, or before a key press that follows a click, select, check or uncheck that changed the page (continue with the new refs). value is the text for fill, the option for select and the keys for press. | |
| snapshot | The page or app screen as an accessibility tree with refs, e.g. `button "Save" [ref=e3]`. Pass refs to perform_actions for several steps, or to click_element/set_value/select_option for one. Default: interactive elements only, plain text is dropped; full: true shows it. find returns only the parts of the page that contain the text (with their refs); full: true includes all text; viewport: true limits it to what is on screen (not together with find). | Salt okunur |
17 aracın tümünü gösterDaha az araç göster
execute_scriptRuns JavaScript in the page (`return` a value; string args that match a selector are passed as elements) or, on Appium, a "mobile: <command>" with args. Prefer the dedicated tools for clicks and typing.
query_docsSalt okunurSearch the official WebdriverIO documentation and return the most relevant excerpts with page, section and source URL. Use before answering any question about WebdriverIO APIs, configuration, services, reporters, selectors, or debugging. Query with 2-3 distinctive keywords, never a sentence: "appium setup", "devtools trace.zip" and "allure reporter" each return the right page first, while "how do I wire up appium in my config file" does not. A word can also collide with an unrelated page — `wire` matches Wire Protocol — so if a query misses, retry with the exact page title, which beats any paraphrase. Set fullPage for the whole page. To browse instead, read wdio://docs/index for every page title and its slug, then wdio://docs/page/{slug} for one page in full. Cite the `path` of any page you rely on.
get_screenshotSalt okunurTakes a screenshot of the current page or screen and returns a base64-encoded image, resized and compressed for model context limits.
get_tabsSalt okunurLists all browser tabs with handle, title, URL, and which is active. Use before switch_tab to find the target handle or index. Browser-only.
enable_toolsSalt okunurAdds more tools: mocks (mock network requests or Electron APIs); cookies (read, set and delete cookies); device (emulate a phone or tablet, fake the location); extensions (install and open a browser extension); attach (launch Chrome with remote debugging, attach to a running WebDriver or Appium session); elements (raw element list with bounds); cloud-apps (upload and list mobile apps on BrowserStack, Sauce Labs, TestMu, TestingBot, Digital.ai).
| execute_script | Runs JavaScript in the page (`return` a value; string args that match a selector are passed as elements) or, on Appium, a "mobile: <command>" with args. Prefer the dedicated tools for clicks and typing. | |
| query_docs | Search the official WebdriverIO documentation and return the most relevant excerpts with page, section and source URL. Use before answering any question about WebdriverIO APIs, configuration, services, reporters, selectors, or debugging. Query with 2-3 distinctive keywords, never a sentence: "appium setup", "devtools trace.zip" and "allure reporter" each return the right page first, while "how do I wire up appium in my config file" does not. A word can also collide with an unrelated page — `wire` matches Wire Protocol — so if a query misses, retry with the exact page title, which beats any paraphrase. Set fullPage for the whole page. To browse instead, read wdio://docs/index for every page title and its slug, then wdio://docs/page/{slug} for one page in full. Cite the `path` of any page you rely on. | Salt okunur |
| get_screenshot | Takes a screenshot of the current page or screen and returns a base64-encoded image, resized and compressed for model context limits. | Salt okunur |
| get_tabs | Lists all browser tabs with handle, title, URL, and which is active. Use before switch_tab to find the target handle or index. Browser-only. | Salt okunur |
| enable_tools | Adds more tools: mocks (mock network requests or Electron APIs); cookies (read, set and delete cookies); device (emulate a phone or tablet, fake the location); extensions (install and open a browser extension); attach (launch Chrome with remote debugging, attach to a running WebDriver or Appium session); elements (raw element list with bounds); cloud-apps (upload and list mobile apps on BrowserStack, Sauce Labs, TestMu, TestingBot, Digital.ai). | Salt okunur |
Yapılandırma
BROWSERSTACK_ACCESS_KEYBROWSERSTACK_USERNAMEDIGITALAI_ACCESS_KEYDIGITALAI_CLOUD_URLSAUCE_ACCESS_KEYSAUCE_USERNAMETESTINGBOT_KEYTESTINGBOT_SECRETTESTMU_ACCESS_KEYTESTMU_USERNAME
| Ad | Açıklama | Sunucu |
|---|---|---|
| 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 | — |
Otomatik kontroller
Çalıştırıldı 16 Kas 2026Tam rapor →Otomatik kontrollerimizden geçti. Bu bir güvenlik denetimi değildir: kodu okuyun ve sunucuya ihtiyaç duyduğu en dar erişimi verin. Kontroller nasıl çalışır · Daha fazla puan için nelerin düzeltileceği
- Kaynak deposu bağlantılı ve erişilebilirwebdriverio/mcp is public and reachablegithub.com/webdriverio/mcp ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyor@wdio/mcp names webdriverio/mcp as sourcenpmjs.com/package/@wdio/mcp ↗Geçti
- Derleme kökeni (Sigstore onayı)Sigstore attestation for @wdio/mcpnpmjs.com/package/@wdio/mcp/v/4.1.0#provenance ↗Geçti
- Açık kaynak lisansı (OSI)MITspdx.org/licenses/MIT.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-15github.com/webdriverio/mcp ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilNo popular package one edit away from @wdio/mcpGeçti
- Pakette veya bağımlılıklarında kritik uyarı yok400 resolved dependencies checked; no critical advisoryosv.dev ↗Geçti
- Modele yönelik gizli talimat yok17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersGeçti
- Yıkıcı araçlar etiketlenmişexecute_script has no destructiveHintBulgu
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorKontrol edilmedi
WebDriverIO 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 soruları
WebDriverIO MCP'yi Claude Code'a nasıl eklerim?
Terminalinizde claude mcp add mcp -- npx -y @wdio/mcp komutunu çalıştırın. Her projede kullanılabilir olması için --scope user ekleyin.
WebDriverIO MCP'yi Cursor'a nasıl eklerim?
~/.cursor/mcp.json dosyasını açın ve yukarıdaki yükleme bölümünde gösterilen Cursor yapılandırmasını kullanarak sunucuyu mcpServers altına ekleyin.
WebDriverIO MCP hangi araçları sunar?
17 araç sunar; bunlar arasında start_session, close_session, navigate, switch_tab, switch_frame yer alır.
Hangi platformları otomatize edebilirim?
Chrome, Firefox, Edge, Safari, Electron, iOS ve Android'i otomatize edebilirsiniz.
Subprocess başlatamayan istemciler için HTTP transport nasıl etkinleştirilir?
Komutu --http bayrağı ile çalıştırıp bir port belirleyerek HTTP transport'u etkinleştirebilirsiniz.
Bulut sağlayıcıları üzerinde test çalıştırabilir miyim?
Evet, sunucu BrowserStack, Sauce Labs, LambdaTest, TestingBot ve Digital.ai Testing platformlarını destekler.