run_playbook — Oya Browser MCP Tool Mutating
run_playbook
(run playbook) is one of 32 tools on the
Oya Browser
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_playbook from your client
- Claude Code Oya Browser run_playbook run in your project directory
- Claude Desktop Oya Browser run_playbook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Oya Browser run_playbook ~/.cursor/mcp.json
- VS Code Oya Browser run_playbook .vscode/mcp.json
- Zed Oya Browser run_playbook ~/.config/zed/settings.json
- Windsurf Oya Browser run_playbook ~/.codeium/windsurf/mcp_config.json
- Cline Oya Browser run_playbook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Oya Browser run_playbook ~/.gemini/settings.json
- Grok Oya Browser run_playbook .mcp.json (in your project root)
- ChatGPT Oya Browser run_playbook Settings → Connectors → Advanced → Developer mode
- Claude.ai Oya Browser run_playbook Settings → Connectors → Add custom connector
- LangChain Oya Browser run_playbook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/poolOther tools on this server
- select_option
- run_script
- wait_for
- find
- hover
- go_back
- go_forward
- reload
- solve_captcha
- sign_in
- complete_mfa
- list_saved_logins
- list_playbooks
- run_task
- analyze_page
- navigate
- click
- type
- screenshot
- press_key
- handle_dialog
- scroll
- wait
- click_coordinates
- mouse_move
- double_click
- keyboard_type
- drag
- start_browser
- stop_browser
- pool_status
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.