Connect Claude, Cursor, or Codex to IFox9 via MCP

Answer first: Install IFox9, create a clearly named test profile, configure your AI client in AI Assistant (API & MCP in earlier builds), restart the client, then run one shared sequence: list profiles → open the exact named profile → read-only first → human review before writes.

IFox9 is a desktop antidetect browser with a local MCP server. Claude, Cursor, Codex, and other supported clients can read pages, fill forms, screenshot, and download files inside a profile you select. AI model access and proxies are not included.

MCP is not exclusive to IFox9. AdsPower, BitBrowser, and others also publish MCP or API paths. Compare whether the assistant can target one named profile, keep page work inside that profile, and leave consequential submits for human review—not marketing slogans.

• IFox9 installed and running on Windows or macOS.
• A supported AI client with its own subscription (Claude Desktop / Claude Code, Cursor, Codex, or another client listed in client compatibility).
• A test profile with no sensitive sessions for the first run.
• Optional proxy only if your network setup requires it—IFox9 does not sell proxies.

UI labels can change by version. Prefer the live Claude / Codex MCP quickstart and MCP reference when wording differs.

1. Open IFox9 and create a profile named after the store or task (avoid vague names like test2).
2. Confirm it can open a public page such as https://example.com/.
3. Keep this first profile free of production store logins until the acceptance task passes.

Profile isolation separates cookies, local storage, cache, and profile-level settings. It does not guarantee platform account outcomes. See what profile isolation separates.

1. Open AI Assistant in the IFox9 sidebar (labeled API & MCP in earlier builds).
2. Configure the detected client that matches the app you actually use (Claude Desktop and Claude Code are different clients).
3. Fully restart that AI client and approve the MCP server if prompted.
4. Run the connection test in IFox9, then confirm the client exposes the ifox9 tools.
5. Ask the client to run check_connection when available.

MCP works without enabling the optional Local API switch. WorkBuddy can auto-configure MCP; other clients follow their own connector flow—see clients.

Use the same sequence for Claude, Cursor, and Codex. Do not skip the list/open step.

Use IFox9. List my profiles and ask me which one to use.
Open the selected profile in visible mode, create a new tab,
and visit https://example.com/. Read its title and summarize
the page. Do not submit forms or change account settings.
Release browser control when finished; leave the profile open.

Pass criteria:

1. The assistant listed profiles and opened the exact named profile you chose.
2. It reported the real page title/content from a fresh snapshot.
3. No other profile was used and no form was submitted.
4. Browser control was released so another client can take over.

A successful tool connection does not prove the correct profile was chosen—always have the assistant read back profile and page identity.

After the public-page check passes, rehearse a download on the fictional practice report (no store login, no real customer data). Ask the assistant to identify reporting dates, time zone, and currency, then download the CSV from the page control.

Expected fixture contents (practice only): three daily rows for September 1–3, 2026, UTC, USD; 12 orders and $360 gross sales in total. Open the downloaded file yourself and check those values. This is a practice fixture, not a recorded marketplace test. Walkthrough: AI task tutorial and quickstart.

• Sign in and complete verification yourself in the selected profile; do not paste passwords into prompts.
• Allow writes (listing edits, messages, payments) only after you confirm store identity, filters, and intended action.
• Use one controlling client per browser session; release control when finished.
• If the account or page differs from the task, stop and re-check the selected profile.

More on wrong-store prevention and permissions: MCP FAQ · security and data access.

1. Confirm which client is configured in AI Assistant—the adapter must match the app you open.
2. Keep IFox9 running; fully restart the AI client after configuration changes.
3. If check_connection is missing, revisit client detection; Local API is not a substitute for MCP setup.
4. If connection works but browser control fails, confirm the selected profile and read the returned error; follow troubleshooting.

Download IFox9 (Free: 20 profiles / 2 seats), complete the acceptance task above, then adapt one authorized store report using the quickstart sample—verify the file, not only the assistant’s reply.

Related: MCP quickstart · MCP reference · clients · FAQ · free plan facts.

For legitimate multi-account and multi-store operations only. Isolation does not guarantee platform results.