MCP Web Curl MCP Server

If you want an AI assistant working directly with MCP Web Curl, the mcp web curl mcp server is the bridge. A universal CLI and MCP server tool for fetching, extracting, and processing web and API content. Supports resource blocking, authentication, Google Custom Search, and robust automation.

What MCP Web Curl does

Google Custom Search API is free with usage limits (e.g., 100 queries per day for free, with additional queries requiring payment). For full details on quotas, pricing, and restrictions, see the official documentation.

Tools it exposes

Once connected, the assistant can call these 7 tools directly:

• browser_flow — One-call browser workflow (optional navigate → optional actions → return ONE result)
• browser_configure — Set proxy/user-agent/viewport (session persistence is always on via user_data/)
• browser_close — Close browser and tabs (also auto-closes after 15 minutes of inactivity)
• multi_search — Run multiple Google searches in parallel (the only exposed search entrypoint)
• fetch_api — REST API request with response truncation (limit)
• download_file — Download a file from a URL
• parse_document — Extract text from PDF/DOCX URLs

Installing the mcp web curl mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 4 environment variables: APIKEY_GOOGLE_SEARCH, CX_GOOGLE_SEARCH, YOUR_GOOGLE_API_KEY, YOUR_CX_ID. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Browser automation servers are the ones people reach for when a site has no API — the assistant drives a real page instead of guessing at endpoints. MCP Web Curl sits in that group, and the shape of its toolset — browser_flow, browser_configure, browser_close among others — tells you what it is really for. Worth comparing against the other browser automation servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 7 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use MCP Web Curl.
• Maintained by rayss868, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp web curl mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.