Hey @calvinrose18938, thanks for the concrete example. Details like that really help.
With QuickBooks, it’s most likely that the site is flagging the bot’s cloud browser as automated traffic. We saw something similar with Shopify: Shopify store connector. There is a separate feature request for a native QuickBooks connector, and that’s a more reliable path than using the browser. Please add your vote there: Grok Bot: QuickBooks Online as a first-party Cursor MCP connector
Until that connector exists, you can connect QuickBooks as a custom MCP server in Settings > Plugins. That kind of server talks directly to the API, so browser checks don’t get in the way. Just keep in mind that these are third-party solutions, and reliability depends on the specific server.
Bot access to your local browser isn’t supported yet. I’ve passed your use case and the web app debugging scenario on to the team. There’s also a separate thread about local computer use in general, and it’s worth posting there too: Local computer use for Grok Bots