scrape, extract, crawl_*, batch_*, browser_*, account_usage (see the tool reference)
Connect the server
Connect the Zenrows MCP server to your client first: see Connect your AI agent to Zenrows. Every connection option exposes the same tools.Read and summarize pages
Ask for any page in plain words. Zenrows renders JavaScript and handles anti-bot protection on its own, and returns clean markdown your agent can read.Get structured fields
Ask for the fields you want. Zenrows returns them as JSON instead of a full page, which keeps your agent’s context small.Discover every page on a site
Give a start page and say which pages you want. The agent crawls the site and returns the URLs, or the pages themselves.Scrape at scale
Hand the agent the whole list, a hundred URLs or a hundred thousand. It sends them to Zenrows as one job that runs in parallel in the cloud, so the conversation stays short and the results wait for you.
A two-URL test job came back
"status": "completed" with "stats": {"total": 2, "successful": 2, "spend": {"credits": 2}}.
Click, type and log in
Describe the steps the way you would to a colleague. The agent drives Zenrows Browser through them and reports back.Combine primitives in one prompt
The agent chains tools on its own when the prompt names the full outcome.Catalog to dataset
Read first, browse when needed
Research brief
Budget-aware run
Use the built-in MCP prompts
The server also ships three ready-made prompts. Clients that support MCP prompts list them in their prompt or slash-command menu, for example/mcp__zenrows__scrape_and_summarize in Claude Code.
Write prompts the agent follows
- Start with “Use Zenrows” so the agent reaches for live data instead of its memory.
- Describe the result, not the settings: “a table of name and price”, “as a visitor from Germany”, “after the reviews load”. The agent picks the parameters.
- Say the size of the job: “every product page”, “these 5,000 URLs”, “up to 50 pages”. Large lists run as one batch job.
- Name elements when you know them: a CSS selector such as
.priceturns a broad request into a precise one. - Close browser sessions in the same prompt.
Troubleshooting
- The agent answers without calling Zenrows: it used its own knowledge. Start the prompt with “Use Zenrows to…”.
- The tool list is empty: the server didn’t authenticate. Check the URL is exactly
https://mcp.zenrows.com/mcpand the Bearer token holds your key, then restart the client. - The agent reports a crawl or batch job as still running: large jobs take longer than one check. Ask it to keep checking until the job is complete.
AUTH004orAUTH014: the plan or the key needs more credits. Ask the agent to check your Zenrows credits, then see Track usage and control spend.
Related recipes
Connect your AI agent to Zenrows
Set up the MCP server in your client, step by step.
Automate scraping from your terminal with the CLI
The same jobs as shell commands and cron.
Build a research agent with live web data
Search, read and cite sources with one agent.
Let your AI assistant browse with Browser tools
Drive Zenrows Browser from a chat.