search-web

Scrapeless (Google Search)

scrapeless-ai

by scrapeless-ai

Access the Scrapeless Google Search API for customizable queries by text, country, or language. Easily integrate with cu

Provides a bridge to the Scrapeless API for performing Google searches with customizable parameters including query text, country code, and language preferences.

github stars

156

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Bypasses blocking and rate limitsCustomizable search parameters

best for

  • / AI research assistants gathering web information
  • / Automated content research workflows
  • / Building search-powered AI applications

capabilities

  • / Perform Google searches with custom queries
  • / Filter results by country and language
  • / Extract search result titles and summaries
  • / Retrieve search result URLs
  • / Access real-time search data

what it does

Connects AI models to Google Search through the Scrapeless API, allowing programmatic search queries with customizable parameters like location and language.

about

Scrapeless (Google Search) is an official MCP server published by scrapeless-ai that provides AI assistants with tools and capabilities via the Model Context Protocol. Access the Scrapeless Google Search API for customizable queries by text, country, or language. Easily integrate with cu It is categorized under search web.

how to install

You can install Scrapeless (Google Search) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

Scrapeless (Google Search) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

preview

Scrapeless MCP Server

Welcome to the official Scrapeless Model Context Protocol (MCP) Server — a powerful integration layer that empowers LLMs, AI Agents, and AI applications to interact with the web in real time.

Built on the open MCP standard, Scrapeless MCP Server seamlessly connects models like ChatGPT, Claude, and tools like Cursor and Windsurf to a wide range of external capabilities, including:

  • Google services integration (Search, Trends)
  • Browser automation for page-level navigation and interaction
  • Scrape dynamic, JS-heavy sites—export as HTML, Markdown, or screenshots

Whether you're building an AI research assistant, a coding copilot, or autonomous web agents, this server provides the dynamic context and real-world data your workflows need—without getting blocked.

Usage Examples

  1. Automated Web Interaction and Data Extraction with Claude

Using Scrapeless MCP Browser, Claude can perform complex tasks such as web navigation, clicking, scrolling, and scraping through conversational commands, with real-time preview of web interaction results via live sessions.

preview

  1. Bypassing Cloudflare to Retrieve Target Page Content

Using the Scrapeless MCP Browser service, the Cloudflare page is automatically accessed, and after the process is completed, the page content is extracted and returned in Markdown format.

preview

  1. Extracting Dynamically Rendered Page Content and Writing to File

Using the Scrapeless MCP Universal API, the JavaScript-rendered content of the target page above is scraped, exported in Markdown format, and finally written to a local file named text.md.

preview

  1. Automated SERP Scraping

Using the Scrapeless MCP Server, query the keyword “web scraping” on Google Search, retrieve the first 10 search results (including title, link, and summary), and write the content to the file named serp.text.

preview

Here are some additional examples of how to use these servers:

Example
Search scrapeless by Google search.
Find the search interest for "AI" over the last year.
Use a browser to visit chatgpt.com, search for "What's the weather like today?", and summarize the results.
Scrape the HTML content of scrapeless.com page.
Scrape the Markdown content of scrapeless.com page.
Get screenshots of scrapeless.com.

Setup Guide

  1. Get Scrapeless Key
  • Log in to the Scrapeless Dashboard(Free trial available)
  • Then click "Setting" on the left -> select "API Key Management" -> click "Create API Key". Finally, click the API Key you created to copy it.

preview

  1. Configure Your MCP Client

Scrapeless MCP Server supports both Stdio and Streamable HTTP transport modes.

🖥️ Stdio (Local Execution)

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

🌐 Streamable HTTP (Hosted API Mode)

