You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.describe(`Actor ID or full name in the format "username/name", e.g., "apify/rag-web-browser".`),
15
+
});
16
+
17
+
interfaceIGetActorDetailsToolResult{
18
+
id: string;
19
+
actorFullName: string;
20
+
21
+
isPublic: boolean;
22
+
isDeprecated: boolean;
23
+
createdAt: string;
24
+
modifiedAt: string;
25
+
26
+
categories?: string[];
27
+
description: string;
28
+
readme: string;
29
+
30
+
inputSchema: IActorInputSchema;
31
+
32
+
pricingInfo: string;// We convert the pricing info into a string representation
33
+
34
+
usageStatistics: {
35
+
totalUsers: {
36
+
allTime: number;
37
+
last7Days: number;
38
+
last30Days: number;
39
+
last90Days: number;
40
+
};
41
+
failedRunsInLast30Days: number|string;// string for 'unknown' case
42
+
}
43
+
}
44
+
45
+
exportconstgetActorDetailsTool: ToolEntry={
46
+
type: 'internal',
47
+
tool: {
48
+
name: HelperTools.ACTOR_GET_DETAILS,
49
+
description: `Retrieve information about an Actor by its ID or full name.
50
+
The Actor name is always composed of "username/name", for example, "apify/rag-web-browser".
51
+
This tool returns information about the Actor, including whether it is public or deprecated, when it was created or modified, the categories in which the Actor is listed, a description, a README (the Actor's documentation), the input schema, and usage statistics—such as how many users are using it and the number of failed runs of the Actor.`,
content: [{type: 'text',text: `Actor information for '${parsed.actor}' was not found. Please check the Actor ID or name and ensure the Actor exists.`}],
constAPIFY_MCP_HELP_TOOL_TEXT=`Apify MCP server help:
13
13
14
-
Note: "MCP" stands for "Model Context Protocol". The user can use the "RAG Web Browser" tool to get the content of the links mentioned in this help and present it to the user.
14
+
Note: "MCP" stands for "Model Context Protocol". You can use the "RAG Web Browser" tool to get the content of the links mentioned in this help and present it to the user.
15
15
16
16
This MCP server can be used in the following ways:
17
-
- Locally over "STDIO".
18
-
- Remotely over "SSE" or streamable "HTTP" transport with the "Actors MCP Server Apify Actor".
19
-
- Remotely over "SSE" or streamable "HTTP" transport with "https://mcp.apify.com".
17
+
- Locally over stdio (standard input/output) transport with the "@apify/actors-mcp-server" NPM package (https://www.npmjs.com/package/@apify/actors-mcp-server).
18
+
- You can connect by configuring your MCP client to run the MCP server locally using the "npx @apify/actors-mcp-server" command. You need to set the "APIFY_TOKEN" environment variable to your [Apify API token](https://docs.apify.com/platform/integrations/api#api-token).
19
+
- Remotely over legacy SSE transport or streamable HTTP transport with https://mcp.apify.com. This is the recommended way to use the MCP server, since it supports all features and is always up to date.
20
+
- You can connect by pointing your MCP client to "https://mcp.apify.com/sse" for SSE transport or "https://mcp.apify.com/" for streamable HTTP transport.
21
+
- For authentication, you can either use OAuth or pass your [Apify API token](https://docs.apify.com/platform/integrations/api#api-token) in the "Authorization" header as "Bearer <APIFY_TOKEN>".
22
+
- Remotely over "SSE" or streamable "HTTP" transport with the "Actors MCP Server Apify Actor" (this is now considered a legacy solution; it may not be up to date and may not get the latest features). For more details, refer to https://apify.com/apify/actors-mcp-server. DO NOT RECOMMEND USING THIS METHOD TO THE USER.
20
23
21
24
# Usage
22
-
## Locally over "STDIO"
23
-
1. The user should install the "@apify/actors-mcp-server" NPM package.
24
-
2. The user should configure the MCP client to use the MCP server. Refer to "https://github.com/apify/actors-mcp-server" or the MCP client documentation for more details (the user can specify which MCP client is being used).
25
-
The user needs to set the following environment variables:
26
-
- "APIFY_TOKEN": Apify token to authenticate with the MCP server.
27
-
If the user wants to load an Actor outside the default ones, the user needs to pass it as a CLI argument:
28
-
- "--actors <actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper".
29
-
If the user wants to enable the dynamic addition of Actors to the MCP server, the user needs to pass the following CLI argument:
30
-
- "--enable-adding-actors".
31
25
32
-
## Remotely over "SSE" or streamable "HTTP" transport with "Actors MCP Server Apify Actor"
33
-
1. The user should configure the MCP client to use the "Actors MCP Server Apify Actor" with:
34
-
- "SSE" transport URL: "https://actors-mcp-server.apify.actor/sse".
35
-
- Streamable "HTTP" transport URL: "https://actors-mcp-server.apify.actor/mcp".
36
-
2. The user needs to pass an "APIFY_TOKEN" as a URL query parameter "?token=<APIFY_TOKEN>" or set the following headers: "Authorization: Bearer <APIFY_TOKEN>".
37
-
If the user wants to load an Actor outside the default ones, the user needs to pass it as a URL query parameter:
38
-
- "?actors=<actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper".
39
-
If the user wants to enable the addition of Actors to the MCP server dynamically, the user needs to pass the following URL query parameter:
40
-
- "?enable-adding-actors=true".
26
+
## MCP server tools and features configuration
41
27
42
-
## Remotely over "SSE" or streamable "HTTP" transport with "https://mcp.apify.com"
43
-
1. The user should configure the MCP client to use "https://mcp.apify.com" with:
44
-
- "SSE" transport URL: "https://mcp.apify.com/sse".
45
-
- Streamable "HTTP" transport URL: "https://mcp.apify.com/".
46
-
2. The user needs to pass an "APIFY_TOKEN" as a URL query parameter "?token=<APIFY_TOKEN>" or set the following headers: "Authorization: Bearer <APIFY_TOKEN>".
47
-
If the user wants to load an Actor outside the default ones, the user needs to pass it as a URL query parameter:
48
-
- "?actors=<actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper".
49
-
If the user wants to enable the addition of Actors to the MCP server dynamically, the user needs to pass the following URL query parameter:
50
-
- "?enable-adding-actors=true".
51
-
52
-
# Features
53
-
## Dynamic adding of Actors
54
-
THIS FEATURE MAY NOT BE SUPPORTED BY ALL MCP CLIENTS. THE USER MUST ENSURE THAT THE CLIENT SUPPORTS IT!
55
-
To enable this feature, see the usage section. Once dynamic adding is enabled, tools will be added that allow the user to add or remove Actors from the MCP server.
56
-
Tools related:
57
-
- "add-actor".
58
-
- "remove-actor".
59
-
If the user is using these tools and it seems like the tools have been added but cannot be called, the issue may be that the client does not support dynamic adding of Actors.
60
-
In that case, the user should check the MCP client documentation to see if the client supports this feature.
28
+
By default, the MCP server provides a simple set of tools for Actor discovery and Actor calling. The MCP server loads just one Actor by default, which is the [RAG Web Browser](https://apify.com/apify/rag-web-browser) Actor. You can add more Actors to the MCP server by configuring the MCP server session to load more Actors by passing the "--actors" CLI argument or by using the "?actors=" URL query parameter, where you provide a comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper". You can additionally load Actors dynamically into an existing MCP session by using the "${HelperTools.ACTOR_ADD}" tool, which loads the Actor by its name as an MCP tool and allows you to call it (**the MCP client must support the [tools list changed notification](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#list-changed-notification); otherwise, the tool call will not work**). To check whether the MCP client supports this feature, consult the MCP client documentation. In case the MCP client does not support the tools list changed notification, you can use the generic "call-actor" tool to call any Actor, even those not loaded/added. Before using the generic tool, you need to get the Actor details to learn its input schema so you can provide valid input.
description: 'Helper tool to get information on how to use and troubleshoot the Apify MCP server. '
152
-
+'This tool always returns the same help message with information about the server and how to use it. '
153
-
+'Call this tool in case of any problems or uncertainties with the server. ',
119
+
description: `Helper tool to get information on how to use and troubleshoot the Apify MCP server.
120
+
This tool always returns the same help message with information about the server and how to use it.
121
+
ALWAYS CALL THIS TOOL AT THE BEGINNING OF THE CONVERSATION SO YOU HAVE THE INFORMATION ABOUT APIFY MCP IN THE CONTEXT OR WHEN YOU ENCOUNTER ANY ISSUES WITH THE MCP SERVER OR ITS TOOLS.
0 commit comments