scrapeless-ai/scrapeless-mcp-server

Overview

Scrapeless MCP Server is a Model Context Protocol server for web scraping. It allows AI agents to request scraping tasks through a standardized interface. The tool is built with TypeScript and provides a bridge between AI models and web data extraction.

Best for

Best for
Developers building AI agents or assistants that need to fetch and process live web data

Use cases

• Integrating real-time web scraping into AI assistant workflows
• Extracting structured data from websites for agent reasoning
• Providing up-to-date web content to language models via MCP

How to use

Tools exposed

• BROWSER_PROFILE_ID
• BROWSER_PROFILE_PERSIST
• BROWSER_SESSION_TTL
• google_search
• google_trends
• browser_create
• browser_close
• browser_goto
• browser_go_back
• browser_go_forward
• browser_click
• browser_type
• browser_press_key
• browser_wait_for
• browser_wait
• browser_screenshot
• browser_get_html
• browser_get_text
• browser_scroll
• browser_scroll_to

Tested with

Claude Desktop, Cursor, Windsurf, ChatGPT

Example client config

{\n  "mcpServers": {\n    "Scrapeless MCP Server": {\n      "command": "npx",\n      "args": ["-y", "scrapeless-mcp-server"],\n      "env": {\n        "SCRAPELESS_API_KEY": "YOUR_SCRAPELESS_KEY"\n      }\n    }\n  }\n}

Notes

Scrapeless MCP Server is a Model Context Protocol server for web scraping. It allows AI agents to request scraping tasks through a standardized interface. The tool is built with TypeScript and provides a bridge between AI models and web data extraction.

161 stars on GitHub. Last updated 2025-09-23. Licensed MIT.

Use cases

• Integrating real-time web scraping into AI assistant workflows
• Extracting structured data from websites for agent reasoning
• Providing up-to-date web content to language models via MCP

Pros

• Leverages the Model Context Protocol for standardized agent-tool communication
• Open source with 161 GitHub stars and TypeScript codebase
• Simplifies adding web scraping capability to MCP-compatible AI systems

Cons

• Dependent on the broader MCP ecosystem for integration
• Limited documentation based on current repository description
• May not handle complex JavaScript-heavy sites without additional configuration

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.