Apify

- Dynamically discover and use any Apify Actor as an MCP tool.
- Pre-configured with apify/rag-web-browser and helper tools.
- Supports OAuth for easy client integration.
- Agentic payments with x402 (USDC on Base) and Skyfire (PAY tokens).
- Streamable HTTP transport; compatible with Claude Desktop, Claude.ai, VS Code, Cursor, and others.
- Loads each Actor’s input schema to create corresponding MCP tools.

The MCP server provides a set of tools for interacting with Apify Actors.
Since Apify Store is large and growing rapidly, the MCP server provides a way to dynamically discover and use new Actors.

One of the most powerful features of using MCP with Apify is dynamic tool discovery.
It allows an AI agent to find new tools (Actors) as needed and incorporate them.
Here are some special MCP operations and how the Apify MCP Server supports them:

- Apify Actors: Search for Actors, view their details, and use them as tools for the AI.
- Apify documentation: Search the Apify documentation and fetch specific documents to provide context to the AI.
- Actor runs: Get lists of your Actor runs, inspect their details, and retrieve logs.
- Apify storage: Access data from your datasets and key-value stores.
- Actor tasks: Create, inspect, and update your saved Actor tasks, and publish or unpublish their public landing pages.

Here is an overview list of all the tools provided by the Apify MCP Server.

Legend for the Enabled by default column:
- ✅ — in the default tool set.
- ⚡ — auto-injected when call-actor, an Actor tool, or get-actor-run is present (which is true in the default configuration).
- ✅¹ — served by default, but only when telemetry is enabled and the client is not withheld: Anthropic surfaces (Claude.ai / Claude Desktop / Claude Code) or local-agent-mode-apify. To disable, pass an explicit tools= list that omits it.

| Tool name | Category | Description | Enabled by default |
| :--- | :--- | :--- | :---: |
| search-actors | actors | Search for Actors in Apify Store. | ✅ |
| fetch-actor-details | actors | Retrieve detailed information about a specific Actor, including its input schema, README (summary when available, full otherwise), pricing, and Actor output schema. | ✅ |
| call-actor | actors | Call an Actor and get its run results. Use fetch-actor-details first to get the Actor's input schema. | ✅ |
| get-actor-run | runs | Get detailed information about a specific Actor run. | ⚡ |
| get-dataset-items | storage | Retrieve items from a dataset with support for filtering and pagination. | ⚡ |
| get-key-value-store-record| storage | Get the value associated with a specific key in a key-value store. | ⚡ |
| abort-actor-run | runs | Abort a running Actor run, optionally gracefully. | ⚡ |
| search-apify-docs | docs | Search the Apify documentation for relevant pages. | ✅ |
| fetch-apify-docs | docs | Fetch the full content of an Apify documentation page by its URL. | ✅ |
| apify--rag-web-browser | Actor (see tool configuration) | An Actor tool to browse the web. | ✅ |
| report-problem | dev | Report a problem with an Apify tool or Actor to the Apify team. | ✅¹ |
| get-actor-run-list | runs | Get a list of an Actor's runs, filterable by status. | |
| get-actor-log | runs | Retrieve the logs for a specific Actor run. | |
| get-dataset | storage | Get metadata about a specific dataset. | |
| get-dataset-schema | storage | Generate a JSON schema from dataset items. | |
| get-key-value-store | storage | Get metadata about a specific key-value store. | |
| get-key-value-store-keys| storage | List the keys within a specific key-value store. | |
| get-dataset-list | storage | List all available datasets for the user. | |
| get-key-value-store-list| storage | List all available key-value stores for the user. | |
| create-actor-task | tasks | Create a saved Actor task (a named, reusable Actor configuration). | |
| get-actor-task | tasks | Get a saved Actor task, its publication state and public display configuration. | |
| update-actor-task | tasks | Update a task's input, run options, or public display configuration. | |
| publish-actor-task | tasks | Publish a task on its public landing page. | |
| unpublish-actor-task | tasks | Unpublish a task from its public landing page. | |

> Note:
>
> When call-actor, an Actor tool, or get-actor-run is present, the server auto-injects get-actor-run, get-dataset-items, get-key-value-store-record, and abort-actor-run.
>
> When you call an Actor — through call-actor or directly via an Actor tool (e.g., apify--rag-web-browser) — the response contains run metadata, storage IDs, and a summary + nextStep, but no dataset items. To fetch items, follow nextStep and call get-dataset-items (auto-injected), passing the datasetId returned from the call.

All tools include metadata annotations to help MCP clients and LLMs understand tool behavior:

- title: Short display name for the tool (e.g., "Search Actors", "Call Actor", "apify/rag-web-browser")
- readOnlyHint: true for tools that only read data without modifying state (e.g., get-dataset, fetch-actor-details)
- openWorldHint: true for tools that access external resources outside the Apify platform (e.g., call-actor executes external Actors). Tools that interact only with the Apify platform (like search-actors or fetch-apify-docs) do not have this hint.

The tools configuration parameter is used to specify loaded tools – either categories or specific tools directly, and Apify Actors. For example, tools=storage,runs loads two categories; tools=call-actor loads just one tool.

When no query parameters are provided, the MCP server loads the following tools by default:

- actors
- docs
- apify/rag-web-browser

If the tools parameter is specified, only the listed tools or categories will be enabled – no default tools will be included.

report-problem is served by default (subject to the gating in the footnote above) but lives in the dev category, so an explicit tools=dev selects it too. To disable it, pass an explicit tools= list that omits it (e.g. tools=actors,docs).

> Easy configuration:
>
> Use the UI configurator to configure your server, then copy the configuration to your client.

Configuring the hosted server:

The hosted server can be configured using query parameters in the URL. For example, to load the default tools, use:

```