screenshot — WebRun Browser Automation MCP Tool
screenshot
(screenshot) is one of 21 tools on the
WebRun Browser Automation
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screenshot from your client
- Claude Code WebRun Browser Automation screenshot run in your project directory
- Claude Desktop WebRun Browser Automation screenshot ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WebRun Browser Automation screenshot ~/.cursor/mcp.json
- VS Code WebRun Browser Automation screenshot .vscode/mcp.json
- Zed WebRun Browser Automation screenshot ~/.config/zed/settings.json
- Windsurf WebRun Browser Automation screenshot ~/.codeium/windsurf/mcp_config.json
- Cline WebRun Browser Automation screenshot ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WebRun Browser Automation screenshot ~/.gemini/settings.json
- Grok WebRun Browser Automation screenshot .mcp.json (in your project root)
- ChatGPT WebRun Browser Automation screenshot Settings → Connectors → Advanced → Developer mode
- Claude.ai WebRun Browser Automation screenshot Settings → Connectors → Add custom connector
- LangChain WebRun Browser Automation screenshot pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http webrun https://api.webrun.ai/mcp
Other tools on this server
- browser_task
- create_session
- send_task
- pause_session_task
- resume_session_task
- stop_session_task
- terminate_session
- guardrail_response
- get_task_status
- list_sessions
- list_environments
- list_workflows
- get_workflow
- create_workflow
- update_workflow
- trigger_workflow
- create_agent
- list_agents
- pause_agent
- resume_agent
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.