Apify MCP Server

Apify MCP Server MCP Server

Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation. You can extract structured data from social media, e-commerce, search engines, maps, travel sites, or any other website.

What is an MCP Server?⁠

Characteristics

Attribute	Details
Docker Image	mcp/apify-mcp-server⁠
Author	apify⁠
Repository	https://github.com/apify/actors-mcp-server⁠
Dockerfile	https://github.com/apify/actors-mcp-server/blob/master/Dockerfile⁠
Docker Image built by	Docker Inc.
Docker Scout Health Score
Verify Signature	COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/apify-mcp-server --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
Licence	MIT License

Available Tools (7)

Tools Details

Tool: apify-slash-rag-web-browser

This tool calls the Actor "apify/rag-web-browser" and retrieves its output results. Use this tool instead of the "call-actor" if user requests to use this specific Actor. Actor description: Web browser for OpenAI Assistants, RAG pipelines, or AI agents, similar to a web browser in ChatGPT. It queries Google Search, scrapes the top N pages, and returns their content as Markdown for further processing by an LLM. It can also scrape individual URLs. Supports Model Context Protocol (MCP). Instructions: Never call/execute tool/Actor unless confirmed by the user.

• san francisco weather

• https://www.cnn.com⁠

• function calling site:openai.com Example values: "web browser for RAG pipelines -site:reddit.com" debugMode|booleanoptional|If enabled, the Actor will store debugging information into the resulting dataset under the debug field. desiredConcurrency|integeroptional|The desired number of web browsers running in parallel. The system automatically scales the number based on the CPU and memory usage. If the initial value is 0, the Actor picks the number automatically based on the available memory. Example values: 5 dynamicContentWaitSecs|integeroptional|The maximum time in seconds to wait for dynamic page content to load. The Actor considers the web page as fully loaded once this time elapses or when the network becomes idle. Example values: 10 htmlTransformer|stringoptional|Specify how to transform the HTML to extract meaningful content without any extra fluff, like navigation or modals. The HTML transformation happens after removing and clicking the DOM elements.

• None (default) - Only removes the HTML elements specified via 'Remove HTML elements' option.

• Readable text - Extracts the main contents of the webpage, without navigation and other fluff. Example values: "none" maxRequestRetries|integeroptional|The maximum number of times the Actor will retry loading the target web page on error. If the last attempt fails, the page will be skipped in the results. Example values: 1 maxResults|integeroptional|The maximum number of top organic Google Search results whose web pages will be extracted. If query is a URL, then this field is ignored and the Actor only fetches the specific web page. Example values: 3 outputFormats|arrayoptional|Select one or more formats to which the target web pages will be extracted and saved in the resulting dataset. Example values: ["markdown"] proxyConfiguration|objectoptional|Apify Proxy configuration used for scraping the target web pages. Example values: {"useApifyProxy":true} removeCookieWarnings|booleanoptional|If enabled, the Actor attempts to close or remove cookie consent dialogs to improve the quality of extracted text. Note that this setting increases the latency. Example values: true removeElementsCssSelector|stringoptional|A CSS selector matching HTML elements that will be removed from the DOM, before converting it to text, Markdown, or saving as HTML. This is useful to skip irrelevant page content. The value must be a valid CSS selector as accepted by the document.querySelectorAll() function.

