MCP connectors

What are MCP connectors?

MCP connectors are a new type of Actor input in Apify Console. They let you add an MCP server URL, authenticate once, and then assign that connector to one or more Actors.

The product page presents MCP connectors as a way to connect Apify Actors with MCP-enabled workflows and external tools. The examples shown on the page include connectors and Actors for chat-based assistants, data publishing, monitoring, and dashboard creation.

Key Features

• Add an MCP server URL in Apify Console, making the connector available as an Actor input.
• Authenticate once and reuse the connector across multiple Actors, reducing repeated setup for each workflow.
• Assign one connector to one or more Actors, so the same MCP connection can support different automations.
• Support workflows that send Actor output to MCP-compatible destinations such as Slack, Notion, or other tools shown in the examples.
• Fit into existing Apify Actor runs and scheduled workflows, since many listed examples describe export, API, scheduling, and monitoring use.

How to Use MCP connectors

Create an MCP connector in Apify Console, enter the MCP server URL, and complete authentication. After that, attach the connector to the Actor or Actors that should use it, then run the Actor and let it use the configured MCP connection.

Use Cases

• Connect an Apify Actor to a Telegram or Slack-based assistant that routes requests through an MCP server.
• Send scraped data into Notion, Sheets, or Airtable through an MCP-connected workflow.
• Publish results from an Apify run to another MCP-compatible platform without setting up separate credentials for every Actor.
• Build monitoring flows that scrape websites or reviews and then forward summaries or alerts to external tools.
• Let AI agents trigger ad hoc checks or post-process Actor results through an MCP server.

FAQ

What is an MCP connector in Apify? It is a new type of Actor input that connects an Actor to an MCP server.

Do I need to authenticate for every Actor separately? No. The page says you authenticate once and then assign the connector to one or more Actors.

Where do I add an MCP connector? In Apify Console.

What kind of workflows does it support? The page shows examples that connect Apify Actors with chat assistants, dashboards, alerts, and data publishing workflows, but it does not list a fixed set of supported apps.

Alternatives

• Direct API integration: connect an Actor to a destination service by calling its API directly, which is more manual but does not require an MCP layer.
• Webhook-based automation: send Actor results into a downstream workflow system after the run finishes, rather than assigning a reusable MCP connector.
• Custom orchestration code: build a script or service that coordinates Apify with other tools, which gives more control but requires more setup.
• Individual app connectors: use a platform-specific integration for one destination at a time instead of a shared MCP connector that can be reused across Actors.