The Daemon Moves Out: Why MCP Was the Wrong Home for the Pipeline
Five months after the manual-to-MCP pivot, I noticed the MCP server was doing two different jobs. One was a tool surface for an agent — the task for which I'd designed and built the MCP server. The other was the hosting environment for the daemon itself: long-running, stateful, with a job queue and a state machine that wanted to live longer than any single Claude Desktop session. For most of those five months, the two jobs sharing one process was fine. Then it wasn't. ...