Apify MCP Server for Cursor: Setup & Config

What you can do with Apify in Cursor

Choose it when assistants need discoverable web-extraction tools backed by Apify Actors.

• Retrieve completed run results from datasets or key-value storage.
• Search the web and extract page content with the RAG Web Browser Actor.

Before you start: Apify in Cursor

• Node.js and npx for the local launch
• An MCP-compatible client
• Apify API token for the documented local configuration

The command is the local stdio route. The recommended hosted alternative uses streamable HTTP at remote_url and supports OAuth. Do not append /sse; the old SSE endpoint was removed. Hosted output-schema inference is not available in local stdio mode.

Apify Cursor configuration

1. Choose Cursor configuration scope

   For Apify MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Apify MCP Server to Cursor

   Use the actors-mcp-server entry below in mcpServers. Keep Apify MCP Server's documented stdio connection fields and your other Cursor entries.

3. Check Apify MCP Server in Cursor

   Apify MCP Server: Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "actors-mcp-server": {
      "command": "npx",
      "args": [
        "@apify/actors-mcp-server"
      ],
      "env": {
        "APIFY_TOKEN": "<Apify API token for local access>"
      }
    }
  }
}

Apify tools available to Cursor

Apify's stored tool list documents 19 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

search-actors

Find search-actors under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Find relevant Actors in Apify Store.

fetch-actor-details

Find fetch-actor-details under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

call-actor

Find call-actor under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get-actor-run

Find get-actor-run under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get-dataset-items

Find get-dataset-items under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get-key-value-store-record

Find get-key-value-store-record under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

abort-actor-run

Find abort-actor-run under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

search-apify-docs

Find search-apify-docs under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

fetch-apify-docs

Find fetch-apify-docs under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

apify--rag-web-browser

Find apify--rag-web-browser under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get-actor-run-list

Find get-actor-run-list under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

List an Actor's executions with optional status filtering.

get-actor-log

Find get-actor-log under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Read logs from a particular Actor execution.

get-dataset

Find get-dataset under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Inspect metadata for a dataset.

get-dataset-schema

Find get-dataset-schema under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Infer a JSON schema from dataset records.

get-key-value-store

Find get-key-value-store under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Inspect metadata for a key-value store.

get-key-value-store-keys

Find get-key-value-store-keys under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Enumerate keys in a selected store.

get-dataset-list

Find get-dataset-list under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

List datasets available to the user.

get-key-value-store-list

Find get-key-value-store-list under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

List the user's available key-value stores.

add-actor

Find add-actor under Apify in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Experimentally register an Actor as another callable tool.

Apify: full stored tool descriptions

Troubleshooting Apify in Cursor

• Cursor must find npx @apify/actors-mcp-server (Node.js/npm) for Apify MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
• Review APIFY_TOKEN for Apify MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
• Apify MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Local stdio lacks some hosted features.
• Known limitation: Client support for dynamic tool discovery varies.
• Known limitation: Paid Actor execution needs an account token or a supported funded payment flow.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions