Scrapeless MCP Server
The Scrapeless MCP Server enables LLMs to fetch Google Search results dynamically for integration into AI workflows, chatbots, and research tools.
Perform Google Searches: Search the web using Scrapeless with a customizable query
Customize Search Location: Specify the country for results using the
glparameter (e.g., 'us', 'uk')Customize Search Language: Specify the language using the
hlparameter (e.g., 'en', 'es')Support Advanced Queries: Use search operators like
inurl:,site:,intitle:, and more
Provides web search capabilities through Google Search, allowing queries with support for advanced search operators like inurl:, site:, and intitle:, with options to customize country and language settings.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Scrapeless MCP Serversearch for the latest AI news and summarize top 3 articles"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

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
Crawl entire websites by following links and capture each page in multiple formats
AI Scraper Create an AI Scraper task for ChatGPT, Gemini, Perplexity, Copilot, Google AI Mode, Google AI Overview, Grok, or Alexa
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
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.

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.

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.

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.

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. |
Related MCP server: MCP Web Research Server
Setup Guide
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.

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_API_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_ID | x-browser-profile-id | Specifies a reusable browser profile ID for session continuity. |
BROWSER_PROFILE_PERSIST | x-browser-profile-persist | Enables persistent storage for cookies, local storage, etc. |
BROWSER_SESSION_TTL | x-browser-session-ttl | Defines the maximum session timeout in seconds. The session will automatically expire after this duration of inactivity. |
Integration with Claude Desktop
Open Claude Desktop
Navigate to:
Settings→Tools→MCP ServersClick "Add MCP Server"
Paste either the
StdioorStreamable HTTPconfig aboveSave and enable the server
Claude will now be able to issue web queries, extract content, and interact with pages using Scrapeless
Integration with Cursor IDE
Open Cursor
Press
Cmd + Shift + Pand search for:Configure MCP ServersAdd the Scrapeless MCP config using the format above
Save the file and restart Cursor (if needed)
Now you can ask Cursor things like:
"Search StackOverflow for a solution to this error""Scrape the HTML from this page"
And it will use Scrapeless in the background.
Supported MCP Tools
Name | Description |
google_search | Universal information search engine. |
google_trends | Get trending search data from Google Trends. |
browser_create | Create or reuse a cloud browser session using Scrapeless. |
browser_close | Closes the current session by disconnecting the cloud browser. |
browser_goto | Navigate browser to a specified URL. |
browser_go_back | Go back one step in browser history. |
browser_go_forward | Go forward one step in browser history. |
browser_click | Click a specific element on the page. |
browser_type | Type text into a specified input field. |
browser_press_key | Simulate a key press. |
browser_wait_for | Wait for a specific page element to appear. |
browser_wait | Pause execution for a fixed duration. |
browser_screenshot | Capture a screenshot of the current page. |
browser_get_html | Get the full HTML of the current page. |
browser_get_text | Get all visible text from the current page. |
browser_scroll | Scroll to the bottom of the page. |
browser_scroll_to | Scroll a specific element into view. |
scrape_html | Scrape a URL and return its full HTML content. |
scrape_markdown | Scrape a URL and return its content as Markdown. |
scrape_screenshot | Capture a high-quality screenshot of any webpage. |
crawl_start | Start an asynchronous crawl job from a base URL and return its job id. |
crawl_cancel | Cancel an in-progress crawl job by its id. |
crawl_result | Poll a crawl job by its id until it completes and return the crawled data. |
ai_scraper | Create an AI Scraper task for ChatGPT, Gemini, Perplexity, Copilot, Google AI Mode, Google AI Overview, Grok, or Alexa. |
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 to free-form text. Use tools like
scrape_html,scrape_markdown, or targetedbrowser_get_textwith 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:
Email: market@scrapeless.com
Official Website: https://www.scrapeless.com
Community Forum: https://discord.gg/Np4CAHxB9a
Available Tools
1 toolgoogle-searchC
Fetch Google Search Results
| Name | Required | Description | Default |
|---|---|---|---|
| gl | No | Parameter defines the country to use for the Google search. It's a two-letter country code. (e.g., us for the United States, uk for United Kingdom, or fr for France). | |
| hl | No | Parameter defines the language to use for the Google search. It's a two-letter language code. (e.g., en for English, es for Spanish, or fr for French). | |
| query | Yes | Parameter defines the query you want to search. You can use anything that you would use in a regular Google search. e.g. inurl:, site:, intitle:. We also support advanced search query parameters such as as_dt and as_eq. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Fetch' implies a read operation, but it doesn't disclose critical traits like rate limits, authentication needs, response format, pagination, or error handling. For a search tool with zero annotation coverage, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with just three words, front-loaded and zero waste. Every word ('Fetch Google Search Results') directly contributes to stating the tool's purpose without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (search functionality with parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values, error cases, or behavioral constraints, leaving the agent with insufficient information to use the tool effectively beyond basic input.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all three parameters (query, gl, hl) with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as examples or usage tips. Baseline 3 is appropriate when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Fetch Google Search Results' states the basic action (fetch) and resource (Google Search Results), but it's vague about scope and format. It doesn't specify what kind of results (e.g., web pages, images, news) or how many results are returned. Without sibling tools, differentiation isn't needed, but the purpose could be more specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. There are no sibling tools mentioned, so no explicit comparisons are needed, but it lacks context about use cases, prerequisites, or limitations. It's a generic statement with no usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'google-search' has a clear and distinct purpose of fetching Google search results, so agents cannot misselect between multiple options.
The single tool name 'google-search' follows a consistent pattern of verb-noun (search as the verb, Google as the noun context), and with only one tool, there is no inconsistency to evaluate. The naming is clear and adheres to a predictable structure.
The server has only one tool, which feels thin and under-scoped for a scraping-related domain. A single tool for fetching Google search results may not provide sufficient coverage for typical scraping workflows, such as parsing results, handling pagination, or interacting with other search engines, making it borderline too few for the apparent purpose.
Inferring the domain as web scraping or search data fetching, the tool surface is severely incomplete. It only offers a basic search fetch without supporting operations like filtering results, extracting specific data, managing queries, or integrating with other scraping tasks, leading to significant gaps that could cause agent failures in broader scraping scenarios.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
MCP server for Google search results via SERP API
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to perform web searches using Google's Custom Search API through a standardized interface.147MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots.131,56720MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots in real-time.41,5679MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that provides web and image search capabilities through Google's Custom Search API, allowing AI assistants like Claude to access current information from the internet.22
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/scrapeless-ai/scrapeless-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server