Give Cursor live web data

Save an mcp.json with an mcpServers entry whose url is Apify's MCP URL and whose Authorization header is Bearer ${env:APIFY_TOKEN}. Use ~/.cursor/mcp.json for every project or .cursor/mcp.json for one, then check the server in Cursor Settings, MCP.

One click, signs in with Apify on first use:

Add to Cursor

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/google-maps-business-lead-finder-with-email" --name google-maps-business-lead-finder-with-email

Method

  1. Save as ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Merge with servers you already have.

    Cursor config for Google Maps Business Lead Finder with Email & Social Links~/.cursor/mcp.json

    Actor on Apify 
    {
  "mcpServers": {
    "google-maps-business-lead-finder-with-email": {
      "url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/google-maps-business-lead-finder-with-email",
      "headers": {
        "Authorization": "Bearer ${env:APIFY_TOKEN}"
      }
    }
  }
}

  2. Set APIFY_TOKEN in the environment Cursor starts from, or replace ${env:APIFY_TOKEN} with your token.

  3. Open Cursor Settings, then MCP, and check that the server lists its tools.

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.

Apify plugin or a scoped URL?

Apify recommends its own plugin for Cursor: one install adds the whole Apify MCP server and five Agent Skills, with a sign-in in your browser. The config above is the other route: a URL scoped to the Actors you pick, so Cursor sees only their tools, which keeps the tool list short and the context small. Use the plugin to explore Apify; use a scoped URL when the agent should do one job with known Actors.

  1. In the Cursor agent chat, run the command below (or search for Apify under Plugins in Cursor Settings).
  2. In Cursor Settings, open Tools & MCPs, select Connect on the Apify MCP server and finish the sign-in.
/add-plugin apify

From Apify's plugin documentation and Apify's Cursor guide, checked 2026-11-12. With the Apify CLI, apify mcp install cursor (or another client name) writes the MCP config for you.

Good to know

  • Cursor's remote server entries use url and headers with no type field.
  • ${env:NAME} reads an environment variable, so the token never sits in the file.
  • Cursor also supports OAuth sign-in for remote servers.

Cursor configs by website

Each page opens on the Cursor tab.

When Cursor 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

Cursor does not show the server's tools. What should I check?

Open the Output panel and pick MCP Logs to see the connection error. A deeplink install that does nothing usually means an older Cursor build; update it or paste the JSON into mcp.json by hand.

Source: Cursor MCP documentation

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

Global or project config?

~/.cursor/mcp.json applies everywhere; .cursor/mcp.json in a repository applies to that project and can be shared without the token.

The tools do not appear. What should I check?

Check that the JSON is valid, that APIFY_TOKEN is set in the environment Cursor was started from, and that the server is enabled in Settings, MCP.