Skip to content

Commit 7d8fe4e

Browse files
committed
fix: update README.md
1 parent 2aadca8 commit 7d8fe4e

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

README.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,6 @@ You can find detailed instructions for setting up the MCP server in the [Apify d
7171
To interact with the Apify MCP server, you can use various MCP clients, such as:
7272
- [Claude Desktop](https://claude.ai/download)
7373
- [Visual Studio Code](https://code.visualstudio.com/)
74-
- [LibreChat](https://www.librechat.ai/)
7574
- [Apify Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-client)
7675
- Other clients at [https://modelcontextprotocol.io/clients](https://modelcontextprotocol.io/clients)
7776
- More clients at [https://glama.ai/mcp/clients](https://glama.ai/mcp/clients)
@@ -83,7 +82,7 @@ With MCP server integrated, you can ask your AI assistant things like:
8382
- "Provide a step-by-step guide on using the Model Context Protocol, including source URLs."
8483
- "What Apify Actors can I use?"
8584

86-
### Supported Clients Matrix
85+
### Supported clients matrix
8786

8887
The following table outlines the tested MCP clients and their level of support for key features.
8988

@@ -92,12 +91,19 @@ The following table outlines the tested MCP clients and their level of support f
9291
| **Claude.ai (web)** | ✅ Full | |
9392
| **Claude Desktop** | 🟡 Partial | Tools may need to be reloaded manually in the client. |
9493
| **VS Code (Genie)** | ✅ Full | |
95-
| **LibreChat** | ❓ Untested | |
9694
| **Apify Tester MCP Client** | ✅ Full | Designed for testing Apify MCP servers. |
9795

98-
*This matrix is a work in progress. If you have tested other clients, please consider contributing to this documentation.*
96+
Apify MCP Server is compatible with any MCP client that adheres to the [Model Context Protocol](https://modelcontextprotocol.org/), but the level of support for dynamic tool discovery and other features may vary between clients. Therefore, the server uses [mcp-client-capabilities](https://github.com/apify/mcp-client-capabilities) to detect client capabilities and adjust its behavior accordingly.
9997

100-
# 🪄 Try Apify MCP Instantly
98+
**Smart tool selection based on client capabilities:**
99+
100+
When the `actors` tool category is requested, the server intelligently selects the most appropriate Actor-related tools based on the client's capabilities:
101+
102+
- **Clients with dynamic tool support** (e.g., Claude.ai web, VS Code Genie): The server provides the `add-actor` tool instead of `call-actor`. This allows for a better user experience where users can dynamically discover and add new Actors as tools during their conversation.
103+
104+
- **Clients with limited dynamic tool support** (e.g., Claude Desktop): The server provides the standard `call-actor` tool along with other Actor category tools, ensuring compatibility while maintaining functionality.
105+
106+
# 🪄 Try Apify MCP instantly
101107

102108
Want to try Apify MCP without any setup?
103109

@@ -172,6 +178,8 @@ Here is an overview list of all the tools provided by the Apify MCP Server.
172178

173179
> **Note:**
174180
>
181+
> When using the `actors` tool category, clients that support dynamic tool discovery (like Claude.ai web and VS Code) automatically receive the `add-actor` tool instead of `call-actor` for enhanced Actor discovery capabilities.
182+
175183
> The `get-actor-output` tool is automatically included with any Actor-related tool, such as `call-actor`, `add-actor`, or any specific Actor tool like `apify-slash-rag-web-browser`. When you call an Actor - either through the `call-actor` tool or directly via an Actor tool (e.g., `apify-slash-rag-web-browser`) - you receive a preview of the output. The preview depends on the Actor's output format and length; for some Actors and runs, it may include the entire output, while for others, only a limited version is returned to avoid overwhelming the LLM. To retrieve the full output of an Actor run, use the `get-actor-output` tool (supports limit, offset, and field filtering) with the `datasetId` provided by the Actor call.
176184
177185
### Tools configuration

0 commit comments

Comments
 (0)