I shipped 7 production MCP server Actors in two weeks — here's what the docs don't tell you

I shipped 7 production MCP server Actors in two weeks — here's what the docs don't tell you

The first Actor took most of a day. The seventh took under two hours. The delta wasn't clever abstractions or a better framework. It was the institutional knowledge that accumulates after you've hit every silent failure mode that Apify's documentation doesn't mention.

This post covers the patterns that mattered. All of it works whether you buy anything at the end or not.

The stack: what "MCP Actor on Apify" actually means

Apify's Standby mode lets you run a persistent Python process that accepts HTTP connections. Combine that with FastMCP and you get an MCP server at a stable public URL, billed per tool call rather than per minute. The Standby URL format is: