Antidetect browser MCP FAQ: Claude, Cursor, Codex, and isolated profiles

IFox9, also called IFox9Browser, is a desktop antidetect browser with a local MCP server. It creates separate Chromium profiles with their own cookies, storage, and browser settings. You can configure a proxy for each profile.

Supported clients such as Claude, Cursor, and Codex can use MCP tools to read pages, fill forms, take screenshots, and download files in a profile you select. Review important changes before submission. AI access and proxy services are not included.

1. Install IFox9 and create a clearly named test profile.
2. In the app’s AI Assistant settings, configure the detected client (e.g. Claude).
3. Restart/reconnect the client and call a connection check.
4. Ask the assistant to list profiles and open the exact test profile—not a generic browser.
5. Start with a public page or practice report; verify identity before any write.

For the full step-by-step guide, see Connect Claude, Cursor, or Codex via MCP. Also follow the live Claude / Codex MCP quickstart — UI labels can change by version. Tool reference: MCP docs.

Yes, when Cursor is configured as a supported MCP client against IFox9: select the store’s profile, confirm the page/filters, export once, then open the file yourself. A successful tool connection does not prove the correct store was chosen—always have the assistant read back store name and date range.

RPA automates predefined steps, while window synchronization repeats interactions across windows. MCP is a protocol that lets a client call exposed tools; an AI assistant can use those tools to carry out instructions.

These approaches can coexist. Compare how each one selects the correct profile, handles a page change, asks for any needed review, and recovers from an error. See the AdsPower evaluation guide for a practical checklist.

1. Name profiles after the accounts or stores they contain.
2. Ask the assistant to list profiles and explicitly open the required one.
3. Have it read the account name and filters from the page before continuing.
4. Start with read-only tasks and review important changes before submission.
5. Use one controlling client per browser session and release control when finished.

If the account or page differs from the task, stop and check the selected profile.

No. MCP support tells you that a client can call a set of tools. You still need to check which tools are available, how profiles are selected, what data reaches the AI provider, and how errors are handled. Run your intended task before relying on the integration.

Check support for your client, profile selection, page-reading and download tools, and the steps for reviewing changes. Test the same task in each candidate product and compare the result and recovery process. IFox9 Free includes 20 profiles and 2 team members; see the free-plan details before starting.

No. Profile isolation separates browser state (e.g. cookies, local storage). Platforms also weigh behavior, payments, content, device/network signals, and policy. Refuse any “undetectable / guaranteed no association” pitch.

Typically: cookies, local storage, cache, and profile-level browser settings. A proxy changes network egress when configured. Fingerprint settings adjust browser-exposed characteristics. None of these alone authorize accounts or guarantee platform results. See profile isolation guide.

No. Bring your own AI client subscription and proxy provider. IFox9 supplies isolated browsers and MCP tools.

20 profiles and 2 seats on Free ($0). Confirm current limits in the app / pricing page before purchasing upgrades.

No. IFox9 runs Chromium browser profiles on a desktop computer. Tasks that require a mobile operating system or a phone-only app need a separate solution.

Yes. Sign in and complete verification yourself in the selected profile, then give the assistant a specific task in that session. Keep passwords out of prompts, limit tool permissions, and review downloads and form submissions. Check your team’s policy and the AI permissions and data access guide.

Specify the store, browser profile, report, date range, filters, and expected output. After opening the profile, ask the assistant to read back these details. Export the report once, open the actual file, and check its contents and totals before releasing control.

Start with fictional data in the practice report tutorial before using an authorized store account. See also the store operations guide.