Resources
MCP resources provide read-only access to live session state. Unlike tools, resources are pulled by the AI model at will; they don't execute actions. All resources use the wdio:// URI scheme.
When to use resources vs tools
- Resources — ambient state that changes as you interact: current elements, screenshot, cookies, accessibility tree. Read them before acting to understand what's on screen.
- Tools — actions that change state: click, navigate, set value.
Prefer wdio://session/current/elements over get_screenshot for element discovery; it returns ready-to-use selectors and costs far fewer tokens.
Session History
wdio://sessions
Index of all browser and app sessions with metadata and step counts.
{
"sessions": [
{
"sessionId": "abc-123",
"type": "browser",
"startedAt": "2024-01-15T10:00:00.000Z",
"endedAt": "2024-01-15T10:05:00.000Z",
"stepCount": 12,
"isCurrent": false
}
]
}
wdio://session/current/steps
JSON step log for the currently active session. Contains all recorded automation steps with tool names, parameters, and timestamps.
wdio://session/current/code
Generated WebdriverIO JavaScript for the currently active session. Auto-generated from recorded steps. Paste into a WebdriverIO test file to replay the session.
wdio://session/{sessionId}/steps
Step log for a specific session by ID. URI template — replace {sessionId} with the ID from wdio://sessions.
wdio://session/{sessionId}/code
Generated WebdriverIO JavaScript for a specific session by ID. URI template — replace {sessionId} with the ID from wdio://sessions.