By default, the Actor removes common navigation elements, headers, footers, modals, scripts, and inline image. You can disable the removal by setting this value to some non-existent CSS selector like dummy_keep_everythi... Example values: "nav, footer, script, style, noscript, svg, img[src^='data:'],\n[role=\"alert\"],\n[role=\"banner\"],\n[role=\"dialog\"],\n[role=\"alertdialog\"],\n[role=\"region\"][aria-label*=\"skip\" i],\n[aria-modal=\"true\"]" requestTimeoutSecs|integer*optional*|The maximum time in seconds available for the request, including querying Google Search and scraping the target web pages. For example, OpenAI allows only [45 seconds](https://platform.openai.com/docs/actions/production#timeouts) for custom actions. If a target page loading and extraction exceeds this timeout, the corresponding page will be skipped in results to ensure at least some results are returned within the timeout. If no page is extracted within the timeout, the whole request fails. Example values: 40scrapingTool|string*optional*|Select a scraping tool for extracting the target web pages. The Browser tool is more powerful and can handle JavaScript heavy websites, while the Plain HTML tool can't handle JavaScript but is about two times faster. Possible values: browser-playwright,raw-http Example values: "raw-http"serpMaxRetries|integer*optional*|The maximum number of times the Actor will retry fetching the Google Search results on error. If the last attempt fails, the entire request fails. Example values: 2serpProxyGroup|string` optional|Enables overriding the default Apify Proxy group used for fetching Google Search results. Possible values: GOOGLE_SERP,SHADER Example values: "GOOGLE_SERP"

Tool: call-actor

Call Any Actor from Apify Store - Two-Step Process

This tool uses a mandatory two-step process to safely call any Actor from the Apify store.

USAGE: • ONLY for Actors that are NOT available as dedicated tools • If a dedicated tool exists (e.g., apify-slash-rag-web-browser), use that instead

MANDATORY TWO-STEP WORKFLOW:

Step 1: Get Actor Info (step="info", default) • First call this tool with step="info" to get Actor details and input schema • This returns the Actor description, documentation, and required input schema • You MUST do this step first - it's required to understand how to call the Actor

Step 2: Call Actor (step="call") • Only after step 1, call again with step="call" and proper input based on the schema • This executes the Actor and returns the results

The step parameter enforces this workflow - you cannot call an Actor without first getting its info.

Tool: fetch-actor-details

Get detailed information about an Actor by its ID or full name. This tool returns title, description, URL, README (Actor's documentation), input schema, and usage statistics. The Actor name is always composed of "username/name", for example, "apify/rag-web-browser". Present Actor information in user-friendly format as an Actor card. USAGE:

• Use when user asks about an Actor its details, description, input schema, etc. EXAMPLES:
• user_input: How to use apify/rag-web-browser
• user_input: What is the input schema for apify/rag-web-browser Parameters|Type|Description -|-|- actor|string|Actor ID or full name in the format "username/name", e.g., "apify/rag-web-browser".

Tool: fetch-apify-docs

Apify documentation fetch tool. This tool allows you to fetch the full content of an Apify documentation page by its URL.

Tool: get-actor-output

Retrieves the output of a specific Actor execution based on its dataset ID. You can also retrieve only specific fields from the output if needed. Use this tool to get Actor output data outside of the Actor dataset output preview, or to access fields from the Actor output dataset schema that are not included in the preview.

Note: This tool is automatically included if the Apify MCP Server is configured with any Actor tools (e.g. apify-slash-rag-web-browser) or tools that can interact with Actors (e.g. call-actor, add-actor).

Tool: search-actors

Search for Actors or Model Context Protocol (MCP) servers in the Apify Store using keywords. This tool returns a list of Actors with title, description, pricing model, usage statistics, and user ratings. Use simple space-separated keywords for best results, such as "web scraping", "data extraction", or "playwright mcp". You may need to use this tool several times to find the right Actor. Limit the number of results returned, but ensure that relevant results are included. Always present the results in a user-friendly format as an Actor cards.

USAGE:

• Use when user wants to find Actors for a specific task or technology
• Use when user asks about available Actors in the Apify Store
• Use when user needs to discover MCP servers or automation tools EXAMPLES:
• user_input: Find Actors for web scraping
• user_input: Search for MCP servers
• user_input: What Actors are available for data extraction
• user_input: Show me Actors that use Playwright Parameters|Type|Description -|-|- category|stringoptional|Filter the results by the specified category. limit|integeroptional|The maximum number of Actors to return. The default value is 10. offset|integeroptional|The number of elements to skip at the start. The default value is 0. search|stringoptional|A string to search for in the Actor's title, name, description, username, and readme. Use simple space-separated keywords, such as "web scraping", "data extraction", or "playwright browser mcp". Do not use complex queries, AND/OR operators, or other advanced syntax, as this tool uses full-text search only.

Tool: search-apify-docs

Apify documentation search tool. This tool allows you to search the Apify documentation using Algolia's full-text search. You can use it to find relevant documentation pages based on keywords. The results will include the URL of the documentation page, a fragment identifier (if available), and a limited piece of content that matches the search query. You can then fetch the full content of the document using the fetch-apify-docs tool by providing the URL. Use this tool when a user asks for help with Apify documentation or when you need to find relevant documentation pages based on keywords. For example, when a user wants to build an Apify Actor, you can search "How to build Actors" to find relevant guidance.

Use this MCP Server

{
  "mcpServers": {
    "apify-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TOOLS",
        "-e",
        "APIFY_TOKEN",
        "mcp/apify-mcp-server"
      ],
      "env": {
        "TOOLS": "actors,docs,apify/rag-web-browser",
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?⁠