Enterprise DNA
M MCP Servers Developer low

scrapeless-ai/scrapeless-mcp-server

by Various

Scrapeless Mcp Server

S

MCP

scrapeless-ai/scrapeless-mcp-server

Added 1 June 2026

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

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.

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