flow_run — Aginx Browser MCP Tool
flow_run
(flow run) is one of 40 tools on the
Aginx Browser
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call flow_run from your client
- Claude Code Aginx Browser flow_run run in your project directory
- Claude Desktop Aginx Browser flow_run ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aginx Browser flow_run ~/.cursor/mcp.json
- VS Code Aginx Browser flow_run .vscode/mcp.json
- Zed Aginx Browser flow_run ~/.config/zed/settings.json
- Windsurf Aginx Browser flow_run ~/.codeium/windsurf/mcp_config.json
- Cline Aginx Browser flow_run ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aginx Browser flow_run ~/.gemini/settings.json
- Grok Aginx Browser flow_run .mcp.json (in your project root)
- ChatGPT Aginx Browser flow_run Settings → Connectors → Advanced → Developer mode
- Claude.ai Aginx Browser flow_run Settings → Connectors → Add custom connector
- LangChain Aginx Browser flow_run pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aginxbrowser https://browser.aginx.net/mcpOther tools on this server
- account_delete
- account_list
- account_login
- account_verify
- cache
- click
- download
- eval
- fetch
- import_curl
- render_markdown
- render_pdf
- render_video
- search
- session_challenges
- session_click
- session_click_xy
- session_clone
- session_close
- session_console
- session_cookies
- session_create
- session_dialog
- session_drag
- session_eval
- session_export
- session_input
- session_list
- session_navigate
- session_network
- session_preload
- session_screenshot
- session_scroll
- session_set_files
- session_state
- session_storage
- session_verdict
- session_viewport
- session_wait
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.