AI browser automation with MCP: connect, operate and verify

IFox9 provides isolated browser profiles and executable browser tools. Your AI client supplies the model, interprets your instruction and chooses tool calls. MCP connects that client to IFox9. A compatible Skill adds operating instructions; it does not supply a model or replace the MCP connection.

1. Connect: configure the intended detected client and test the connection.
2. Select: identify the exact profile and page.
3. Observe: obtain fresh page information before interacting.
4. Act: perform the bounded read, form, screenshot or download task.
5. Verify: inspect the actual page or file result and release control.

Begin with the Claude / Codex walkthrough. It starts with a public-page task before introducing report downloads.

• Which client and configuration path should I use?
• Which tools and API operations are available?
• What does the IFox9 Skill install?
• What information can the model receive?
• Why can the client not connect or control the page?

If your concern is separating account state, start with profile isolation. If your concern is correct operational output, use the store reporting workflow. For supported systems and additional costs, review product facts.

These guides describe the documented desktop integration. Actual detected clients and available actions in your installed application are the source of truth. Get the desktop app.