Give Claude Desktop live web data

The quickest route is a custom connector: open Customize, then Connectors, add a custom connector with Apify's MCP URL and sign in to Apify. If you prefer a local server, add the @apify/actors-mcp-server entry to claude_desktop_config.json with your token and restart the app.

Method

  1. Easiest: open Customize, then Connectors, choose Add custom connector, paste the server URL (the ChatGPT tab shows it on its own) and sign in to Apify.

    Claude Desktop config for Google Maps Business Lead Finder with Email & Social Linksclaude_desktop_config.json

    Actor on Apify 
    {
  "mcpServers": {
    "google-maps-business-lead-finder-with-email": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--tools",
        "fetch-actor-details,vexaloom-labs/google-maps-business-lead-finder-with-email"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}

  2. Local alternative (needs Node.js): merge this into claude_desktop_config.json (Settings, Developer, Edit config) and replace YOUR_APIFY_TOKEN.

  3. Restart Claude Desktop and enable the server from the tools menu in a chat.

The example uses Google Maps Business Lead Finder with Email & Social Links. Every Actor page and every website page below has the same config, pre-filled.

Good to know

  • Custom connectors work on the desktop app and claude.ai; Team and Enterprise owners add them under Organization settings.
  • claude_desktop_config.json only starts local servers. The local entry needs Node.js and keeps the token on your machine.
  • Apify also appears in Claude's connector directory; the custom URL lets you choose exactly which Actors are exposed.

Claude Desktop configs by website

Each page opens on the Claude Desktop tab.

When Claude Desktop does not connect

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Claude Desktop cannot start the local server. How do I fix it?

The local package needs Node.js 22 or newer. If it still fails with a connection error, clear the npx cache (rm -rf ~/.npm/_npx on macOS and Linux, the _npx folder under %LOCALAPPDATA%\npm-cache on Windows) or use the custom connector instead, which needs no local install.

Source: Apify documentation: Claude Desktop

The Claude connector worked yesterday and now fails. What helps?

Remove the custom connector and add it again so the OAuth sign-in starts fresh. Connectors are reached from Anthropic's cloud, not from your computer, and the Free plan allows one custom connector.

Source: Claude help: custom connectors

My old config uses mcp.apify.com/sse and stopped working. Why?

Apify retired the SSE transport on 1 April 2026. Use https://mcp.apify.com with the streamable HTTP transport, as every config on this site does.

Source: Apify changelog: MCP improvements

Every fix in one place

Questions

Where is claude_desktop_config.json?

Open Claude Desktop settings, then Developer, then Edit config. The app opens the file in its folder for your operating system.

Why does the local config not use the URL?

The desktop config file starts local stdio servers. The Apify package runs locally with your token and the --tools flag takes the same owner/name list as the URL.

Sources