list_sessions — WebRun Browser Automation MCP Tool Read-only
list_sessions
(list sessions) 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 list_sessions from your client
- Claude Code WebRun Browser Automation list_sessions run in your project directory
- Claude Desktop WebRun Browser Automation list_sessions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WebRun Browser Automation list_sessions ~/.cursor/mcp.json
- VS Code WebRun Browser Automation list_sessions .vscode/mcp.json
- Zed WebRun Browser Automation list_sessions ~/.config/zed/settings.json
- Windsurf WebRun Browser Automation list_sessions ~/.codeium/windsurf/mcp_config.json
- Cline WebRun Browser Automation list_sessions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WebRun Browser Automation list_sessions ~/.gemini/settings.json
- Grok WebRun Browser Automation list_sessions .mcp.json (in your project root)
- ChatGPT WebRun Browser Automation list_sessions Settings → Connectors → Advanced → Developer mode
- Claude.ai WebRun Browser Automation list_sessions Settings → Connectors → Add custom connector
- LangChain WebRun Browser Automation list_sessions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http webrun https://api.webrun.ai/mcpOther 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
- screenshot
- 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.