topmcps
Browse MCPs
Apify

Apify

Official

Run pre-built browser-automation Actors on managed infrastructure.

Score 90(?)ApifyApache-2.01.3kVerified Top MCPs for Browser Automation →
InstallView on GitHub

Quick answer

What it does

Connects to the Apify platform, lists available Actors, runs them with parameters, and returns structured output. Also exposes datasets, key-value stores, and run history.

Best for

  • Web scraping with pre-built Actors
  • Google Maps / Search / Shopping extraction
  • Social media scraping (TikTok, Instagram, X)
  • E-commerce product extraction

Not for

  • Custom one-off flows with no Actor
  • Sites with hard anti-bot blocks

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server"
      ],
      "env": {
        "APIFY_TOKEN": "${APIFY_TOKEN}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export APIFY_TOKEN=your-apify-api-token
claude mcp add apify -- npx -y @apify/actors-mcp-server

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server"
      ],
      "env": {
        "APIFY_TOKEN": "${APIFY_TOKEN}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server"
      ],
      "env": {
        "APIFY_TOKEN": "${APIFY_TOKEN}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server"
      ],
      "env": {
        "APIFY_TOKEN": "${APIFY_TOKEN}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server"
      ],
      "env": {
        "APIFY_TOKEN": "${APIFY_TOKEN}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@apify/actors-mcp-server"
          ],
          "env": {
            "APIFY_TOKEN": "${APIFY_TOKEN}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.apify]
command = "npx"
args = [
  "-y",
  "@apify/actors-mcp-server",
]
env = { APIFY_TOKEN = "${APIFY_TOKEN}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "apify": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@apify/actors-mcp-server"
        ]
      },
      "env": {
        "APIFY_TOKEN": "${APIFY_TOKEN}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Apify doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set APIFY_TOKEN in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Network
Sandbox
Apify API token in env. Actors execute on Apify infrastructure — your code does not run locally. Tokens are scoped per organisation; scope tightly for shared use.
Gotchas
  • Per-Actor billing means a runaway agent loop can run up bills quickly. Set per-run timeouts.
  • Public Actors are maintained by third parties — quality varies. Pin to known-good Actors for production.
  • Scraping is a legal grey zone; some Actors target sites whose terms forbid automation.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. browser automation work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-browser-automation
Compare Apify against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Apify MCP vs [Browserbase MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/apify
- top-mcps.com listing for Browserbase
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Apify MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/apify (fetch https://top-mcps.com/mcp/apify.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (APIFY_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Browser Automation MCPs

Other tools in the same category worth evaluating.

Puppeteer

Full browser automation: navigate, click, screenshot, and scrape.

browser, automation, scraping, puppeteer
5 minMedium
Playwright
Official

Official Microsoft browser automation across Chromium, Firefox, and WebKit.

browser, automation, playwright, testing
5 minMedium
Browserbase
Official

Hosted, isolated Chromium runtime for AI agents that need a fresh browser per task.

browser, cloud, browserbase, automation
5 minMedium

Compared with Apify

Side-by-side breakdowns for the choices people most often weigh against this MCP.

ApifyvsBrowserbaseApifyvsPuppeteerApifyvsPlaywrightApifyvsHyperbrowser

Exploring Top MCPs for Browser Automation? See all Browser Automation MCPs →