actors-mcp-server
OfficialThis server lets AI agents discover, inspect, run, and monitor Apify Actors, read their results, access Actor MCP tools, call Server Actor APIs, search Apify/Crawlee docs, and report problems.
Search Apify Store Actors by keywords and paginate results.
Fetch Actor details including input/output schemas, README, pricing, stats, metadata, and Server Actor HTTP operations.
Run any Actor with JSON input, optional wait time, memory, timeout, build, and cost caps.
Check Actor run details and abort running runs.
Read dataset items and key-value store records produced by runs.
List and call tools exposed by Actors that are MCP servers.
Send direct HTTP requests to documented Server Actor APIs.
Search and fetch Apify and Crawlee documentation.
Report problems with Apify MCP tools or Actors.
Integrates with Facebook through the Facebook Posts Scraper Actor to extract data from Facebook posts from multiple pages/profiles.
Integrates with Google Search through the Google Search Results Scraper to scrape Google Search Engine Results Pages (SERPs).
Integrates with Google Maps through the Google Maps Email Extractor Actor to extract contact details from Google Maps listings.
Integrates with Instagram through the Instagram Scraper Actor to scrape Instagram posts, profiles, places, photos, and comments.
Click 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., "@actors-mcp-server scrape recent posts from Elon Musk's Twitter profile"
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.
Apify MCP server
Connect your agent to the largest marketplace of tools for AI.
The official Apify Model Context Protocol (MCP) server gives AI agents web scraping, data extraction, and browser automation through thousands of ready-made Actors from Apify Store, at https://mcp.apify.com.
Apify is the marketplace of ready-to-run tools for AI agents. One connection to the Apify MCP server gives your agent thousands of tools to choose from, for jobs like web fetch, SERP monitoring, lead generation and enrichment, and pulling data from e-commerce sites and social media. The server loads only what each task needs.
Your agent searches Apify Store, checks an Actor's input and pricing, runs it, and reads the structured results, so you don't install a separate MCP server for every site. Connect to the hosted server with OAuth, or run it locally over stdio with the @apify/actors-mcp-server npm package.
Contents
Related MCP server: Apify MCP Server
๐ Quickstart
Open the MCP configurator, pick your client, and choose the tools you want.
Copy the generated configuration, deeplink, or command into your client.
Sign in to Apify in the browser window that opens. If you don't have an account, you can create a free one there.
The hosted endpoint is https://mcp.apify.com. If your client can't use OAuth, send your Apify API token in an Authorization: Bearer <APIFY_TOKEN> header instead. Treat the token like a password and keep it out of repositories. Create a token in Apify Console and copy it right after creating it. It is shown only once.
Using a coding agent such as Claude Code, Codex, Cursor, or GitHub Copilot? An official Apify plugin installs this MCP server together with Apify agent skills in one step.
๐ค Set up your client
The configurator generates the exact setup for each supported client, including Claude Code, ChatGPT, Cursor, VS Code, GitHub Copilot CLI, Claude, Claude Desktop, Codex, OpenCode, Kiro, and more. The snippets below cover the most common cases.

