Antidetect browser MCP: Claude, Codex & Cursor

IFox9’s MCP server gives a connected AI assistant tools to select a browser profile, read pages, interact with forms, take screenshots and download files. Claude, Codex and Cursor can use these tools in the selected profile. IFox9 supplies the browser connection; you supply the AI client and model access. See the client compatibility guide for each setup path.

1. Install IFox9 for Windows or macOS, keep it running and create a test profile that opens a public webpage.
2. Open AI Assistant in IFox9, choose the detected client and use its configuration action. Claude Desktop and Claude Code are separate clients; select the one you use.
3. Fully restart that client and approve its MCP server connection if prompted.
4. Ask the assistant to call check_connection, then list_profiles. Confirm the intended profile before opening it.

MCP works with the optional Local API switch turned off. For missing tools or connection errors, follow the troubleshooting guide.

Use this read-only prompt after setup:

Use IFox9. List my profiles and ask which test profile to use.
Open that profile in visible mode and create a new tab.
Visit https://example.com/ and read the page title.
Report the selected profile, page URL and observed title.
Do not submit forms or change account settings.
Release browser control when finished; leave the profile open.

Check that the visible window matches the selected profile and the reported URL and title match the page. This is a sample acceptance check, not a recorded test result. Record your IFox9 version, AI client version, operating system and result when diagnosing a failure. Continue with the CSV download tutorial once page reading works.

1. Call check_connection → list_profiles
2. Call open_profile with the exact profile_id; retain the returned browser_session_id.
3. Call browser_pages to select the exact page_id.
4. Call browser_snapshot to get fresh element references and a snapshot_id.
5. Use matching session, page, snapshot, and element references for actions. Take a new snapshot after page changes.
6. Call release_browser when finished. Use close_profile only when asked to close the profile.

A profile has one exclusive controlling client at a time. IDs are opaque and cannot be reused after a browser restart. Choose visible mode when a person needs to sign in or inspect the work; headless is for compatible background tasks.

Profiles & pages

• check_connection
• list_profiles
• open_profile
• close_profile
• release_browser
• browser_pages
• browser_new_page
• browser_close_page
• browser_activate_page

Navigation & interaction

• browser_navigate
• browser_back
• browser_forward
• browser_reload
• browser_snapshot
• browser_click
• browser_click_coordinates
• browser_type
• browser_press
• browser_hover
• browser_select
• browser_scroll
• browser_drag
• browser_wait
• browser_handle_next_dialog

Data & files

• browser_screenshot
• browser_upload_files
• browser_get_cookies
• browser_set_cookies
• browser_clear_cookies
• browser_storage_get
• browser_storage_set
• browser_storage_clear
• browser_grant_permissions
• browser_prepare_download
• browser_wait_download
• browser_evaluate

These are tool names, not complete request schemas. The connected MCP server advertises current parameter names and required fields to the AI client; use that schema instead of guessing arguments. Cookie, storage, upload, and JavaScript tools can access sensitive data.

Enable Local API only if a local integration needs HTTP. Copy the current loopback endpoint and access token from AI Assistant (API & MCP in earlier builds); the port is assigned dynamically. MCP remains available with HTTP disabled.

GET http://127.0.0.1:<port>/v1/status
Authorization: Bearer <access-token>
X-IFox9-Client-ID: my-integration

The token is required. The optional client ID is recommended and must be 1–64 ASCII letters, digits, underscores, or hyphens. Examples use placeholders only. Never publish your real token.

GET /v1/profiles lists profiles; POST /v1/profiles/open opens one. Successful responses use {"ok":true,"data":…}; failures use {"ok":false,"error":{"code":…,"message":…}}. See common error codes.

The HTTP listener binds to 127.0.0.1, validates Host headers, and does not enable browser CORS. Do not expose it through a public reverse proxy or publish its discovery files. Token rotation invalidates old credentials; update your local integration afterwards.