MCP connectors are live! Actors now work where you do🔌 Actors were once limited to the open web. With connectors, they now securely connect to apps like @NotionHQ, @SlackHQ, @GitHub, or any MCP server, access business data, send results, and integrate with external workflows.

Since there's no official @aidotengineer world's fair SF afterparty, @apify, @joinmassive, and @topk_io are joining forces to host an unofficial one on Thursday, 2nd July in South Park luma.com/aie-sf-afterparty

If you're at WORLDEF, find the Apify team at booth A83-84. E-commerce is one of the strongest use cases on the platform: pricing, product, review, and seller data without a data team behind it. Come say hi 👋

100 public Actors, 1.7K users, >99% run success rate. @maximehugodupre has been building on Apify, and the numbers speak for themselves 👏

Competitor ad research across Google, LinkedIn, and Meta - compiled into a dashboard inside @boltdotnew, no code needed. Full tutorial below 👇

The new @apify's MCP connectors might sound like a nice little feature, but it’s our most important launch of the year. Apify Actors were always supposed to “act”. But until now, most Actors only passively fetched data from the open web, which served as input to workflows and actions running elsewhere. It was easier to do it this way. That changes today. Actors can now securely connect to external apps via the Model Context Protocol (MCP) to access your business data, send results, or integrate with external workflows. MCP is supported by a rapidly growing ecosystem of services, so this opens up a lot of exciting opportunities for what Actors can do. Now there are 37k - with MCP connectors, I believe there will be 100k . To test this new feature, over the past week I rewrote our `apify/ai-code-sandbox` Actor. In this demo, I give this Actor access to Apify’s Notion, launch Claude Code inside the sandbox, and have it solve some tasks. It’s not hard to imagine cool agentic Actors that could be built on top of this.