zenrows/zenrows-mcp

Browser automation

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

21 stars 5 forks 品質 85 トレンド 30MIT

Repository Install

Official ZenRows MCP integration

概要

The Zenrows MCP (Model Context Protocol) server is the standard way AI systems use Zenrows' web data infrastructure. A single connection gives your AI assistant, agent, or application reliable, real-time access to the live web, including the protected web. - Get reliable access to protected sites at scale, without building anti-bot handling yourself. - Proxy rotation, headless browser orchestration, anti-bot handling, and session management run on Zenrows' infrastructure. - Works with any MCP client, including AI assistants, agent frameworks, AI SDKs, IDE plugins, and custom applications. - Describe the task naturally and the AI picks the right tool. No selectors, no proxy management, no anti-bot tuning. Zenrows MCP supports two transport options. Both expose the same set of tools and capabilities. Pick the one that fits your client. - no signup, no key. The first tool call creates a Free account (5,000 credits/month) that you can claim later, keeping the key and its usage.

README

以下は原文 README の抜粋です。原文を見る。

Zenrows MCP Server

The Zenrows MCP (Model Context Protocol) server is the standard way AI systems use Zenrows’ web data infrastructure. A single connection gives your AI assistant, agent, or application reliable, real-time access to the live web, including the protected web.

📚 Full documentation: docs.zenrows.com/mcp/overview

Why Zenrows MCP

Reach sites that normally block bots. Get reliable access to protected sites at scale, without building anti-bot handling yourself.
Managed web data infrastructure. Proxy rotation, headless browser orchestration, anti-bot handling, and session management run on Zenrows’ infrastructure.
Plug into any AI you already use. Works with any MCP client, including AI assistants, agent frameworks, AI SDKs, IDE plugins, and custom applications.
Plain English, no scraping code. Describe the task naturally and the AI picks the right tool. No selectors, no proxy management, no anti-bot tuning.

Quick start

Zenrows MCP supports two transport options. Both expose the same set of tools and capabilities. Pick the one that fits your client.

What works without a key:

Local (npx @zenrows/mcp): no signup, no key. The first tool call creates a Free account (5,000 credits/month) that you can claim later, keeping the key and its usage. Opt out with ZENROWS_AUTO_SIGNUP=false. In CI, set ZENROWS_API_KEY as a secret or persist ZENROWS_HOME between runs.
Remote (https://mcp.zenrows.com/mcp): initialize and tools/list answer without a key; tool calls need one (OAuth in clients that support it, or a Bearer key). The remote server never creates accounts by itself. A headless agent can create a Free account with POST https://app.zenrows.com/api/agent/signup and use the returned apiKey as the Bearer token. The endpoint may first answer 428 with a short question; POST {"challenge_id": "...", "answer": "..."} back to the same URL to get the key.

Remote MCP server

Use the hosted Zenrows MCP server when your AI application calls an LLM API directly. The server runs on Zenrows’ infrastructure, so there is nothing to install, configure, or update.

Server URL:

https://mcp.zenrows.com/mcp

Transport: Streamable HTTP

Authentication: OAuth or API key as Bearer token. Pass your Zenrows API key in the Authorization header on every request (or complete OAuth in clients that support it).

Authorization: Bearer YOUR_ZENROWS_API_KEY

GitHub で README 全文を見る

インストール

npx -y @zenrows/mcp

MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
  "mcpServers": {
    "zenrows": {
      "command": "npx",
      "args": ["-y", "@zenrows/mcp"],
      "env": {
        "ZENROWS_API_KEY": "YOUR_ZENROWS_API_KEY"
      }
    }
  }
}