Skip to main content

​
Can I use BrowserAct through MCP in QwenPaw?

Yes, if QwenPaw supports a remote MCP connection with Bearer API Key authentication. Connect to https://mcp.browseract.com/mcp/ with your general BrowserAct API Key. Your agent can then find and run your accessible published Bots and official templates; you do not need to expose each Bot individually. Both Workflow Built Bots and Agent Built Bots support MCP. See BrowserAct MCP for the setup steps.

​
Can BrowserAct MCP connect to the Claude.ai web app?

Not currently. Support for connecting BrowserAct MCP to Claude.ai on the web is under development.

​
Can I use BrowserAct with AI agents other than Claude?

Yes. BrowserAct Bots can connect to supported Claude clients, such as Claude Desktop and Claude Code, and to other compatible AI agents through MCP. Connect your client to https://mcp.browseract.com/mcp/ using your general BrowserAct API Key. One connection lets your agent find and run accessible published Bots and official templates, then retrieve their results. Individual Bot exposure is only needed when you choose a Custom MCP Server. BrowserAct provides connection guidance for clients such as Claude Desktop, Claude Code, Cursor, Windsurf, Gemini CLI, VS Code, and supported API-based agent environments. For setup details, see Connect to BrowserAct MCP.

​
Why does a REST API request fail with a Custom MCP Server key?

A Custom MCP Server key only grants access to its matching Custom Server. It cannot be used for BrowserAct REST API requests. Use a general BrowserAct API Key for REST API requests and the BrowserAct MCP connection at https://mcp.browseract.com/mcp/. For a Custom MCP Server, use the URL and independent MCP API Key shown on that Server’s connection page.

​
Where are API keys managed?

Open API & Integrations and use the API Keys section to create or manage a general BrowserAct API Key. See API Keys & Authentication. Custom MCP Server keys are managed separately on the selected Server’s Connect to Clients page.

​
Is Google Sheets a direct BrowserAct integration?

Not directly. Connect BrowserAct to Make, n8n, or Zapier, then add Google Sheets as the next step in your automation.

​
Can I integrate BrowserAct with platforms other than Make, n8n, and Zapier?

Yes. Use the BrowserAct API to connect a Bot to another application or automation platform. Compatible AI clients can also use BrowserAct MCP to find and run accessible published Bots and official templates. See BrowserAct MCP for setup. Make, n8n, and Zapier provide ready-to-use integration paths. Other platforms can connect through the API or MCP, depending on the platform’s capabilities.

​
How do I schedule a BrowserAct Bot to run automatically?

Use BrowserAct schedules when you want BrowserAct to run a published Bot automatically and email results from inside BrowserAct. See Schedule Bot Runs for setup steps. Use Make, n8n, or Zapier when you want an external automation platform to trigger the Bot and continue into other apps, such as Google Sheets, Slack, email, a database, or a CRM. In those platforms, schedule options, time zones, retries, and limits depend on the automation platform.