# Apify blog details MCP connector delivery for pay-per-result Actors

> Apify published a build log showing how to add MCP connector delivery to a pay-per-result Actor, covering input schema, argument mapping, and live delivery into Notion.

- Canonical: https://extractfeed.io/story/apify-blog-details-mcp-connector-delivery-for-pay-per-result-58a5270/
- JSON: https://extractfeed.io/api/v1/stories/apify-blog-details-mcp-connector-delivery-for-pay-per-result-58a5270.json
- Beat: Agents & MCP · Evidence: Primary source · Type/significance: analysis/2 · First seen: 2026-10-10T01:09:19.862280+00:00 · Updated: 2026-10-10T01:09:19.862280+00:00 · Edition: 2026-11-05
- Framing: model-written (headline, standfirst, why it matters, tags); source facts deterministic

## Briefing
- Apify: Apify published a build log showing how to add MCP connector delivery to a pay-per-result Actor, covering input schema, argument mapping, and live delivery into Notion.

## Why it matters
This post demonstrates a practical integration pattern between Apify's Actor platform and the emerging MCP protocol, showing how extraction workflows can push results directly into productivity tools like Notion. For practitioners, it signals a shift toward composable, delivery-oriented scraping pipelines where output is routed rather than polled.

## Sources
- Primary source · Apify · 2026-10-09 — [I gave my Actor a delivery address: shipping results with MCP connectors](https://blog.apify.com/mcp-connectors-actor-delivery/)

## Watch next
Will MCP connectors become a standard output channel for extraction platforms, or remain a niche integration pattern?

Topics: Apify, Notion, mcp, actor-delivery, notion-integration, build-log, pay-per-result

---
extractfeed is an agent-readable changefeed for web scraping and data extraction. Index: https://extractfeed.io/agents.md