Skip to content

Commit 230e61b

Browse files
marcel-rbroclaude
andauthored
docs: add Claude Desktop integration and nest MCP client pages under mcp/ directory (#2371)
## Summary - Nest MCP client pages under `mcp/` directory (`mcp.md` → `mcp/index.md`, `chatgpt.md` → `mcp/chatgpt.md`) - Add a dedicated Claude Desktop integration page with setup (remote server with OAuth/Bearer token, one-click connector install) and troubleshooting - Simplify the Claude Desktop tab on the main MCP page to show only the basic OAuth setup and link to the dedicated page - Update the main MCP page troubleshooting section to cross-reference Claude Desktop-specific issues - Fix style guide violations: en-dashes → hyphens, numbered list formatting, terminology consistency Closes #2368 ## Test plan - [ ] Verify page renders at `/integrations/claude-desktop` - [ ] Confirm sidebar shows "Claude Desktop" nested under "MCP server" - [ ] Check all internal cross-links work in both directions (main MCP ↔ Claude Desktop) - [ ] Verify `npm run build` passes with no broken links - [ ] Review content against Apify style guide (markdownlint + Vale pass) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent dad65d7 commit 230e61b

3 files changed

Lines changed: 152 additions & 31 deletions

File tree

sources/platform/integrations/ai/chatgpt.md renamed to sources/platform/integrations/ai/mcp/chatgpt.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Before connecting ChatGPT to Apify, you'll need:
3131

3232
1. In ChatGPT, go to **Settings > Apps & Connectors > Create**. If you don't see the **Create** button, enable Developer mode or reload the page.
3333

34-
2. Fill in the following fields:
34+
1. Fill in the following fields:
3535

3636
- **Name** - a user-facing title, e.g., `apify-mcp`
3737
- **Description** - a short description of what the connector does
@@ -41,10 +41,10 @@ Before connecting ChatGPT to Apify, you'll need:
4141
- Refer to [mcp.apify.com](https://mcp.apify.com) for details
4242
- **Authentication** - OAuth, you don’t need to provide a client ID or secret.
4343

44-
3. Select **Create** to proceed to the authentication page.
44+
1. Select **Create** to proceed to the authentication page.
4545
You’ll be redirected to the Apify website to authorize ChatGPT to access your Apify account.
4646

47-
![ChatGPT Create connection](../images/chatgpt-connector.png)
47+
![ChatGPT Create connection](../../images/chatgpt-connector.png)
4848

4949
Once authorized, you'll return to ChatGPT and see a success message with a list of tools available from the Apify MCP server.
5050

@@ -67,7 +67,7 @@ Once your connector is ready:
6767
You'll need to grant permission for each Apify tool when it's used for the first time.
6868
You should see ChatGPT calling Apify tools - such as the [RAG Web Browser](https://apify.com/apify/rag-web-browser) - to gather information.
6969

70-
![ChatGPT Apify tools](../images/chatgpt-with-rag-web-browser.png)
70+
![ChatGPT Apify tools](../../images/chatgpt-with-rag-web-browser.png)
7171

7272
## Limitations
7373

Lines changed: 137 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,137 @@
1+
---
2+
title: Claude Desktop integration
3+
sidebar_label: Claude Desktop
4+
description: Learn how to set up the Apify MCP server in Claude Desktop using the remote server or one-click connector install, and troubleshoot common issues.
5+
sidebar_position: 2
6+
slug: /integrations/claude-desktop
7+
---
8+
9+
import Tabs from '@theme/Tabs';
10+
import TabItem from '@theme/TabItem';
11+
import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx';
12+
13+
Connect [Claude Desktop](https://claude.ai/download) to the [Apify MCP server](/platform/integrations/mcp) to give your conversations access to thousands of Actors from [Apify Store](https://apify.com/store). Once connected, Claude can search for, run, and retrieve results from Actors directly in your chat.
14+
15+
<ThirdPartyDisclaimer />
16+
17+
## Prerequisites
18+
19+
- An [Apify account](https://console.apify.com/sign-up)
20+
- [Claude Desktop](https://claude.ai/download) installed
21+
22+
## Connect to Apify
23+
24+
Choose one of the following methods:
25+
26+
- [Remote server](#remote-server-recommended) - recommended, automatic updates, OAuth support, no local dependencies
27+
- [One-click installation](#one-click-installation) - install from the connector directory
28+
29+
### Remote server (recommended)
30+
31+
The remote server at `https://mcp.apify.com` is the recommended way to connect. Key advantages:
32+
33+
- Automatic updates - always runs the latest version of the Apify MCP server
34+
- OAuth authentication - secure sign-in through your browser, no API token needed
35+
- No local dependencies - nothing to install or maintain on your machine
36+
37+
To set up the remote server, [add a custom connector](https://support.claude.com/en/articles/11175166) in Claude Desktop and use `https://mcp.apify.com` as the server URL.
38+
39+
On first connection, your browser opens to sign in to Apify and authorize the connection.
40+
41+
### One-click installation
42+
43+
Search for "Apify" in the [Claude Desktop connector directory](https://support.claude.com/en/articles/11175166) and install the connector.
44+
45+
Alternatively, download and open the [Apify MCP server `.mcpb` file](https://github.com/apify/actors-mcp-server/releases/latest/download/apify-mcp-server.mcpb) to register the connector automatically.
46+
47+
## Verify the connection
48+
49+
1. Restart Claude Desktop after saving configuration changes.
50+
1. Open a new conversation.
51+
1. Check that Apify tools are available in the tools list.
52+
1. Test with a prompt like: "Search for web scraping Actors on Apify."
53+
54+
## Troubleshooting
55+
56+
<!-- markdownlint-disable MD001 -->
57+
58+
If the steps below don't resolve your issue, [submit a GitHub issue](https://github.com/apify/apify-mcp-server/issues) or contact [Apify support](https://apify.com/contact).
59+
60+
#### Tools fail to load
61+
62+
The MCP server shows as connected but Apify tools don't appear in the tools list, or Claude doesn't recognize any Apify tools in conversation.
63+
64+
- _Check tool permissions._ Individual connector tools can be blocked in your [connector settings](https://support.anthropic.com/en/articles/11175166-how-to-manage-and-remove-integrations-in-claude). Verify that Apify tools are set to **Always allow** or **Ask first**, not blocked.
65+
- _Check the connector version._ Claude Desktop may silently downgrade the connector to an older version. If tools aren't appearing despite the connector showing as enabled, remove and re-add the connector to trigger an update.
66+
- _Restart Claude Desktop._ Configuration changes only take effect after a restart.
67+
- _Reinstall the connector._ Remove the Apify connector and add it again.
68+
69+
#### Authentication errors
70+
71+
Authentication errors occur when the MCP server can't verify your identity. You may see "Unauthorized" or "Invalid token" messages, or Actor runs may fail silently.
72+
73+
- _Re-authorize the connection._ Remove and re-add the Apify connector in Claude Desktop to trigger a new OAuth flow.
74+
75+
#### Claude Desktop logs
76+
77+
Check the Claude Desktop logs for MCP-related errors:
78+
79+
- macOS: `~/Library/Logs/Claude/`
80+
- Linux: `~/.config/Claude/logs/`
81+
- Windows: `%APPDATA%\Claude\logs\`
82+
83+
Look for files with `mcp` in the name for server-specific error messages.
84+
85+
### One-click installation issues
86+
87+
The following troubleshooting steps apply specifically to the [one-click installation](#one-click-installation) method. The remote server runs entirely on Apify's infrastructure, so there are no local logs or configuration to debug. If you experience issues with the [remote server](#remote-server-recommended), contact [Apify support](https://apify.com/contact).
88+
89+
#### "Unable to connect to extension server" error
90+
91+
This is the most common issue. It typically appears when installing from the Claude Desktop connector directory. In some cases, the MCP server starts and communicates correctly, but Claude Desktop still shows the error.
92+
93+
1. _Consider switching to the [remote server](#remote-server-recommended) setup._ The remote server is the most reliable option.
94+
1. _Uninstall and reinstall the extension._ In Claude Desktop, disable the Apify extension, remove it, then add it again.
95+
1. _Clear the npx cache._ A stale cache can cause connection failures. Follow the steps in [Corrupted npx cache](#corrupted-npx-cache).
96+
1. _Check the [Claude Desktop logs](#claude-desktop-logs)_ for specific error messages.
97+
1. _Check your network._ Ensure your firewall or VPN is not blocking the connection.
98+
1. _Still not working?_ [Submit a GitHub issue](https://github.com/apify/apify-mcp-server/issues) or contact [Apify support](https://apify.com/contact).
99+
100+
#### Corrupted npx cache
101+
102+
A stale or corrupted npx cache can prevent the server from starting. Clear the cache and retry:
103+
104+
<Tabs groupId="operating-system">
105+
<TabItem value="macos-linux" label="macOS and Linux">
106+
107+
```bash
108+
rm -rf ~/.npm/_npx
109+
```
110+
111+
</TabItem>
112+
<TabItem value="windows" label="Windows">
113+
114+
```text
115+
rmdir /s /q %LOCALAPPDATA%\npm-cache\_npx
116+
```
117+
118+
</TabItem>
119+
</Tabs>
120+
121+
After clearing the cache:
122+
123+
1. Restart Claude Desktop to re-download the server package.
124+
1. Check the [Claude Desktop logs](#claude-desktop-logs) for errors.
125+
1. If the issue persists, switch to the [remote server](#remote-server-recommended) setup, which doesn't rely on local packages.
126+
127+
## Known limitations
128+
129+
- Claude Desktop may silently downgrade an installed connector to an older version (for example, from 0.9.14 back to 0.9.6). This can cause tools to stop loading even though the connector still shows as enabled. Removing and re-adding the connector may prompt an update, but doesn't always resolve the issue.
130+
- Some Claude Desktop versions have inconsistent behavior with remote MCP server connections. Update to the latest version if you experience issues.
131+
- If the connector directory installation fails, use the [remote server](#remote-server-recommended) at `https://mcp.apify.com` instead.
132+
133+
## Next steps
134+
135+
- [Apify MCP server](/platform/integrations/mcp) - Explore tool selection, available tools, telemetry, and rate limits
136+
- [Apify MCP server configurator](https://mcp.apify.com) - Select tools visually and copy configuration
137+
- [Apify MCP server on GitHub](https://github.com/apify/apify-mcp-server) - Report bugs and suggest features

sources/platform/integrations/ai/mcp.md renamed to sources/platform/integrations/ai/mcp/index.md

Lines changed: 11 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Apify MCP server
3-
sidebar_label: MCP
3+
sidebar_label: MCP server
44
description: Learn how to use the Apify MCP server to integrate Apify's library of Actors into your AI agents or large language model-based applications.
55
sidebar_position: 1
66
slug: /integrations/mcp
@@ -18,7 +18,7 @@ using [Model Context Protocol](https://modelcontextprotocol.io/docs/getting-star
1818
discover and run Actors from [Apify Store](https://apify.com/store), access storages and results,
1919
and enables AI coding assistants to access Apify documentation and tutorials.
2020

21-
![Apify MCP server](../../images/apify_mcp_server.png)
21+
![Apify MCP server](../../../images/apify_mcp_server.png)
2222

2323
<ThirdPartyDisclaimer />
2424

@@ -208,33 +208,11 @@ VS Code supports MCP through GitHub Copilot's agent mode (requires Copilot subsc
208208
</TabItem>
209209
<TabItem value="claude-desktop" label="Claude Desktop">
210210

211-
:::tip One-click installation
212-
213-
Download and run the [Apify MCP server `.mcpb` file](https://github.com/apify/actors-mcp-server/releases/latest/download/apify-mcp-server.mcpb) for one-click installation.
214-
215-
:::
216-
217-
To manually configure Apify's MCP server for Claude Desktop:
218-
219-
1. Open Claude Desktop settings.
220-
1. Navigate to the **Developer** section.
221-
1. Add the following to the configuration file:
211+
[Add a custom connector](https://support.claude.com/en/articles/11175166) in Claude Desktop and use `https://mcp.apify.com` as the server URL. On first connection, your browser opens to sign in to Apify and authorize the connection.
222212

223-
```json
224-
{
225-
"mcpServers": {
226-
"actors-mcp-server": {
227-
"command": "npx",
228-
"args": ["-y", "@apify/actors-mcp-server"],
229-
"env": {
230-
"APIFY_TOKEN": "<APIFY_TOKEN>"
231-
}
232-
}
233-
}
234-
}
235-
```
213+
You can also search for "Apify" in the connector directory and install it directly.
236214

237-
Replace `<APIFY_TOKEN>` with your actual Apify API token from the [API & Integrations section](https://console.apify.com/settings/integrations).
215+
For detailed setup options and troubleshooting, see the [Claude Desktop integration guide](/platform/integrations/claude-desktop).
238216

239217
</TabItem>
240218
</Tabs>
@@ -399,6 +377,12 @@ documentation queries. If you exceed this limit, you'll receive a `429` response
399377
<!-- markdownlint-disable MD001 -->
400378
## Troubleshooting
401379

380+
:::tip Claude Desktop issues
381+
382+
For Claude Desktop-specific troubleshooting (tools not loading, connection errors, corrupted cache), see [Claude Desktop troubleshooting](/platform/integrations/claude-desktop#troubleshooting).
383+
384+
:::
385+
402386
##### Authentication errors
403387

404388
- _Check your API token_: Verify that your Apify API token is correct. You can find it in the **API & Integrations** section of the [Apify Console](https://console.apify.com/settings/integrations). Without a valid token, the server cannot start Actor runs.

0 commit comments

Comments
 (0)