Web Scrapper Stdio MCP Server

Or with Docker Compose: ```sh docker compose --profile service up -d ```

Local serverstdioPython

What is the Web Scrapper Stdio MCP server?

Web Scrapper Stdio MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Or with Docker Compose: sh docker compose --profile service up -d .

What you get

  • Headless browser scraping (Playwright, BeautifulSoup, Markdownify)
  • Outputs Markdown, text, or HTML
  • Designed for MCP (Model Context Protocol) stdio/JSON-RPC integration
  • Dual transport — stdio (default) and Streamable HTTP for shared service mode
  • Persistent browser pool — Chromium stays alive across requests for fast scraping
  • Smart DOM wait — MutationObserver-based content stabilization instead of fixed sleep

What the assistant can call

Once Web Scrapper Stdio is connected, these are the calls the assistant has available:

  • Transport — The Transport tool exposed by this server

Configuration and credentials

You will need 3 environment variables: MCP_HTTP_HOST, CAPTCHA_API_KEY, CAPTCHA_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at ghcr.io/justazul/web-scrapper-stdio on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Web Scrapper Stdio's toolset — Transport — is a fair guide to whether it matches your workflow. It is maintained by JustAzul; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Web Scrapper Stdio's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the web scrapper stdio mcp server does with a few real requests.

Available tools

ToolWhat it does
TransportThe Transport tool exposed by this server.

How to install the Web Scrapper Stdio MCP server

{
  "mcpServers": {
    "web-scrapper-stdio": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/justazul/web-scrapper-stdio"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MCP_HTTP_HOSTEndpoint or connection string the server talks to.Optional
CAPTCHA_API_KEYCredential the server authenticates with.Yes
CAPTCHA_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Web Scrapper Stdio to Transport.

Frequently asked questions

It connects Web Scrapper Stdio to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Transport) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Web Scrapper Stdio directly.