# Apify MCP server > Run thousands of Apify Store Actors to scrape websites, extract data and automate web tasks from your AI assistant. - Listing: https://mcp.tc/i/apify - Connect: use the server's own URL `https://mcp.apify.com` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Search & Web Data](https://mcp.tc/c/search-web) - Vendor: Apify - Homepage: - Repository: - Package: npm `@apify/actors-mcp-server` ## About Connects your assistant to the Apify Store, a marketplace of ready-made scrapers, crawlers and automation tools called Actors. Actors can extract data from social media, search engines, maps, e-commerce and travel sites, or fetch and read arbitrary web pages. The server also covers Actor tasks, schedules and run storage such as datasets and key-value stores. The hosted endpoint at https://mcp.apify.com uses streamable HTTP and supports OAuth sign-in, or an Authorization: Bearer header with an Apify API token. A local stdio option is available through the npm package @apify/actors-mcp-server, which needs the APIFY\_TOKEN environment variable. Running Actors uses an Apify account. ## What it can do - Search the Apify Store for Actors that fit a task - Read an Actor's README and input schema before running it - Run Actors and retrieve dataset and key-value store output - Scrape social media, maps, search results and e-commerce sites - Fetch web pages as Markdown, text, HTML or links - Create and run saved Actor tasks and schedules ## Example prompts - "Find an Apify Actor that scrapes Google Maps and run it for coffee shops in Berlin" - "Scrape the latest posts from this Instagram profile and summarize them" - "Fetch this URL as Markdown using Apify" - "Schedule my saved Actor task to run every day at 08:00 UTC" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http apify https://mcp.apify.com ``` 2. Start Claude Code, type `/mcp`, pick **apify** and choose **Authenticate**. A browser window opens for the Apify sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Apify** and paste this URL: ```url https://mcp.apify.com ``` 3. Click **Add**, then **Connect**, and sign in when Apify asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.apify.com` and click **Add**. 3. Click **Connect** and sign in when Apify asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.apify.com` as the server URL and choose **OAuth**. ChatGPT sends you to Apify to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"apify","type":"http","url":"https://mcp.apify.com"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "apify": { "type": "http", "url": "https://mcp.apify.com" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "apify": { "serverUrl": "https://mcp.apify.com" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add apify --url https://mcp.apify.com codex mcp login apify ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.apify] url = "https://mcp.apify.com" ``` ### Gemini CLI ```bash gemini mcp add --transport http apify https://mcp.apify.com ``` Then, inside Gemini CLI, run `/mcp auth apify` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.apify.com`. ## Details - Server version: 0.17.1 - MCP protocol version: 2026-07-28 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/apify (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report