browser_close_session — WebArm24 MCP Tool
browser_close_session
(browser close session) is one of 91 tools on the
WebArm24
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call browser_close_session from your client
- Claude Code WebArm24 browser_close_session run in your project directory
- Claude Desktop WebArm24 browser_close_session ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WebArm24 browser_close_session ~/.cursor/mcp.json
- VS Code WebArm24 browser_close_session .vscode/mcp.json
- Zed WebArm24 browser_close_session ~/.config/zed/settings.json
- Windsurf WebArm24 browser_close_session ~/.codeium/windsurf/mcp_config.json
- Cline WebArm24 browser_close_session ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WebArm24 browser_close_session ~/.gemini/settings.json
- Grok WebArm24 browser_close_session .mcp.json (in your project root)
- ChatGPT WebArm24 browser_close_session Settings → Connectors → Advanced → Developer mode
- Claude.ai WebArm24 browser_close_session Settings → Connectors → Add custom connector
- LangChain WebArm24 browser_close_session pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http webarm24 https://webarm24.online/mcpOther tools on this server
- browser_navigate
- browser_screenshot
- browser_click
- browser_click_at
- browser_fill
- browser_press_key
- browser_paste_html
- browser_extract_text
- browser_scroll
- browser_get_html
- send_email
- analyze_json
- pipeline_list
- pipeline_get
- pipeline_create
- pipeline_update
- pipeline_delete
- pipeline_history_list
- pipeline_history_get
- pipeline_history_restore
- pipeline_deleted_list
- pipeline_deleted_restore
- pipeline_group_list
- pipeline_group_create
- pipeline_group_update
- pipeline_group_delete
- pipeline_group_assign
- pipeline_test_step
- pipeline_run
- pipeline_run_get
- pipeline_run_wait
- pipeline_runs_list
- pipeline_run_cancel
- pipeline_builder_chat
- pipeline_debug_chat
- workflow_list
- workflow_get
- workflow_validate
- workflow_create
- workflow_update
- workflow_delete
- workflow_export
- workflow_import
- workflow_run
- workflow_run_get
- workflow_run_wait
- workflow_runs_list
- workflow_run_cancel
- workflow_approve
- workflow_history_list
- workflow_history_get
- workflow_history_restore
- workflow_deleted_list
- workflow_deleted_restore
- workflow_builder_chat
- workflow_builder_create_pipeline
- agent_job_submit
- agent_job_get
- agent_job_list
- schedule_list
- schedule_get
- schedule_create
- schedule_update
- schedule_delete
- schedule_run
- schedule_export
- schedule_import
- storage_list
- storage_read
- storage_write
- storage_delete
- ai_models_list
- skill_list
- skill_get
- skill_create
- skill_import
- skill_update
- skill_delete
- storage_files_list
- storage_file_put
- storage_file_get
- storage_file_delete
- browser_session_list
- browser_session_get
- browser_session_put
- browser_session_delete
- account_me
- credits_history
- credit_packs
- credits_checkout_url
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.