Scrapely MCP Server
OfficialClick on "Deploy 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., "@Scrapely MCP ServerSearch Scrape.ly for a Google Maps scraper and run it for coffee shops in Austin"
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.
scrapely-mcp
An MCP server for Scrape.ly. It gives AI agents and MCP clients access to a Scrape.ly account: search the Store for Actors, read their README and input schema, run them, follow the runs, and read the results from datasets, key-value stores and logs. It can also manage saved tasks and search the Scrape.ly and Crawlee documentation.
The same package runs in two ways:
Hosted:
scrapely-mcp-http, a multi-tenant streamable HTTP server. Scrape.ly runs it behind the API athttps://api.scrape.ly/mcp. Most users connect to that URL and never install anything.Local:
scrapely-mcp-server, a stdio server started by a desktop MCP client on your machine.
Connect to the hosted server
Point your client at https://api.scrape.ly/mcp.
Clients that support MCP authorization find the OAuth flow on their own and ask you to sign in.
Otherwise send your API token as a header:
Authorization: Bearer <token>.Clients that cannot set headers can append
?token=<token>to the URL. URLs tend to end up in logs, so prefer the header.
Example for a client that takes a JSON config:
{
"mcpServers": {
"scrapely": {
"url": "https://api.scrape.ly/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}Related MCP server: AXE Fleet MCP Server
Run locally (stdio)
Requires Python 3.11 or newer.
uvx --from scrapely-mcp scrapely-mcp-server
# or
pip install scrapely-mcp
scrapely-mcp-serverThe token comes from SCRAPELY_TOKEN, or from the token field of ~/.scrapely/credentials.json or
~/.scrapely/auth.json. A token is required unless every selected tool works without one
(search-actors, fetch-actor-details and the docs tools).
{
"mcpServers": {
"scrapely": {
"command": "uvx",
"args": ["--from", "scrapely-mcp", "scrapely-mcp-server"],
"env": { "SCRAPELY_TOKEN": "YOUR_TOKEN" }
}
}
}Options:
Flag | Meaning |
| Tool categories or tool names to enable. Replaces the default set. |
| Expose these Actors as their own tools. |
| MCP Apps widget mode (widgets are disabled in this release, see below). |
| Opt in to usage telemetry (also needs a write key, see below). |
| Which telemetry write key variable to use. |
Tools
Default categories: actors, docs, runs, storage, tasks. The dev category (report-problem) is off by
default.
Category | Tools |
actors |
|
docs |
|
runs |
|
storage |
|
tasks |
|
dev |
|
Whenever call-actor, get-actor-run or an Actor tool is enabled, get-actor-run, get-actor-output,
get-dataset-items, get-key-value-store-record and abort-actor-run are added as well.
call-actor waits up to waitSecs (0 to 45, default 30) and returns the run status and storage IDs; the agent then
fetches the results with get-actor-output (pass the runId, or a datasetId). It returns a page of dataset items
(offset, limit up to 1000, default 100, and fields with dot notation) plus the run's OUTPUT record. Long text
values are cut and a page may hold fewer items than limit so the reply stays small; hasMore and nextOffset say
where to continue. get-dataset-items remains available for finer control. Clients that support protocol tasks can run call-actor as a long-running task
and collect the result when the run ends. Progress notifications are sent while a run is awaited, and cancelling the
request aborts the run.
Any Scrape.ly API GET endpoint can also be read with resources/read using its full URL, for example
https://api.scrape.ly/v2/datasets/<id>/items?limit=20.
Hosted server
scrapely-mcp-http --host 0.0.0.0 --port 8000Path | Purpose |
| MCP endpoint (streamable HTTP; 2026-07-28 stateless requests are also served) |
| OAuth protected-resource metadata (also under |
| Health check, |
URL parameters on the MCP endpoint: tools, actors, maxActorMemoryBytes, ui, payment (skyfire or
x402), telemetry-enabled, token.
Each session gets its own server instance bound to the SHA-256 fingerprint of the credential that opened it; a
request with a different credential is answered as if the session did not exist. SCRAPELY_TOKEN is never used by
the HTTP server.
A container image definition is in Dockerfile (docker build --build-arg SOURCE=local -t scrapely-mcp .).
Configuration
Variable | Default | Purpose |
| none | Token for the stdio server |
|
| API origin used for outbound calls |
| derived | API origin shown to clients and used as OAuth issuer |
|
| Base of Store links |
| API origin | Base for MCP-server Actors |
|
| HTTP bind address |
| none | Default tool selection of the HTTP server |
|
| Widget mode |
|
| Idle session timeout |
|
| Session limit |
|
| Clients that do not see |
|
| Usernames shown as official |
| empty | Scrape.ly docs search index |
| public Crawlee DocSearch values | Crawlee docs search |
| disabled | Personalised dashboard links |
| off | MCP Apps widgets (experimental) |
|
| Also send the legacy payment-protocol header |
| none | Shown in Skyfire payment hints |
| off | Opt-in telemetry |
| none | Error reporting (install the |
|
| Log level (logs go to stderr) |
Telemetry is off unless it is enabled and a write key is configured; the package ships no keys. Logs never contain tokens, payment tokens or payment signatures.
Widgets
MCP Apps widget tools (search-actors-widget, fetch-actor-details-widget, call-actor-widget,
get-actor-run-widget) are implemented but disabled by default, and no widget HTML is bundled. With widgets
disabled every client gets the plain tool set.
Development
uv venv && uv pip install -e ".[test]"
pytestLicense
MIT, see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Scrape, crawl and search the web for AI agents via MCP.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Web scraping, extraction and search for AI agents. Hosted MCP with workspace API keys.
Web search, browser automation, scraping, crawling and CAPTCHA solving for AI agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with the Apify platform to manage actors, monitor runs, and retrieve scraped data from datasets. It supports natural language commands for executing web scrapers, managing tasks, and accessing key-value stores.28MIT
- AlicenseNot gradedqualityNot gradedmaintenanceExposes over 19,000 Apify Actors as MCP tools for web scraping, data extraction, and OSINT automation. It enables AI agents to dynamically discover and execute scrapers to collect structured data and crawl web content.MIT
- AlicenseNot gradedqualityDmaintenanceEnables web scraping, browser automation, and dataset management through Apify's actor platform.MIT
- FlicenseNot gradedqualityBmaintenanceEnables querying the Apify Store to retrieve structured data on public Actors including pricing, usage trends, ratings, and categories. Integrates with AI agents for market research and competitor tracking.-