Claude / Codex MCP browser tutorial

Install and keep IFox9 running. Sign in as needed, create a profile, and make sure it can open a public webpage. Use a test profile without sensitive sessions for your first run. The matching browser kernel is managed by IFox9; most users do not need to download a kernel ZIP manually.

Open AI Assistant (API & MCP in earlier builds) in the IFox9 sidebar. Configure a detected client using the available action, then restart that AI client. Existing configuration is backed up and unrelated entries are preserved. WorkBuddy supports automatic MCP configuration; Doubao Work requires confirmation inside its own connector flow. See the compatibility table.

Use the connection test in IFox9, then check that the AI client exposes the ifox9 server tools. MCP works without enabling the optional Local API switch.

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.

This is an example prompt, not a recorded run. The assistant should select the exact profile and page, obtain a fresh snapshot, report the observed result, then release its lease.

• The expected profile and tab are visible.
• The assistant reports the actual page title and content.
• No unrelated profile is used and no form is submitted.
• Control is released so another client can use the profile.

For screenshots, exports, or form filling, specify the page, output, and allowed actions. Review privacy and permissions before using authenticated or sensitive pages.

Use the fictional report practice page to rehearse reading a page, downloading a CSV and checking its contents. It contains no store login or real customer data. Ask your assistant to identify the reporting dates, time zone and currency, then download the CSV using the page control.

Expected fixture contents: three daily rows for September 1–3, 2026, UTC, USD; 12 orders and $360 gross sales in total. Check the downloaded file against those values. This is a practice fixture, not a recorded demonstration or a tested marketplace integration.

After the public-page task succeeds, choose one store profile and open its dashboard in visible mode. Complete sign-in yourself if needed. Identify the store, marketplace, report type, date range and time zone before asking the assistant to download anything.

The following is a sample workflow for the documented IFox9 0.0.3 integration, not a recorded marketplace test. Export controls and supported formats depend on the actual store platform. An AI subscription, store account and any required proxy are separate prerequisites.

Use IFox9 to list my profiles and ask which store profile to use.
Open that profile in visible mode and read the current dashboard.
Report the store name, marketplace, report type, date range and time zone.
If any item is unclear, ask me before continuing.
After I confirm those details, use the page's export control to download
one report. Do not change listings, send messages or edit account settings.
Report the downloaded file's actual location and anything you could not verify.
Release browser control when done and leave the profile window open.

Replace the task details with your own requirements. If the dashboard asks for a login or human verification, complete that step in the visible window, then ask the assistant to read the page again. Do not treat a sample prompt as proof that a marketplace has been tested.

If no file is produced, inspect the actual export state instead of claiming success. Use the troubleshooting guide for connection or session errors. The MCP reference explains the control interface.

1. Check which client you actually use in AI Assistant (AI Assistant (API & MCP in earlier builds) in earlier builds). Claude Desktop and Claude Code are different clients; configure the detected adapter for the intended application.
2. Keep IFox9 running. After configuration, fully restart that AI client and approve the MCP server in the client if prompted.
3. Ask the client to run check_connection. If the tool is missing, revisit client detection and configuration; enabling the optional Local API switch is not a substitute for MCP setup.
4. If the connection succeeds but browser control fails, confirm the selected profile and read the returned error. Follow the matching recovery steps instead of changing unrelated settings.

Consult client-specific integration paths and the Skill installation guide. Skill availability is shown separately from MCP connectivity.

For your own acceptance test, record the IFox9 version, operating system, AI client version, test date, target public URL and observed outcome. Save an actual screenshot or output file and note any failed step. Remove account identifiers before sharing the record.

The prompts on this page are reproducible instructions, not measured success-rate claims. Once the public-page check passes, adapt the report example to one authorized store. Review platforms, plans and prerequisites or return to the desktop downloads.