Apify MCP server

Endpoint: https://mcp.apify.com · Authentication: Sign in with OAuth

Searches Apify Store, runs Actors for web scraping and automation, and reads their datasets and documentation. Uses OAuth or an Apify API token as a bearer token; a few tools work without an account.

Test it live Run the release-readiness report

How do I authenticate?

Add the endpoint in your client, start Connect or Sign in, approve the requested scopes, and return to the client. OAuth discovery finds the authorization server; client registration requirements vary by provider. Follow the provider guidance and client setup below.

Authentication and connection guide

Connection specification

Remote endpoint: https://mcp.apify.com
Live-validated endpoint: https://mcp.apify.com/
Browser access: Not yet measured
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Streamable HTTP — Observed by the latest catalog validation
Declared authentication: OAuth 2.1
Detected authentication: OAuth 2.1 detected or retained from publisher evidence
Alternative authentication: Bearer token
Protocol lifecycle: Stateless MCP · 2026-07-28
Required header: Authorization — Optional Apify API token alternative: Bearer <APIFY_TOKEN>
Authorization server: https://console-backend.apify.com
Category: Automation

Product documentation · Source repository · Official listing documentation

Provider guidance

Initialization succeeded without credentials in the 2026-10-20 audit because Apify exposes a limited anonymous tool set; running Actors on an account requires OAuth or an API token.

More Automation MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

Registration requirements not verified

The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

Publisher evidence reviewed 2026-10-20.

Publisher documentation

Connect it

Live-validated endpoint: https://mcp.apify.com/ · Streamable HTTP. Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

Agent prompt for Claude Code or Codex

Add the Apify MCP server to my MCP client configuration and verify that it works.

What it is: Searches Apify Store, runs Actors for web scraping and automation, and reads their datasets and documentation. Uses OAuth or an Apify API token as a bearer token; a few tools work without an account.
Server URL: https://mcp.apify.com/
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: OAuth 2.1. Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/apify/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "apify" in that client's MCP configuration, user scope unless I ask otherwise.
   Claude Code: claude mcp add --transport http --scope user 'apify' 'https://mcp.apify.com/'
   Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

claude mcp add --transport http --scope user 'apify' 'https://mcp.apify.com/'

After adding the server, open Claude Code, run /mcp, select the server, and follow the browser flow to authenticate.

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'apify' --url 'https://mcp.apify.com/'
codex mcp login 'apify'

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/"
    }
  }
}

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com/"
    }
  }
}

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Notes for every client

Publisher evidence (reviewed 2026-10-20): https://docs.apify.com/platform/integrations/mcp
Optional bearer token alternative: Store APIFY_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <APIFY_TOKEN>.
Provider guidance: Initialization succeeded without credentials in the 2026-10-20 audit because Apify exposes a limited anonymous tool set; running Actors on an account requires OAuth or an API token.

Client compatibility

Client	Status	Why
Claude Code	Supported	Claude Code supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
Codex	Supported	Codex supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
Cursor	Supported	Cursor supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
VS Code	Supported	VS Code supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
Claude	Supported	Claude supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
Claude Desktop	Supported	Claude Desktop supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
ChatGPT	Supported	ChatGPT supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
Windsurf	Supported	Windsurf supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
Gemini CLI	Supported	Gemini CLI supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.
MCP SDK	Supported	MCP SDK supports Streamable HTTP servers and OAuth sign-in or bearer-token headers.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

Make — Runs Make scenarios as tools and manages scenarios, connections, and other Make resources. This endpoint uses OAuth; Make also documents zone-specific MCP-token URLs. OAuth 2.1
Zapier — Runs actions in the apps connected to a Zapier account through a configured Zapier MCP server. Supports OAuth or a Zapier MCP connection token as a bearer token. OAuth 2.1
Airbyte — Adds and removes Airbyte agent connectors and reads or writes data in connected SaaS sources. Requires Airbyte sign-in through OAuth, then per-connector authorization. OAuth 2.1
Browser Use — Runs Browser Use cloud browser-agent tasks, polls their status and output, and manages sessions and browser profiles. Requires a Browser Use API key as a bearer token. Bearer token
IFTTT — Create IFTTT Applets and run actions and queries across connected services. OAuth 2.1
Octoparse — Discover Octoparse templates, manage cloud scraping tasks and export structured data. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain Apify? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/apify.svg)](https://mcptest.io/servers/apify/)

HTML

<a href="https://mcptest.io/servers/apify/"><img src="https://mcptest.io/badge/server/apify.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/apify.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/apify/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 11:06 AM
Validation detail: Negotiated stateless MCP 2026-07-28 at https://mcp.apify.com/; detected transport streamable-http; authentication oauth

Tool inventory

Requires authorization; inventory not observed

The catalog validator lists tools only on servers that answer without credentials. Apify asks for OAuth 2.1 sign-in first, so its tools, resources and prompts were not observed. Connect in the Playground with your own credentials to list them.