Skip to main content
The Zenrows connector gives Claude live web data through the remote Zenrows MCP server at https://mcp.zenrows.com/mcp. You sign in to your Zenrows account with OAuth when you connect, so there is no API key to copy and nothing to install. You add the connector in Claude on the web or Claude Desktop, and it also works in Cowork. Once added, it is available in the Claude apps for iOS and Android the next time you sign in there.

​
Before you start

You need:
  • A Zenrows account. Sign up if you don’t have one. Requests use credits on your Zenrows plan.
  • A Claude account on any plan. Custom connectors are available on Free, Pro, Max, Team and Enterprise; Free plans can add one custom connector.

​
Add the connector

1

Open Connectors

In Claude, go to Customize > Connectors, click + Add, then Add custom connector.
2

Enter the server

Enter Zenrows as the name and https://mcp.zenrows.com/mcp as the URL, then click Continue. Click Continue again on the detected authentication settings.
3

Choose how to sign in

Under Authentication, choose Sign in now. Under OAuth client, choose Register automatically, then click Add.
4

Sign in to Zenrows

Sign in to your Zenrows account in the window that opens and approve access.

​
Use Zenrows in a conversation

Click + at the lower left of the chat, select Connectors and check that Zenrows is on. Then ask in plain language:
Claude picks the right tool for each request: scrape for a single page, extract for structured data, batch_* for a list of URLs and browser_* for multi-step tasks.
Using Claude Code? Install the Zenrows plugin instead. It bundles the same connector with skills that guide Claude through each task. See the plugin README, or set up Claude Code with an API key.

​
Troubleshooting

Claude doesn’t use Zenrows Check that Zenrows is turned on under + > Connectors in the conversation. You can also name it in the prompt, for example “Use Zenrows to fetch …”. Sign-in fails or returns an error Remove the connector and add it again, choosing Register automatically under OAuth client. Zenrows returns AUTH003 The sign-in is no longer valid, for example because the API key was rotated. Go to Customize > Connectors, select Zenrows, disconnect it and connect again. Zenrows returns AUTH004 or AUTH006 These are plan limits, so reconnecting doesn’t clear them. AUTH004 means the account’s credit allowance is spent and AUTH006 means too many requests are running at once. See MCP errors for how to resolve each one. Zenrows returns AUTH014 The API key the connector signs in with reached one of its credit caps. Your other keys keep working. Raise or remove the cap, or wait for its window to reset; reconnecting doesn’t clear it. For error codes and other issues, see the Zenrows MCP overview.