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
Copy file name to clipboardExpand all lines: .actor/ACTOR.md
+11-75Lines changed: 11 additions & 75 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,8 @@
1
1
# Apify Model Context Protocol (MCP) Server
2
2
3
+
> **⚠️ Legacy solution notice**
4
+
> This Actor is legacy implementation of the Apify MCP Server. For the current and actively maintained solution, please visit **[mcp.apify.com](https://mcp.apify.com)** where you'll find the latest server, comprehensive documentation, and setup guides.
Implementation of an MCP server for all [Apify Actors](https://apify.com/store).
@@ -91,18 +94,13 @@ When a tool is called, the arguments are automatically passed to the Actor by th
91
94
You can refer to the specific Actor's documentation for a list of available arguments.
92
95
93
96
### Helper tools
97
+
One of the powerful features of MCP with Apify is dynamic actor tooling – the ability for an AI agent to find new tools (Actors) as needed and incorporate them. Here are some special MCP operations and how Apify MCP Server supports them:
94
98
95
-
The server provides a set of helper tools to discover available Actors and retrieve their details:
96
-
-`get-actor-details`: Retrieves documentation, input schema, and details about a specific Actor.
97
-
-`discover-actors`: Searches for relevant Actors using keywords and returns their details.
98
-
99
-
There are also tools to manage the available tools list. However, dynamically adding and removing tools requires the MCP client to have the capability to update the tools list (handle `ToolListChangedNotificationSchema`), which is typically not supported.
100
-
101
-
You can try this functionality using the [Apify Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-client) Actor.
102
-
To enable it, set the `enableActorAutoLoading` parameter.
103
-
104
-
-`add-actor-as-tool`: Adds an Actor by name to the available tools list without executing it, requiring user consent to run later.
105
-
-`remove-actor-from-tool`: Removes an Actor by name from the available tools list when it's no longer needed.
99
+
- Actor discovery and management: Search for Actors (`search-actors`), view details (`get-actor-details`), and dynamically add or remove tools (`add-actor`, `remove-actor`).
100
+
- Actor execution and monitoring: Start Actor runs, fetch run results (`get-actor-run`), logs (`get-actor-log`), and abort runs (`abort-actor-run`).
101
+
- Dataset access: List datasets, retrieve dataset info and items (`get-dataset`, `get-dataset-list`, `get-dataset-items`).
102
+
- Key-value store access: List key-value stores, view keys, and retrieve records (`get-key-value-store-list`, `get-key-value-store`, `get-key-value-store-keys`, `get-key-value-store-record`).
103
+
- Built-in help tool: A static helper (`apify-actor-help-tool`) that returns usage info for the Apify MCP Server.
106
104
107
105
## Prompt & Resources
108
106
@@ -156,44 +154,6 @@ In the client settings, you need to provide server configuration:
156
154
}
157
155
}
158
156
```
159
-
Alternatively, you can use [clientSse.ts](https://github.com/apify/actor-mcp-server/tree/main/src/examples/clientSse.ts) script or test the server using `curl` </> commands.
160
-
161
-
1. Initiate Server-Sent-Events (SSE) by sending a GET request to the following URL:
The MCP server will start the Actor `lukaskrivka/google-maps-with-contact-details` with the provided arguments as input parameters.
184
-
For this POST request, the server will respond with:
185
-
186
-
```text
187
-
Accepted
188
-
```
189
-
190
-
3. Receive the response. The server will invoke the specified Actor as a tool using the provided query parameters and stream the response back to the client via SSE.
191
-
The response will be returned as JSON text.
192
-
193
-
```text
194
-
event: message
195
-
data: {"result":{"content":[{"type":"text","text":"{\"searchString\":\"restaurants in San Francisco\",\"rank\":1,\"title\":\"Gary Danko\",\"description\":\"Renowned chef Gary Danko's fixed-price menus of American cuisine ... \",\"price\":\"$100+\"...}}]}}
196
-
```
197
157
198
158
## ⾕ MCP Server at a local host
199
159
@@ -216,7 +176,7 @@ If not, follow this guide to install Node.js: [Downloading and installing Node.j
216
176
217
177
#### Claude Desktop
218
178
219
-
To configure Claude Desktop to work with the MCP server, follow these steps. For a detailed guide, refer to the [Claude Desktop Users Guide](https://modelcontextprotocol.io/quickstart/user).
179
+
To configure Claude Desktop to work with the MCP server, follow these steps. For a detailed guide, refer to the [Claude Desktop Users Guide](https://modelcontextprotocol.io/quickstart/user) or watch the [video tutorial](https://youtu.be/gf5WXeqydUU?t=440).
Copy file name to clipboardExpand all lines: README.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,5 @@
1
1
# Apify Model Context Protocol (MCP) Server
2
2
3
-
> **⚠️ Legacy solution notice**
4
-
> This Actor is legacy implementation of the Apify MCP Server. For the current and actively maintained solution, please visit **[mcp.apify.com](https://mcp.apify.com)** where you'll find the latest server, comprehensive documentation, and setup guides.
0 commit comments