Give an n8n AI Agent live web data

Attach an MCP Client Tool node to your AI Agent's tool input, paste Apify's MCP URL with the Actors in ?tools=, choose HTTP Streamable and a Bearer auth credential with your Apify token. The agent can then decide when to run each Actor.

Method

  1. Add an AI Agent node, then attach an MCP Client Tool node to its tool input.

    n8n AI Agent config for Google Maps Business Lead Finder with Email & Social LinksMCP Client Tool node

    Actor on Apify 
    https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/google-maps-business-lead-finder-with-email

  2. Paste the URL as the endpoint and choose HTTP Streamable as the transport.

  3. Choose Bearer auth and create a credential that holds your Apify token.

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

  • For fixed schedules, a plain workflow is cheaper and more predictable: every Actor page has an n8n workflow that calls the Actor directly.
  • The MCP Client Tool node lets you include or exclude individual tools after it connects.

n8n AI Agent configs by website

Each page opens on the n8n AI Agent tab.

When n8n AI Agent 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

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

MCP Client Tool or HTTP Request?

Use the MCP Client Tool when an AI Agent should choose the Actor and its input. Use the HTTP Request workflow when the input and schedule are fixed.

Sources