Integrate real-time Scrapeless Google SERP(Google Search, Google Flight, Google Map, Google Jobs....) results into your LLM applications. This server
Scrapeless MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Integrate real-time Scrapeless Google SERP(Google Search, Google Flight, Google Map, Google Jobs....) results into your LLM applications. This server enables.
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:
Once Scrapeless is connected, these are the calls the assistant has available:
Example — The Example tool exposed by this servergoogle_search — Universal information search enginegoogle_trends — Get trending search data from Google Trendsbrowser_create — Create or reuse a cloud browser session using Scrapelessbrowser_close — Closes the current session by disconnecting the cloud browserbrowser_goto — Navigate browser to a specified URLbrowser_go_back — Go back one step in browser historybrowser_go_forward — Go forward one step in browser historybrowser_click — Click a specific element on the pagebrowser_type — Type text into a specified input fieldbrowser_press_key — Simulate a key pressbrowser_wait_for — Wait for a specific page element to appearYou will need 3 environment variables: SCRAPELESS_KEY, YOUR_SCRAPELESS_KEY, BROWSER_PROFILE_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Scrapeless's toolset — Example, google_search, google_trends and 11 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Example | The Example tool exposed by this server. |
| 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. |
🌐 Streamable HTTP (Hosted API Mode)
```JSON
{
"mcpServers": {
"Scrapeless MCP Server": {
"type": "streamable-http",
"url": "https://api.scrapeless.com/mcp",
"headers": {
"x-api-token": "YOUR_SCRAPELESS_KEY"
},
"disabled": false,
"alwaysAllow": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SCRAPELESS_KEY | Credential the server authenticates with. | Yes |
| YOUR_SCRAPELESS_KEY | Credential the server authenticates with. | Yes |
| BROWSER_PROFILE_ID | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.