{
  "mcpServers": {
    "Scrapeless MCP Server": {
      "type": "streamable-http",
      "url": "https://api.scrapeless.com/mcp",
      "headers": {
        "x-api-token": "YOUR_SCRAPELESS_KEY"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Advanced Options

Customize browser session behavior with optional parameters. These can be set via environment variables (for Stdio) or HTTP headers (for Streamable HTTP):

Stdio (Env Var)Streamable HTTP (HTTP Header)Description
BROWSER_PROFILE_IDx-browser-profile-idSpecifies a reusable browser profile ID for session continuity.
BROWSER_PROFILE_PERSISTx-browser-profile-persistEnables persistent storage for cookies, local storage, etc.
BROWSER_SESSION_TTLx-browser-session-ttlDefines the maximum session timeout in seconds. The session will automatically expire after this duration of inactivity.

Integration with Claude Desktop

  1. Open Claude Desktop
  2. Navigate to: SettingsToolsMCP Servers
  3. Click "Add MCP Server"
  4. Paste either the Stdio or Streamable HTTP config above
  5. Save and enable the server
  6. Claude will now be able to issue web queries, extract content, and interact with pages using Scrapeless

Integration with Cursor IDE

  1. Open Cursor
  2. Press Cmd + Shift + P and search for: Configure MCP Servers
  3. Add the Scrapeless MCP config using the format above
  4. Save the file and restart Cursor (if needed)
  5. Now you can ask Cursor things like:
    1. "Search StackOverflow for a solution to this error"
    2. "Scrape the HTML from this page"
  6. And it will use Scrapeless in the background.

Supported MCP Tools

NameDescription
google_searchUniversal information search engine.
google_trendsGet trending search data from Google Trends.
browser_createCreate or reuse a cloud browser session using Scrapeless.
browser_closeCloses the current session by disconnecting the cloud browser.
browser_gotoNavigate browser to a specified URL.
browser_go_backGo back one step in browser history.
browser_go_forwardGo forward one step in browser history.
browser_clickClick a specific element on the page.
browser_typeType text into a specified input field.
browser_press_keySimulate a key press.
browser_wait_forWait for a specific page element to appear.
browser_waitPause execution for a fixed duration.
browser_screenshotCapture a screenshot of the current page.
browser_get_htmlGet the full HTML of the current page.
browser_get_textGet all visible text from the current page.
browser_scrollScroll to the bottom of the page.
browser_scroll_toScroll a specific element into view.
scrape_htmlScrape a URL and return its full HTML content.
scrape_markdownScrape a URL and return its content as Markdown.
scrape_screenshotCapture a high-quality screenshot of any webpage.

Security Best Practices

When using Scrapeless MCP Server with LLMs (like ChatGPT, Claude, or Cursor), it's critical to handle all scraped or extracted web content with care. Web data is untrusted by default, and improper handling may expose your application to prompt injection or other security vulnerabilities.

✅ Recommended Practices

  • Never pass raw scraped content directly into LLM prompts. Raw HTML, JavaScript, or user-generated text may contain hidden injection payloads.
  • Sanitize and validate all extracted content. Strip or escape potentially harmful tags and scripts before using content in downstream logic or AI models.
  • Prefer structured extraction over free-form text. Use tools like scrape_html, scrape_markdown, or targeted browser_get_text with known-safe selectors to extract only the content you trust.
  • Apply domain or selector whitelisting when scraping dynamically generated pages, to restrict data flow to known and trusted sources.
  • Log and monitor all outbound requests made via browser or scraping tools, especially if you're handling sensitive data, tokens, or internal network access.

🚫 Avoid

  • Injecting scraped HTML directly into prompts
  • Letting users specify arbitrary URLs or CSS selectors without validation
  • Storing unfiltered scraped content for future prompt usage

Community

Contact Us

For questions, suggestions, or collaboration inquiries, feel free to contact us via:

FAQ

What is the Scrapeless (Google Search) MCP server?
Scrapeless (Google Search) is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Scrapeless (Google Search)?
This profile displays 40 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

Use Cases

Web Research & Information Gathering

Fetch and extract information from websites automatically

Example

Research competitor pricing, scrape product reviews, monitor news mentions

Automate 5-10 hours/week of manual web research

Content Monitoring & Alerts

Track website changes, new content, price updates

Example

Monitor competitor blog for new posts, track stock availability, watch for pricing changes

Stay informed without manual checking, never miss important updates

Data Extraction & Aggregation

Extract structured data from multiple websites

Example

Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data

Build datasets 100x faster than manual copying

API-less Integration

Interact with services that don't offer APIs

Example

Check form submissions, validate website functionality, test user flows

Automate interactions with any website, even without API

Implementation Guide

Prerequisites

  • Claude Desktop or Cursor with MCP support
  • Understanding of web scraping ethics and robots.txt
  • Rate limiting awareness to avoid overwhelming target sites
  • Knowledge of legal restrictions on data collection

Time Estimate

20-40 minutes including configuration and testing

Installation Steps

  1. 1.Install web automation MCP server via npm or pip
  2. 2.Configure allowed domains and rate limits in MCP config
  3. 3.Test with simple fetch: 'Get content from example.com'
  4. 4.Progress to extraction: 'Extract all product prices from this page'
  5. 5.Set up monitoring: 'Check this URL daily for changes'
  6. 6.Parse structured data: 'Create CSV from this table'
  7. 7.Respect robots.txt and rate limits always

Troubleshooting

  • 403 Forbidden: Website blocks bots—respect their wishes, use official API instead
  • Rate limit errors: Slow down requests, add delays between fetches
  • Stale data: Target site changed HTML structure—update selectors
  • Timeout errors: Site is slow or blocking—increase timeout, try different user agent
  • JavaScript-rendered content: Use headless browser MCP servers for dynamic sites

Best Practices

✓ Do

  • +Check robots.txt and respect crawl rules
  • +Rate limit requests: 1-2 requests/second maximum
  • +Use official APIs when available instead of scraping
  • +Identify your bot with descriptive user agent
  • +Cache results to minimize repeated requests
  • +Handle errors gracefully with retries and fallbacks
  • +Validate extracted data for accuracy

✗ Don't

  • Don't scrape sites that explicitly forbid it (robots.txt, ToS)
  • Don't overwhelm servers with rapid requests—use rate limiting
  • Don't scrape personal data without consent and legal basis
  • Don't ignore copyright on extracted content
  • Don't assume HTML structure is stable—handle changes
  • Don't use scraped data for commercial purposes without permission

💡 Pro Tips

  • Use CSS selectors or XPath for robust data extraction
  • Set up monitoring alerts for extraction failures (structure changed)
  • Implement exponential backoff for retries on failures
  • Store raw HTML for reprocessing if extraction logic changes
  • Combine with data analysis tools for insights from extracted data
  • Consider using official APIs or RSS feeds as more stable alternatives

Technical Details

Architecture

MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.

Protocols

  • HTTP/HTTPS
  • WebSocket (for real-time sites)
  • Puppeteer/Playwright (for JavaScript sites)

Compatibility

  • Static HTML sites
  • JavaScript-rendered SPAs (with headless browser)
  • REST APIs
  • GraphQL endpoints

When to Use This

✓ Use When

Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.

✗ Avoid When

Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.

Integration

  • Scheduled monitoring with change detection
  • Multi-source data aggregation pipelines
  • Fallback to web scraping when API rate limits hit
  • Headless browser for JavaScript-heavy sites

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.640 reviews
  • Camila Malhotra· Dec 28, 2024

    Scrapeless (Google Search) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Diego Park· Dec 28, 2024

    Scrapeless (Google Search) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Chaitanya Patil· Dec 20, 2024

    Scrapeless (Google Search) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Mia Sanchez· Dec 4, 2024

    Useful MCP listing: Scrapeless (Google Search) is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Xiao Dixit· Nov 23, 2024

    Strong directory entry: Scrapeless (Google Search) surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Rahul Santra· Nov 19, 2024

    Scrapeless (Google Search) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Omar Haddad· Nov 19, 2024

    I recommend Scrapeless (Google Search) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Piyush G· Nov 11, 2024

    Scrapeless (Google Search) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Olivia Johnson· Oct 14, 2024

    I recommend Scrapeless (Google Search) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Pratham Ware· Oct 10, 2024

    According to our notes, Scrapeless (Google Search) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

showing 1-10 of 40

1 / 4