Summary
The blocked-page problem handed to a service, with the output format as the only real decision.
scrape_url_html and scrape_url_markdown take the same two parameters and differ in what they hand back, so the choice is made on what you plan to do next: parse the markup, or read the prose. The surface stops there — one URL per call, with browserCommands as the single lever for pages that only reveal their content after a click or a scroll.
What it is
A two-tool front end to the ScrAPI scraping service, one tool per output format, both taking the same URL.
What you get
- Website content reached through ScrAPI where bot detection, captchas or geolocation restrictions stand in the way of a direct fetch
- HTML output when advanced parsing is required, and Markdown when the text content matters and the page structure does not
- An optional browserCommands list that interacts with the page before the content is taken
Requirements
A ScrAPI key in SCRAPI_API_KEY. Pages are addressed one URL at a time, and the browserCommands list is the only way to reach content that appears after an interaction.
Setup effort
One command plus a key — npx -y @deventerprisesoftware/scrapi-mcp, then supply credentials