PyScrappy MCP Server

PyScrappy MCP server exists for a simple reason — assistants are far more useful when they can act on PyScrappy directly instead of describing what you should do. Web-scraping toolkit with 22 tools for structured web data as JSON for AI agents.

What you get

PyScrappy is an AI-native web scraping toolkit that turns websites into structured, LLM-ready data. Use it as a Python library or expose it as an MCP server for AI agents.

• Generic scraper — — give it any URL, get back structured text, links, images, tables, and metadata
• LLM-ready output — — .to_markdown() turns any result into clean Markdown; also .to_json() and .to_dataframe()
• MCP server — — expose the scrapers as tools for AI agents (Claude, Cursor, local LLMs, …)
• JS rendering — — optional Playwright backend for JavaScript-heavy sites
• Custom selectors — — pass CSS selectors to extract exactly what you need
• Concurrent scraping — — scrape_many / scrape_all run scrapes in parallel

What the assistant can call

Once PyScrappy is connected, these are the calls the assistant has available:

• scrape_url — Scrape any URL — text, links, images, tables, metadata
• scrape_wikipedia — Fetch a Wikipedia article (full / paragraphs / headers)
• scrape_stock — Yahoo Finance quotes, history, and profiles
• scrape_news — RSS/Atom feeds, auto-discovered site feeds, or a single article
• search_images — Image search (returns URLs + metadata)
• search_youtube — YouTube video search
• search_linkedin_jobs — Public LinkedIn job listings
• search_github — GitHub repository search (stars, language, …)
• search_hackernews — Hacker News story search (points, comments)
• search_books — Book search via Open Library (title, author, year)
• get_weather — Current weather for a place (no key)
• get_crypto — Cryptocurrency prices and market data (CoinGecko)

Setting it up

The server ships on PyPI as pyscrappy, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 2 environment variables: OMDB_API_KEY, YOUR_KEY. 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.

Choosing this one

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. PyScrappy's toolset — scrape_url, scrape_wikipedia, scrape_stock and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mldsveda; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against PyScrappy'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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch PyScrappy.
• 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 pyscrappy mcp server does with a few real requests.