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: sources/platform/integrations/ai/mcp/claude-desktop.md
+47Lines changed: 47 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,6 +57,15 @@ Alternatively, download and open the [Apify MCP server `.mcpb` file](https://git
57
57
58
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
59
60
+
:::tip Quick checks
61
+
62
+
Before diving into specific issues, check these two things first:
63
+
64
+
1._Check the [Claude Desktop logs](#claude-desktop-logs)._ Look for files with `mcp` in the name.
65
+
1._Check [tool permissions](#tools-fail-to-load)._ The connector may block some tools by default.
66
+
67
+
:::
68
+
60
69
#### Tools fail to load
61
70
62
71
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.
@@ -124,6 +133,44 @@ After clearing the cache:
124
133
1. Check the [Claude Desktop logs](#claude-desktop-logs) for errors.
125
134
1. If the issue persists, switch to the [remote server](#remote-server-recommended) setup, which doesn't rely on local packages.
126
135
136
+
#### Connector does not work in Claude Cowork
137
+
138
+
The Apify connector shows as connected in Cowork, but Claude doesn't recognize the tools or can't call them. The same connector works fine in regular Claude Chat.
139
+
140
+
Cowork launches local MCP servers with a different mechanism than Claude Chat and requires a system-wide `node` binary. If Node.js is only installed through a version manager (such as nvm, fnm, nodenv, or Volta), Cowork cannot find it and the server fails to start. The [Claude Desktop logs](#claude-desktop-logs) show `spawn node ENOENT` in this case.
141
+
142
+
Install Node.js system-wide and restart Claude Desktop:
143
+
144
+
<TabsgroupId="operating-system">
145
+
<TabItemvalue="macos"label="macOS">
146
+
147
+
```bash
148
+
brew install node
149
+
```
150
+
151
+
Or download the installer from [nodejs.org](https://nodejs.org).
152
+
153
+
</TabItem>
154
+
<TabItemvalue="windows"label="Windows">
155
+
156
+
Download and run the installer from [nodejs.org](https://nodejs.org).
157
+
158
+
</TabItem>
159
+
<TabItemvalue="linux"label="Linux">
160
+
161
+
```bash
162
+
# Debian/Ubuntu
163
+
sudo apt install nodejs
164
+
165
+
# Fedora
166
+
sudo dnf install nodejs
167
+
```
168
+
169
+
</TabItem>
170
+
</Tabs>
171
+
172
+
A system-wide installation can coexist with an existing version-manager installation. If installing Node.js system-wide is not an option, switch to the [remote server](#remote-server-recommended) setup, which doesn't require a local Node.js runtime.
173
+
127
174
## Known limitations
128
175
129
176
- 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.
0 commit comments