Apify: MCP connectors - Apify's built-in credential layer for third-party tools

MCP connectors are live. Actors now work where you do. Apify Actors are built for the open web. But workflows that need authenticated access to Notion, Slack, or GitHub had to run outside Apify. MCP connectors change that. Assign a connector to an Actor, and it can read and write to your external apps through a secure proxy in a single run - without ever seeing your credentials.

Apify is already the largest marketplace of tools for AI with 30,000 Actors ready to us off the shelf... And it will get even better.

Apify is releasing MCP connector: MCP Connectors is Apify's built-in credential layer for third-party tools. Users authorize their accounts once (Notion, Slack, etc.) in Settings → Integrations. Those connections are then available as inputs to any compatible Actor : no token-sharing, no developer access to credentials, no OAuth app registration required.

If you haven't tried to build something with Apify, it is the perfect time to join.

You can learn more about how MCP connectors work here: https://blog.apify.com/announcing-mcp-connectors/
You can also check Actors embedding MCP connectors here: https://apify.com/store/collections/mcp-connectors

Apify: MCP connectors - Apify's built-in credential layer for third-party tools

Replies