> ## Documentation Index
> Fetch the complete documentation index at: https://docs.browseract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent & Integrations FAQ

## Can I use BrowserAct through MCP in QwenPaw?

Yes, if QwenPaw supports connecting to a remote MCP server. Create a BrowserAct MCP Server, expose the required Bot as an MCP Tool, and add the MCP Server URL and API key to QwenPaw.

Both Workflow Built Bots and Agent Built Bots support MCP. See [Integrate BrowserAct with MCP](/integrations/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.

Create a BrowserAct MCP Server, expose the Bot as an MCP Tool, and connect the server to your MCP client with the MCP Server URL and API key.

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 [Workflow Built MCP setup](/integrations/mcp#convert-a-workflow-built-bot-into-an-mcp-tool) or [Agent Built MCP setup](/integrations/mcp#convert-an-agent-built-bot-into-an-mcp-tool).

## Why does a REST API request return an authorization error when I use an API key created from the MCP Server?

The API key created from the MCP Server panel is only used for MCP Server access. It cannot be used for REST API requests. MCP Server and REST API are separate modules, and their API keys are managed separately.

* **MCP Server key:** Used only for MCP client connections.
* **REST API key:** Used only for BrowserAct REST API calls.

## Where are API keys managed?

Open `Integrations` and select `Manage API Keys` to create, copy, edit, or delete an API key. For endpoints and API-based webhooks, see the API Reference.

## 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. BrowserAct Bots can also be exposed as MCP Tools for supported AI agents and MCP clients.

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 Make, n8n, or Zapier to trigger the Bot on a schedule. Build and test the Bot in BrowserAct first, then connect it to your automation and add a schedule trigger.

Schedule options, time zones, retries, and limits depend on the automation platform.