Claude Desktop: Unable to connect to extension server with apify-mcp-server
I installed apify-mcp-server and connected Apify through the Connectors feature in Claude Desktop, but I keep getting "Unable to connect to extension server. Please try disabling and re-enabling the extension." Disabling and re-enabling doesn't help. What is the correct way to set up the Apify MCP server in Claude Desktop?
Originally asked on GitHub: https://github.com/apify/apify-mcp-server/issues/560
4 answers
Status: explained. The issue is closed. The maintainers' recommended fix is to skip the local
apify-mcp-serverextension and connect Claude Desktop to the remote Apify MCP server, because Claude Desktop can behave inconsistently with the extension.The setup confirmed as working by multiple users in the thread:
- Go to https://mcp.apify.com/ (opens external site) and get the link for the tools you want.
- In Claude Desktop: Settings → Connectors → Add custom connector, give it a name, and use
https://mcp.apify.comas the URL. - Complete the browser-based OAuth flow to verify the connection.
One user reported success by adding the tool link from
mcp.apify.comas a custom connector along with the Apify API token. If you prefer a JSON config, a maintainer proposed using the remote server throughmcp-remote:json{ "mcpServers": { "apify": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.apify.com/", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } } }One user also got a working connection simply by uninstalling the extension and trying again, after which it connected to Claude Desktop. If the error persists, the maintainer asked for logs via the bug report template and pointed to the troubleshooting section in the
apify/apify-mcp-serverREADME and the Apify docs.Did this work for you?What @YagneshKhamar tried on GitHub (Worked)
Got the tool link from https://mcp.apify.com/ (opens external site), added it as a custom connector in Claude Desktop with a name, link, and API token, then completed the browser verification. The maintainer confirmed this approach and another user reported it worked.
Source: https://github.com/apify/apify-mcp-server/issues/560#issuecomment-4222783227 (opens external site)
Did this work for you?What @the-niresh tried on GitHub (Worked)
Uninstalled the apify-mcp-server extension and tried again; the user reported it then connected to Claude Desktop.
Source: https://github.com/apify/apify-mcp-server/issues/560#issuecomment-4074783260 (opens external site)
Did this work for you?What @jirispilka tried on GitHub (Outcome unclear)
A maintainer suggested using the remote Apify MCP via
npx mcp-remote https://mcp.apify.com/ --header "Authorization: Bearer <YOUR_API_TOKEN>"in the mcpServers config, but the thread doesn't show this being tried or confirmed.Source: https://github.com/apify/apify-mcp-server/issues/560#issuecomment-4080246818 (opens external site)
Did this work for you?
Related questions
- OpenAI rejects apify-mcp-server tools: 'array schema missing items' and '--' in tool name
- Open WebUI not calling apify-mcp-server — what URL should I use?
- apify website-content-crawler fails: proxyConfiguration required even when not sent
- Why does Apify MCP server truncate Actor output and call get-dataset-items again?
- Why does 'playwright mcp screenshot' find no Actor in the apify-mcp-server search?