Skip to main content
ZenRows handles the hard parts of web access so your agents don’t have to. Anti-bot bypass, JavaScript rendering, and residential proxies come built in on every tool call. Use the hosted MCP server to reach any public website, or route scraped data through MCP Tunnels when your infrastructure can’t be exposed to the internet.

What is Claude Managed Agents?

Claude Managed Agents is Anthropic’s hosted agent platform. It lets you build and deploy agents that call external tools, including MCP servers, without managing orchestration infrastructure yourself. Agents are configured and run from the Claude Console.

Key benefits

  • No-code web access for your agents
    Connect ZenRows MCP in the Console and your agent can scrape any website by describing the task in plain English. No selectors, no proxy management, no anti-bot tuning.
  • Anti-bot bypass on every tool call
    Premium residential proxies, JavaScript rendering, and stealth fingerprinting come standard. Your agents reach JavaScript-heavy SPAs, Cloudflare-protected sites, and geo-restricted pages without configuration.
  • Private network routing with MCP Tunnels
    MCP Tunnels creates an outbound-only encrypted connection from your infrastructure to Anthropic’s backend. Scraped data flows directly into your internal systems with no inbound ports, no firewall changes, and no public endpoints required.
  • Works with the Messages API too
    Use the same tunneled MCP server programmatically through the Anthropic Messages API, alongside the Console-based agent interface.

Use cases

The Claude Managed Agents and ZenRows combination unlocks a wide range of agent workflows:
Agents that visit multiple URLs, follow citations, and synthesize findings from across the web into a single brief.
Agents that scrape company websites, find pricing pages and product launches, and write enriched profiles into your CRM.
Agents that periodically check competitor pricing pages, blog posts, and changelogs, then surface what changed since the last run.
For regulated industries, route scraped data through MCP Tunnels directly into internal databases and pipelines without touching the public internet.
Agents that navigate multi-step checkout flows, login-walled forms, or job applications using ZenRows’ browser tools.

Get started

ZenRows MCP connects to Claude Managed Agents through three paths. Pick the one that fits your setup.
Use this option when your agent only needs to scrape public websites. This is the simplest path — no infrastructure required.Prerequisites
1

Open Managed Agents in the Console

In the Claude Console sidebar, go to Managed Agents > Sessions and click New session.
If you don’t see Managed Agents in the sidebar, your account may not have access yet. Claude Managed Agents is currently in beta. Request access to try it.
2

Add the ZenRows MCP server

When configuring the agent, click + MCP Server and enter the following:
FieldValue
Server URLhttps://mcp.zenrows.com/mcp
TransportStreamable HTTP
AuthorizationBearer YOUR_ZENROWS_API_KEY
Replace YOUR_ZENROWS_API_KEY with your key from the ZenRows dashboard.
Most MCP clients accept an authorization field that automatically wraps the value as a Bearer token. If the Console provides a free-form headers field instead, set Authorization: Bearer YOUR_ZENROWS_API_KEY manually.
3

Start scraping

Once connected, your agent can access all ZenRows tools. Describe the task in plain English:
Get the product names and prices from https://www.scrapingcourse.com/ecommerce/.
Scrape https://www.scrapingcourse.com/antibot-bypass using Premium Proxies.
Open https://www.scrapingcourse.com/ecommerce/ in a browser, type "hoodie" into the search field, press Enter, wait for results to load, then extract all matching product names and prices.

Troubleshooting

The tunnel does not appear in the MCP server dropdown

The tunnel must have at least one active CA certificate registered in the Console. A tunnel showing “Needs certificate” will not appear in the picker. Register a certificate and try again.

The agent cannot reach the upstream MCP server

Confirm the upstream value in config.yaml is reachable from the container running the proxy. On Docker Desktop, use host.docker.internal instead of localhost to reach services on the host machine. On Linux, use the host’s LAN IP or add host-gateway as described in Step 3.

Connection errors after adding the tunnel

Check the proxy and cloudflared container logs:
docker compose logs mcp-proxy
docker compose logs cloudflared
Common causes are a mismatched certificate or a revoked tunnel token. Generate a new token from the Console, update your .env file, and restart the stack.

The scrape tool is not available

Confirm the ZenRows local MCP server is running and that the upstream port in config.yaml matches the port the server is listening on. The default port is 8080. You can verify with npx -y @zenrows/mcp --help. For more help, see the ZenRows MCP overview and the Anthropic MCP Tunnels troubleshooting guide.

FAQ (Frequently asked questions)

No. If your agent only needs to scrape public websites, connect through the ZenRows hosted MCP server (Option A). MCP Tunnels is only needed when scraped data has to flow into private infrastructure or when compliance requirements prevent exposing systems to the internet.
For Claude Managed Agents and the Messages API, use the remote MCP server URL (https://mcp.zenrows.com/mcp) or a tunneled URL. The local stdio package (@zenrows/mcp) is for desktop AI clients like Claude Desktop that run the server as a local subprocess. When using MCP Tunnels, the local MCP server runs inside your private network behind the tunnel proxy, not as a local subprocess on your laptop.
Option A uses the ZenRows hosted MCP server directly over the public internet. It is simpler to set up and works for most use cases. Option B routes all traffic through a private encrypted tunnel. Use it when your internal systems cannot be exposed to the internet, or when your industry has compliance requirements around data routing.
Yes. Add additional routes to config.yaml, each with a different subdomain. Each route maps to a different upstream MCP server inside your network. In the Console, attach each subdomain as a separate MCP server in the agent session.
Both use MCP Tunnels for private network routing. Option B connects through the Claude Console and is aimed at no-code or low-code agent configuration. Option C connects programmatically through the Anthropic Messages API and is aimed at developers building applications directly on top of the API.