Summary
A browser-automation surface with the cookie-banner problem already solved.
The 29 tools match Microsoft's Playwright MCP surface, so anything written against that works here. What you get on top is the consent layer — the reason article scraping usually returns a wall of banner markup instead of the article.
What it is
A Playwright-based server with 29 tools: three for article extraction with cookie-consent handling, and the rest a full browser-automation surface — navigation, forms, tabs, network monitoring and element discovery.
What you get
- scrape_article_content — title, author, date, summary and body, in text, HTML or markdown
- get_page_screenshot and handle_cookie_consent — a screenshot after the banner is dealt with, or a consent check on its own
- browser_navigate, browser_click, browser_type, browser_hover, browser_select_option, browser_press_key, browser_handle_dialog, browser_file_upload, browser_close
- browser_pdf_save, browser_console_messages, browser_resize, browser_snapshot, browser_install, browser_generate_playwright_test
- manage_tabs, monitor_network, drag_drop and navigate_history for session-based work across pages
- browser_find_text, browser_find_element, browser_describe_element, browser_annotate_page, browser_get_element_text, browser_wait_for_page_state, browser_execute_javascript
- Cookie-consent handling across 30+ languages and 25+ consent frameworks
Requirements
Docker is the shortest path — the published image serves on port 3001, with a health check at /health. Building from source needs Node and a Playwright install. No credentials.
Setup effort
One command — docker run -p 3001:3001 descoped/mcp-web-scraper