Webdriverio MCP

Name: Webdriverio MCP
Author: webdriverio

by webdriverioversion 4.1.0i★ –iRuns on your computer

Registry nameio.github.webdriverio/mcp

Install

Overview

Description from the maker (original English)

MCP server with WebdriverIO for browser and mobile app automation (iOS/Android via Appium)

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "webdriverio": {
      "command": "npx",
      "args": [
        "-y",
        "@wdio/mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add webdriverio -- npx -y @wdio/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "webdriverio": {
      "command": "npx",
      "args": [
        "-y",
        "@wdio/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "webdriverio": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@wdio/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account webdriverio, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 875 servers in this category
Published to the registry more recently than 83% of the other 875 servers in this category
Basic checks equal to or better than 100% of the other 875 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Webdriverio MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (4.1.0) reached the registry 7 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 16 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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" ] } } }

Claude Desktop

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 Code

claude mcp add wdio-mcp -- npx -y @wdio/mcp@latest

Cline

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" ] } } }

Cursor

Go to Cursor Settings → MCP → Add new MCP Server, or create .cursor/mcp.json:

"mcpServers": { "wdio-mcp": { "command": "npx", "args": [ "-y", "@wdio/mcp@latest" ] } } }

Codex

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"]

Goose

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

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

"mcpServers": { "wdio-mcp": { "command": "npx", "args": [ "-y", "@wdio/mcp@latest" ] } } }

Zed

Edit Zed settings (~/.config/zed/settings.json):

"context_servers": { "wdio-mcp": { "source": "custom", "command": "npx", "args": [ "-y", "@wdio/mcp@latest" ] } } }

VS Code (Copilot)

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)
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:

BrowserStack

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" } } } }

Sauce Labs

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" } } } }

The data center is set per-session via the region parameter in start_session (defaults to eu-central-1).

LambdaTest (TestMu)

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" } } } }

TestingBot

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" } } } }

Digital.ai Testing

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" } } } }

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 flo

Only the beginning is shown; read the rest in the repo

Webdriverio MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

WebDriverIO MCP Server

Installation

Option 2: Global Installation

HTTP Transport (for non-subprocess clients)

Prerequisites For Mobile App Automation

Server runs at http://127.0.0.1:4723 by default

Cloud Providers

Prerequisites

Browser Sessions