claude mcp add apify "https://mcp.apify.com" -t httpClaude Code opens the Apify sign-in page the first time it uses the server. To install the Apify plugin with Apify agent skills instead, run /plugin marketplace add apify/apify-claude-code-plugin, then /plugin install apify@apify and /reload-plugins.
Open ChatGPT Plugins, select +, then Add custom MCP server.
Name it
Apify, enterhttps://mcp.apify.comas the server URL, and choose OAuth authentication.Review the risk warning, select I understand and want to continue, then Create as a plugin.
Sign in with Apify, review the tools, and install the plugin. No API token is needed.
Start a new conversation, type
@, and select Apify.
In Business, Enterprise, and Edu workspaces, an admin or owner may need to create or publish the plugin. If the option is missing, ask your workspace admin. When the server's tools change, open the plugin and select Refresh.
The ChatGPT desktop app uses local MCP configuration shared with Codex instead: go to Settings > MCP servers > Add server, choose Streamable HTTP, and enter https://mcp.apify.com. See OpenAI's custom MCP server guide.
Use the one-click install link from the configurator, or let the Apify CLI write the configuration, including your API token:
apify mcp install cursorThe same command works for claude-code, vscode, codex, kiro, and antigravity.
Use the one-click install link from the configurator, run apify mcp install vscode, or add https://mcp.apify.com as an HTTP server in your MCP configuration:
{
"servers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com"
}
}
}Apify is available as a Claude connector. Open Settings > Connectors, find Apify in the connector directory, and connect it. You can also select Add custom connector, name it Apify, and enter https://mcp.apify.com as the remote MCP server URL. Sign in with Apify when prompted. The same connector works on Claude.ai and in Claude Desktop. See the Claude guide.
Most clients that support remote servers and OAuth accept a configuration like this:
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com"
}
}
}Requires Node.js 22 or later.
{
"mcpServers": {
"actors-mcp-server": {
"command": "npx",
"args": ["-y", "@apify/actors-mcp-server"],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
}Create an API token in Apify Console and copy it right after creating it. It is shown only once.
If you've run apify login, the server can also read the token saved by the Apify CLI. Run npx @apify/actors-mcp-server --help for all options.
The server is also listed in the Docker MCP catalog, and each release ships an MCP bundle file (apify-mcp-server.mcpb) for one-click installation in clients that support it.
Remote (hosted) or local MCP server
The hosted remote MCP server with OAuth is the recommended option. Use the local server when you want to run the MCP process on your own machine; Actors still run and store their results on the Apify platform in both modes. If your client supports only stdio, you can also bridge it to the hosted server with mcp-remote: npx mcp-remote https://mcp.apify.com.
Hosted ( | Local ( | |
Transport | Streamable HTTP | stdio |
Authentication | OAuth or Bearer token |
|
Output schemas inferred for Actor results | Yes | No |
Tool selection |
|
|
Updates | Always the latest server | The npm version you install |
How an agent uses Apify Actors
Actors are serverless programs on the Apify platform. Each one does a specific job, like scraping Google Maps, crawling a website for RAG, or collecting social media posts. The MCP server turns Actors into tools an agent can find and call without you configuring each one in advance.
A typical task follows four steps:
search-actorsfinds candidate Actors in Apify Store for the task.fetch-actor-detailsreturns the Actor's input schema, README, and pricing, plus its output schema on request.call-actorstarts the run and waits for it to finish, 30 seconds by default and up to 45. It returns the run status and storage IDs; the scraped items stay in the run's dataset.get-dataset-itemsreads the results from the run's dataset, withlimitandoffsetfor pagination.
The server adds get-dataset-items, get-key-value-store-record, get-actor-run, and abort-actor-run whenever call-actor or an Actor tool is loaded, so the agent can always read results and check on long runs that outlast the wait.
You can also expose a specific Actor as its own tool, for example apify/instagram-scraper. The server builds the tool's parameters from the Actor's input schema, so the agent knows exactly what to pass. A Server Actor with an API schema, such as apify/web-fetch, apify/web-search, or apify/rag-web-browser, gets a tool that sends one HTTP request to its API instead.
Actors that run their own MCP server. Some Actors are MCP servers themselves. fetch-actor-mcp-tool-list lists their tools, and call-actor-mcp-tool calls one. When such an Actor is loaded as a tool source and has no API schema, its tools are exposed under names in the form username--actor-name--tool-name; an Actor with an API schema, such as apify/web-search, gets its server tool instead, and call-actor-mcp-tool reaches its MCP tools. Apify Store also lists MCP-related Actors from independent creators; those are separate products with their own READMEs and pricing.
๐ ๏ธ Tools, resources, and prompts
Any Actor can be a tool, and agents discover new ones as they work. By default, the server loads the actors and docs categories, two Actor tools (Web Search and Web Fetch), and report-problem. Everything else is opt-in by category or by tool name.
Helper tools
Besides Actor tools, the server provides helper tools for the Apify platform:
Actors: search Apify Store, list the Actors in your account, view their details, call tools on Actors that run MCP servers, send requests to Server Actors, and delete your own Actors.
Documentation: search the Apify and Crawlee docs and fetch pages as context.
Runs and storage: list runs, inspect them, read their logs, and read datasets and key-value stores.
Tasks and schedules: manage saved Actor tasks and their public landing pages, and schedules that run Actors and tasks automatically.
Builds and versions: build Actors, read build logs, and create, read, change, copy, and delete versions from files.
Apify API: search the API reference, inspect an operation, and send requests to read or change data.
Available tools
Legend for the Enabled by default column:
โ In the default tool set.
โก Added automatically when
call-actor, an Actor tool, orget-actor-runis loaded, which is true in the default configuration.โ ยน Served by default only when telemetry is on and the client name doesn't contain
claude,anthropic, orlocal-agent-mode. Select it explicitly withtools=report-problemortools=devto serve it to any client; telemetry still has to be on.
Tool name | Category | Description | Enabled by default |
| actors | Search for Actors in Apify Store. | โ |
| actors | Get an Actor's input schema, README (summary when available, full otherwise), pricing, and a Server Actor's HTTP operations. The output schema is opt-in. | โ |
| actors | Run an Actor and return its run status and storage IDs. Use | โ |
| actors | List the tools of an Actor that runs an MCP server, with their schemas, annotations, and metadata. | โ |
| actors | Call one tool on an Actor's MCP server and return its result. | โ |
| actors | Send one HTTP request to a Server Actor's API, as documented by its API schema, and return the response. | โ |
| runs | Get details about an Actor run. | โก |
| storage | Read items from a dataset, with filtering and pagination. | โก |
| storage | Get the value stored under a key in a key-value store. | โก |
| runs | Abort a running Actor run, optionally gracefully. | โก |
| docs | Search the Apify and Crawlee documentation for relevant pages. | โ |
| docs | Fetch the full content of a documentation page by its URL. | โ |
Actor (see Choose which tools load) | Search the web and return one page of results: titles, URLs, and snippets. | โ | |
Actor (see Choose which tools load) | Fetch a URL and return its content as Markdown, text, HTML, or other formats. | โ | |
| dev | Report a problem with an Apify tool or Actor to the Apify team. | โ ยน |
Actor (see Choose which tools load) | Search the web and return the content of the top results. | ||
| none (select by name: | List the Actors you own and those shared with you, including private ones. | |
| none (select by name: | Delete an Actor from your account permanently. Public Actors must be unpublished first. | |
| runs | List Actor runs, filtered by Actor and status. | |
| runs | Read the log of an Actor run. | |
| storage | Get metadata about a dataset. | |
| storage | Generate a JSON schema from dataset items. | |
| storage | List the datasets in your account. | |
| storage | Get metadata about a key-value store. | |
| storage | List the keys in a key-value store. | |
| storage | List the key-value stores in your account. | |
| tasks | Create a saved Actor task (a named, reusable Actor configuration). | |
| tasks | Get a saved Actor task, its publication state, and its public display configuration. | |
| tasks | Update a task's input, run options, or public display configuration. | |
| tasks | Publish a task on its public landing page. | |
| tasks | Unpublish a task from its public landing page. | |
| schedules | Create a schedule that runs Actors or tasks on a cron expression. | |
| schedules | Get a schedule, its cron expression, state, and the actions it runs. | |
| schedules | Update a schedule's cron expression, time zone, enabled state, or actions. | |
| schedules | Delete a schedule. | |
| builds | Build an Actor version and wait a bounded time for the build to finish. | |
| builds | Get the status of an Actor build. | |
| builds | List the account's builds, or one Actor's, in every status, newest first. | |
| builds | Read the log of an Actor build. | |
| versions | Get an Actor version's file listing with hashes, plus the content of the files you ask for. | |
| versions | Create a private Actor in your account from files, optionally starting a build. | |
| versions | Write, edit, or delete files of an Actor version in one all-or-nothing write. | |
| versions | Add a version to an Actor, from files or as a copy of another version, optionally starting a build. | |
| versions | Delete an Actor version. Its builds and their tags stay. | |
| api | Search the Apify API reference by keywords. Returns each operation's method, path, and docs page. | |
| api | Get the parameters and request body schema of the Apify API operations on a path. | |
| api | Send a GET request to an Apify API path, like | |
| api | Send a POST, PUT, PATCH, or DELETE request with a JSON body to any Apify API path, like |
The tasks category manages saved Actor tasks. It is unrelated to the MCP Tasks protocol. The tool reference has full descriptions of each tool.
Tool annotations
Every tool carries a title, a readOnlyHint, and an openWorldHint. readOnlyHint is true for tools that only read data. Actor tools get it only for Apify-maintained Actors with limited permissions and no inputs that accept secrets, writable storage, an MCP connector, or code; other Actor tools are marked destructive. openWorldHint is true for tools that reach outside the Apify platform, such as call-actor, and false for platform-only tools.
Prompts and resources
No prompts are registered yet, so prompts/list returns an empty list. resources/read accepts any Apify API GET URL (https://api.apify.com/v2/...) and returns the response body using the session's Apify token, inlined up to 256 KB. Your data isn't enumerated in resources/list; resources/templates/list lists the common shapes with their paging parameters.
Choose which tools load
The tools parameter takes categories, tool names, and Actor names, separated by commas. When you set it, the defaults are dropped and only what you list is loaded, plus the โก run and storage tools whenever the list includes call-actor or an Actor. The easiest way to build a selection is the configurator.
Hosted server:
https://mcp.apify.com?tools=actors,docs,apify/web-search,apify/web-fetchLocal server:
npx @apify/actors-mcp-server --tools actors,docs,apify/web-search,apify/web-fetchTo give an agent a single Actor, list only that Actor. The agent gets its tool plus the four โก tools it needs to read the results:
https://mcp.apify.com?tools=apify/instagram-scraperPin your tools in production. The default tool set can change between versions. Set
toolsexplicitly if you need a stable interface.
apify/web-searchreplacedapify/rag-web-browserin the default tools. To keepapify--rag-web-browser, addapify/rag-web-browserto yourtoolslist, or settools=actors,docs,apify/rag-web-browser,apify/web-fetchfor the previous default categories and Actors.The
actorsURL parameter and--actorsflag still work. They're merged intotools, so?actors=apify/web-fetchequals?tools=apify/web-fetch.enableAddingActors,enable-adding-actors, andenableActorAutoLoadingwere removed and are ignored. Dynamic Actor calls come fromcall-actor, which the defaultactorscategory includes.The selectors
add-actor,experimental, andprevieware retired and load nothing. Usecall-actoror theactorscategory.get-actor-logwas renamed toget-actor-run-log, and thesourcecategory toversions. The old names load nothing.call-actorno longer calls tools on MCP server Actors: theactorName:toolNameform is rejected. Usecall-actor-mcp-toolwithactor,tool, andarguments.call-actorstill starts a run of an MCP server Actor that has an input schema; one without is refused. A selection that namescall-actoralone needscall-actor-mcp-tooladded.fetch-actor-detailsno longer lists an MCP server Actor's tools, andoutput.mcpToolsis ignored. Usefetch-actor-mcp-tool-list, which returns the definitions instructuredContent.tools. A selection that namesfetch-actor-detailsalone needsfetch-actor-mcp-tool-listadded.A selected Actor with an API schema (a Server Actor) gets a tool that sends one HTTP request to its API, with
method,path, andqueryarguments, instead of a tool that starts a run. If the Actor is also an MCP server, the selection no longer loads its MCP tools: usecall-actor-mcp-tool.call-actorstill starts runs of the Actor when it has an input schema. A selectedapify/rag-web-browseris served this way too, withGET /search.apify--web-fetchsends one HTTP request to the Web Fetch Actor's API instead of starting a run, and returns the HTTP response. Its arguments aremethod,path,queryand, forPOST /,body, for example{"method": "GET", "path": "/", "query": {"url": "https://example.com", "formats": ["markdown", "links"]}}.apify--web-searchsends one HTTP request to the Web Search Actor's API instead of starting a run, and returns the HTTP response. Its arguments aremethod,path,queryand, forPOST /,body, for example{"method": "GET", "path": "/", "query": {"query": "AI agent payment protocols", "maxResults": 5}}.call-actorstill starts runs of the Actor, andcall-actor-mcp-toolcalls itssearchMCP tool.
UI mode configuration
The ui parameter controls MCP Apps widget tools. With UI mode on, the server adds search-actors-widget and fetch-actor-details-widget next to their base tools, which keep returning standard responses. By default (auto), UI mode turns on when the client supports MCP Apps.
Value | Behavior |
| Widget tools added when the client supports MCP Apps |
| Widget tools always added |
| No widget tools |
Hosted server:
https://mcp.apify.com?tools=actors,docs&ui=trueLocal server, with a CLI flag or the UI_MODE environment variable:
npx @apify/actors-mcp-server --ui true
UI_MODE=true npx @apify/actors-mcp-server๐ฌ Example prompts
Ask in plain language. The agent finds a suitable Actor, checks its input and pricing, runs it, and reads the results. These prompts cover the most common jobs:
Use case | Example prompt | Example Actor |
Web research | "Find what people on X said about autonomous AI agents this week and summarize the key developments." | |
Search and read the web | "Compare the current pricing plans of Notion, Coda, and Airtable and tell me which is cheapest for a 10-person team." | |
Search results (SERP) | "Get the top 20 Google results for 'best CRM for startups' in the US and show who ranks where." | |
Lead generation | "Find dentists in Austin, Texas on Google Maps with their phone numbers, websites, and ratings." | |
LinkedIn profiles | "Get the current job title, company, and work history for these 20 LinkedIn profiles." | |
LinkedIn company posts | "Get the 30 latest posts from Apify's LinkedIn company page with their reaction counts." | |
Review analysis | "Pull the latest 100 Google Maps reviews for this hotel and group the complaints by theme." | |
Social media monitoring | "Get the 50 latest posts from @nasa on Instagram with likes and comments." | |
Trend research | "Find the most viewed TikTok videos for #skincare this week." | |
E-commerce | "List the 10 best-rated wireless earbuds on Amazon with prices and review counts." | |
Knowledge base and RAG | "Crawl docs.example.com and turn every page into Markdown I can load into my vector database." |
Follow-ups work too. "Show me the next 10 results from that run" makes the agent call get-dataset-items again with a higher offset. With the schedules category loaded, "Run that Google Maps search every Monday at 9 am" creates a schedule.
๐ฐ Pricing and limits
Connecting to the MCP server is free. Actor runs bill to your Apify account according to each Actor's pricing, which
fetch-actor-detailsshows before a run. The Apify free plan includes $5 of monthly platform usage.To cap what a run can cost, pass
maxTotalChargeUsd(pay-per-event Actors) ormaxItems(pay-per-result Actors) in thecallOptionsofcall-actor.timeoutandmemorylimit the run's duration and memory, not its price.The hosted server accepts up to 20 requests per second per account.
search-actorsreturns only free and pay-per-event Actors that pass the platform's agent-safety filters, so rental and pay-per-result Actors don't appear in search. Full-permission Actors need your one-time approval; until then,call-actorreturns an error with an approval link.Some tools work without an Apify account:
search-actors,fetch-actor-details,search-apify-docs,fetch-apify-docs,apify-api-search, andapify-api-details. Select only those, for examplehttps://mcp.apify.com?tools=search-actors, and the hosted server accepts the connection without a token.
๐ช Agentic payments (experimental). Agents can pay for Actor runs without an Apify account. AGI sells a prepaid, spend-capped Apify API token for an x402, MPP, or Skyfire payment. The agent then uses it as a normal Bearer token against
mcp.apify.com, with any Actor that uses limited permissions. See the agentic payments documentation for supported methods and limits, and agi.apify.com/AGENTS.md for protocol details.
๐ก Telemetry
The Apify MCP server collects telemetry about tool calls to help Apify understand usage patterns and improve the service. Telemetry is on by default. With telemetry on, Actor searches in Apify Store send the first 12 hex characters of the SHA-256 hash of the MCP session ID as _traceId, and tool-call events carry it as trace_id. search-actors also sends _useCase, a one-sentence reason for the search written by the model, which Apify uses to improve Store search results. The stdio transport also uses Sentry for error tracking, which helps the Apify team find and fix issues faster.
To opt out, including Sentry, set the telemetry-enabled URL parameter or the --telemetry-enabled CLI flag to false, or set TELEMETRY_ENABLED=false. CLI flags take precedence over environment variables.
https://mcp.apify.com?telemetry-enabled=falsenpx @apify/actors-mcp-server --telemetry-enabled=false
TELEMETRY_ENABLED=false npx @apify/actors-mcp-server๐ Troubleshooting and limitations
The local server won't start. Check your Node.js version: the package requires Node.js 22 or later.
Authentication fails. Reconnect so the client repeats the OAuth flow, or switch to a Bearer token. For the local server, check that
APIFY_TOKENis set in the client's server configuration, not only in your shell.VS Code says the OAuth app is not registered. Run Authentication: Remove Dynamic Authentication Providers, select Apify, and sign in again.
Client features vary. Any MCP client can connect, but support for dynamic tool lists, OAuth, and MCP Apps differs between clients.
Invalid Actor input. When
call-actorfails because of invalid input, the error includes the Actor's input schema so the agent can correct the input and retry.
The server adapts Actor input schemas so that more clients and models can use them:
Descriptions longer than 500 characters are cut at the last complete sentence and marked
[Description truncated].Enums are kept in full up to 2,000 combined characters. Larger enums are replaced by a short note with example values.
Required fields get a
REQUIREDprefix in their descriptions for frameworks that ignore the JSON Schemarequiredlist.Nested properties are built for special inputs such as proxy configuration and request lists.
Missing array item types are inferred from the item type, the prefill, the default value, or the editor type, in that order.
Prefill and default values are copied into descriptions as examples, for clients that ignore JSON Schema
examples.
For more help, see the MCP documentation or open an issue.
โ FAQ
What is an MCP server? An MCP server exposes tools and data to AI agents through the Model Context Protocol, an open standard supported by clients such as Claude, ChatGPT, and Cursor. The agent connects once and calls the server's tools when a task needs them. The Apify MCP server's tools are the Actors in Apify Store.
What is the Apify MCP server? It's the official Model Context Protocol server for Apify. It lets AI agents search Apify Store, run Actors for web scraping, data extraction, and browser automation, and read the structured results.
When is it a good MCP server for web scraping? When an agent needs data from many different sites. A typical case is Google Maps one day, Instagram or an online store the next. The agent picks a ready-made Actor for each site from Apify Store instead of you writing and maintaining a scraper. Each Actor works like a web scraping API for its site, and the Apify platform handles scaling, proxies, and storage of the results.
How does it compare to Playwright MCP? Playwright MCP drives a browser on your machine step by step, through clicks and page snapshots. The Apify MCP server runs Actors in the Apify cloud. Each Actor handles JavaScript rendering, proxies, and blocking for its site and returns structured results, so the agent asks for the data instead of operating a browser. Many agents use both.
Can ChatGPT or Claude scrape websites with it?
Yes. Connect ChatGPT, Claude, or Claude Code to https://mcp.apify.com, then ask in plain language. The model searches for a suitable Actor, runs it, and reads the results.
Is it free? Connecting is free, and some discovery tools work without an account. Actor runs bill to your Apify account at each Actor's price, and the free plan includes $5 of monthly platform usage.
Do I need an API token?
Not with the hosted server, because OAuth signs you in through the browser. The local server needs APIFY_TOKEN or an Apify CLI login.
Can I limit what the agent can do or spend?
Yes. Select tools with the tools parameter or expose a single Actor. To cap a run's cost, pass maxTotalChargeUsd for pay-per-event Actors or maxItems for pay-per-result Actors in call-actor options.
๐ง Development
This repository contains the open-source server package published to npm as @apify/actors-mcp-server. The hosted service at mcp.apify.com runs on this core logic from a separate private repository.
You need Node.js 22 or later and pnpm.
pnpm install
pnpm run build
pnpm run dev # Streamable HTTP server on http://localhost:3001, hot reload for widgets
pnpm run inspector:stdio # MCP Inspector against the stdio serverThe development HTTP server doesn't read APIFY_TOKEN from the environment. Pass your token in an Authorization: Bearer header or a ?token= query parameter, for example from the MCP Inspector.
To publish a canary build of a pull request to pkg.pr.new, add the beta label to it.
DEVELOPMENT.md covers the project structure, tool loading phases, the Node.js version policy, and testing.
๐ค Contributing
Bug reports, feature requests, and documentation fixes are welcome. Open an issue with steps to reproduce a bug, or describe the problem a feature would solve and who runs into it. Send typos, broken links, and wrong commands straight to a pull request. For code, work only on an issue a maintainer has invited you to pick up; unsolicited pull requests are closed.
Read CONTRIBUTING.md before you start, including the rules for AI-assisted contributions.
๐ Privacy and license
Requests and Actor inputs go to the Apify API to run the Actors you call. Apify doesn't share them with third parties beyond what running those Actors requires. See Apify legal documents for details on data collection and retention.
The project is licensed under the MIT license.
๐ Learn more
MCP documentation: authentication, tool reference, and advanced configuration
Apify for AI agents: choosing between MCP, plugins, agent skills, the CLI, and machine-readable docs
Apify agent skills: guided multi-step workflows, installed with
npx skills add apify/agent-skillsApify CLI: running and building Actors from a terminal
Available Tools
13 toolsabort-actor-runAbort Actor runADestructiveIdempotentInspect
Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.
USAGE:
Use when you need to stop a run that is taking too long or misconfigured.
USAGE EXAMPLES:
user_input: Abort run y2h7sK3Wc
user_input: Gracefully abort run y2h7sK3Wc
Inputs: runId (required), gracefully. Returns: tip, runId, stats, status, +10 more
call-actorCall ActorADestructiveInspect
Call any Actor from the Apify Store.
WORKFLOW:
Use fetch-actor-details to get the Actor's input schema
Call this tool with the actor name and proper input based on the schema
If the actor name is not in "username/name" format, use search-actors to resolve the correct Actor first.
An MCP server Actor with no input schema is not run here; call-actor-mcp-tool calls its MCP tools.
For Server Actors (Actors with an HTTP API):
This tool starts a batch run and stores the results in a dataset; use it when you need batch results
For one or a few results, send-server-actor-request returns them in the HTTP response, without a batch run
fetch-actor-details with output={ serverInterface: true } lists its HTTP operations
IMPORTANT:
Waits up to waitSecs (default 30s) for completion; returns run status and storage IDs, and with waitSecs > 0 also reports dataset field metadata
Use get-dataset-items with the datasetId to fetch results; non-terminal runs include a nextStep with polling instructions
There are two ways to use an Actor:
Its dedicated tool, when the session has one: a Server Actor's tool sends one HTTP request to its API, an MCP server Actor's tools call its MCP server, and any other Actor's tool starts a run.
The generic call-actor tool: starts a run of any Actor and stores the results in a dataset.
USAGE:
Prefer the dedicated tool when the session has one for the Actor
call-actor runs an Actor that has no dedicated tool, and batch work whose results belong in a dataset.
Use
waitSecs(0โ45) to control how long to wait. Default 30s returns results for fast actors. UsewaitSecs: 0to start and return immediately for long-running actors.
EXAMPLES:
user_input: Get instagram posts using apify/instagram-scraper
Inputs: actor (required), input (required), waitSecs, callOptions. Returns: tip, runId, stats, status, +10 more
call-actor-mcp-toolCall Actor MCP toolADestructiveInspect
Call one tool on an Actor's MCP server and return its result. fetch-actor-mcp-tool-list lists the Actor's MCP tools and their input schemas. It connects with your Apify API token. Connecting can start a Server Actor run in your account, kept until its idle timeout; a multi-tenant Server Actor charges per event. What the tool itself does depends on the Actor.
Example call: {"actor": "username/name", "tool": "search", "arguments": {"query": "apify"}}
USAGE:
Use when the user asks to call a tool on an Actor's MCP server.
USAGE EXAMPLES:
user_input: Use the search tool of username/name to look up apify
Inputs: tool (required), actor (required), arguments.
fetch-actor-detailsFetch Actor detailsARead-onlyIdempotentInspect
Get detailed information about an Actor by its ID or full name (format: "username/name", e.g., "apify/rag-web-browser").
Requires the exact ID or full name โ do not construct a plausible-looking name and call this tool with it. If you only have a description, a partial name, or a name you have not seen in this conversation, find it with search-actors first.
Use 'output' to control returned information:
Default: all fields except outputSchema and serverInterface. Server Actors always get a one-line server interface summary unless serverInterface is true or a selector.
Selective: set only the fields you need to true, e.g. output: { inputSchema: true }
Common patterns: inputSchema only, description + readme, serverInterface: true (every operation in full when they fit, an index of them otherwise) or "GET /search" (one operation in full) for Server Actors
The 'readme' field returns the summary when available, full README otherwise. Use when querying Actor details, documentation, or input requirements. It does not connect to an MCP server Actor; fetch-actor-mcp-tool-list lists its MCP tools.
EXAMPLES:
What does apify/web-fetch do?
What is the input schema for apify/web-scraper?
What HTTP operations does this Server Actor expose?
Inputs: actor (required), output. Returns: readme, nextStep, actorInfo, inputSchema, +2 more
fetch-actor-mcp-tool-listFetch Actor MCP tool listAInspect
List an Actor's MCP tools with each tool's name, description, input schema, annotations, and metadata, as the server reports them. call-actor-mcp-tool calls one of them by name. Each call asks the server again; nothing is cached. It connects with your Apify API token. Connecting can start a Server Actor run in your account, kept until its idle timeout; a multi-tenant Server Actor charges per event.
USAGE:
Use when the user asks which MCP tools an Actor provides, or before calling one of them.
USAGE EXAMPLES:
user_input: What tools does username/name provide?
Inputs: actor (required). Returns: tools
fetch-apify-docsFetch Apify docsARead-onlyIdempotentInspect
Fetch the full content of an Apify or Crawlee documentation page by its URL. Use this after finding a relevant page with the search-apify-docs tool.
USAGE:
Use when you need the complete content of a specific docs page for detailed answers.
USAGE EXAMPLES:
user_input: Fetch https://docs.apify.com/platform/actors/running#builds
user_input: Fetch https://docs.apify.com/academy
user_input: Fetch https://crawlee.dev/docs/guides/basic-concepts
Inputs: url (required). Returns: url, content
get-actor-runGet Actor runARead-onlyIdempotentInspect
Get detailed information about a specific Actor run.
Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
waitSecs (0โ45, default 30) waits up to that many seconds for terminal status before returning.
USAGE:
Use to check the status of a run started by any Actor-running tool.
Pass waitSecs > 0 to block until terminal (or until the cap elapses).
USAGE EXAMPLES:
user_input: Show details of run y2h7sK3Wc
user_input: Wait for run y2h7sK3Wc to finish
Inputs: runId (required), waitSecs. Returns: tip, runId, stats, status, +10 more
get-dataset-itemsGet dataset itemsARead-onlyIdempotentInspect
Get items (rows) from a dataset โ the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.
USAGE:
Use when you need to read data from a dataset (all items or only selected fields).
USAGE EXAMPLES:
user_input: Retrieve results from dataset abc123
user_input: Get only metadata.url and title from dataset username~my-dataset
Inputs: datasetId (required), desc, omit, clean, +4 more. Returns: items, limit, offset, summary, +5 more
get-key-value-store-recordGet key-value store recordARead-onlyIdempotentInspect
Get the value stored under a specific key in a key-value store โ a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically. A record over 262144 bytes is returned as a link to download it, not as its value.
USAGE:
Use when you need to retrieve a specific record (JSON, text, or binary) from a store.
USAGE EXAMPLES:
user_input: Get record INPUT from store abc123
user_input: Get record data.json from store username~my-store
Inputs: recordKey (required), keyValueStoreId (required). Returns: key, value, summary, contentType, +1 more
report-problemReport a problemAInspect
Report a problem with Apify's MCP tools or Actors to the Apify team.
Reports can describe missing tools or Actors, errors, timeouts, confusing results, steps that took several attempts, or tasks that the available tools could not complete. Reports help fix the problem for other users.
Put what you were doing and what went wrong in "message". Do NOT include personal data, credentials, secrets, or verbatim private conversation content โ describe the issue in your own words.
Inputs: message (required), actorId, actorRunId, relatedTools. Returns: reported
search-actorsSearch ActorsARead-onlyIdempotentInspect
Search the Apify Store to FIND and DISCOVER what scraping tools/Actors exist for specific platforms or use cases. This tool provides INFORMATION about available Actors - it does NOT retrieve actual data or run any scraping tasks.
Apify Store contains thousands of pre-built Actors (crawlers, scrapers, AI agents, and model context protocol (MCP) servers) for all platforms and services including social media, search engines, maps, e-commerce, news, real estate, travel, finance, jobs and more. Apify Store lists Actors published by Apify and by independent developers.
Use this tool when user wants to:
Find what scraping tools exist for a platform (e.g., "What tools can scrape Instagram?")
Discover available Actors for a use case (e.g., "Find an Actor for Amazon products")
Browse existing solutions (e.g., "Show me scrapers for news sites")
Learn about MCP servers or AI agents available in the Store
This tool discovers Actors; it does not retrieve their output. IMPORTANT: When the user wants detailed data from a specific platform or is looking for scraping tools, prefer searching the Store first โ a relevant Actor often already exists. When the user names a specific Actor, look up that Actor directly instead of searching.
Usage:
Use 1-3 simple terms from the platform and/or data type the user named (e.g. "Instagram posts", "Twitter", "Amazon products"). With neither named, empty keywords return the Store's default ordering. A platform-only query is an option if more specific results do not fit.
Important limitations: This tool does not return full Actor documentation or detailed usage instructions - only summary information.
Each result lists the Actor's input fields with their types (e.g. url: string, maxResults?: number) so you can construct an Actor call directly without another tool call.
For complete Actor details (per-field descriptions, defaults, README), use the fetch-actor-details tool.
The search is limited to publicly available Actors and excludes rental and restricted Actors.
Returns list of Actor cards with the following info:
Title: Markdown header linked to the Store page, followed by the full Actor name in code format
URL: Direct Store link
Description: Actor description or fallback
Pricing: Details with pricing link
Stats: Total and monthly users
Rating: Out of 5 (if available)
Developed by: Username linked to profile, marked (Apify) or (community)
Categories: Formatted or "Uncategorized"
Last modified: Date (if available)
Input fields: Inline list of input field names and types (e.g.
url: string, maxResults?: number);?marks optional fields,... (+N more)marks a truncated list
Inputs: limit, offset, useCase, keywords. Returns: count, query, actors, userTier, +1 more
search-apify-docsSearch Apify docsARead-onlyIdempotentInspect
Search Apify and Crawlee documentation using full-text search. Do not also search the Apify Store unless the user asks to find Actors.
You must explicitly select which documentation source to search using the docSource parameter:
โข docSource="apify" - Apify: Apify Platform documentation including: Platform features, SDKs (JS, Python), CLI, REST API, Academy (web scraping fundamentals), Actor development and deployment
โข docSource="crawlee-js" - Crawlee (JavaScript): Crawlee is a web scraping library for JavaScript. It handles blocking, crawling, proxies, and browsers for you.
โข docSource="crawlee-py" - Crawlee (Python): Crawlee is a web scraping library for Python. It handles blocking, crawling, proxies, and browsers for you.
The results will include the URL of the documentation page (which may include an anchor), and a limited piece of content that matches the search query.
Fetch the full content of the document using the fetch-apify-docs tool by providing the URL.
When results contain both platform documentation (docs.apify.com/platform) and Academy content (docs.apify.com/academy) on the same topic, prefer the platform documentation.
Inputs: query (required), limit, offset, docSource. Returns: results, instructions
send-server-actor-requestSend Server Actor requestADestructiveInspect
Send one HTTP request to an Actor Server: the HTTP API of a Server Actor, documented in its API schema (OpenAPI) and README. fetch-actor-details with output.serverInterface returns the documented operations with their parameters. Give the method, the path, and optionally query parameters and a JSON body; the Actor Server's host and your Apify API token are added for you. Only an Actor with an Actor Server and an API schema takes requests here; the Actor accepts or rejects the method and path. A request to a single-tenant Actor Server can start a run of the Actor in your account, kept until its idle timeout; a multi-tenant Actor Server charges per event. The request is sent once, with no retries and without following redirects. A JSON, text, or XML response body is returned as text, cut at 262144 bytes; other content types are not returned.
Example call: {"actor": "apify/rag-web-browser", "method": "GET", "path": "/search", "query": {"query": "AI news", "maxResults": 3}}
USAGE:
Use when the Actor that fits the user's request has an Actor Server, and its API schema or README names the endpoint for the task.
Fits requests for one or a few results returned in the HTTP response. Larger batches depend on the endpoint and the response size and time limits.
USAGE EXAMPLES:
user_input: Search the web for the latest AI news and read the top pages with apify/rag-web-browser
user_input: Read https://docs.apify.com as Markdown with apify/rag-web-browser
Inputs: path (required), actor (required), method (required), body, +1 more. Returns: body, path, bytes, method, +13 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 13 tools
Most tools target clearly distinct actions (search, fetch details, run, abort, read dataset, docs search/fetch). The only murky cluster is call-actor vs call-actor-mcp-tool vs send-server-actor-request, which all 'invoke' something, but the descriptions clearly differentiate generic runs, MCP tool calls, and HTTP endpoint requests.
All 13 tools use consistent kebab-case verb-first naming: fetch-*, search-*, get-*, call-*, abort-*, send-*, report-*. No mixing of conventions or casing styles.
13 tools sits squarely in the well-scoped range for an Actor hub that must cover discovery, execution, storage retrieval, docs, and reporting. Each tool maps to a distinct step in the workflow.
The surface covers the full Actor lifecycle (discover, inspect, run, poll, abort) plus dataset and key-value access, docs, MCP tool invocation, server HTTP requests, and problem reporting. Minor gaps remain: no listing of a user's own runs/actors or dataset/key-value-store enumeration, though agents can work around these with known IDs.
Maintenance
Related MCP Connectors
No-code web scraping & data-extraction Apify actors: scrape and enrich web data at scale.
No-code web scraping & data-extraction Apify actors: scrape and enrich web data at scale.
Pay-per-use Apify tools for AI classification, SEO audits, leads, transcripts and web data.
64 public Apify Actors for public-record, jobs, lead, SEO and social data, as MCP tools.
Related MCP Servers
- 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
- AlicenseAqualityBmaintenance35 public-data MCP tools with optional focused profiles for business leads, market intelligence, government records, and research/health. Includes Maps, jobs, SEC filings, grants, sanctions and more. Runs use your own Apify account and are billed there. Structured results and deterministic errors.43MIT

honestkit-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to access fourteen web-data tools for scraping, SEO and site auditing, extraction, validation, enrichment, and screenshots through Apify actors. It runs those tools on the user's own Apify account via an API token.MIT