The gate is at the action, not the access — a sandboxed agent, an MCP bridge, and a beta opt-in that opens from the inside.
Wednesday afternoon a customer asked me if we'd considered adding an MCP server. By Thursday night he was using it and called it flawless. The speed of deployment is crazy cool once you remove the two humans involved — but it's not the story. Not that we sent out a feature release itself, but the how.
We released an opt-in beta to the entire customer base. His agent watched the broadcast. He curl'd the opt-in himself. The architecture turned out different than I expected.
The ask
Jeff DeVerter — first paying customer at AgenticBoxes.email — filed the FR Thursday morning (9:26am CT / 14:26 UTC). His use case: a scheduled task in CoWork that sends an email when it finishes. CoWork is sandboxed, no outbound HTTP, so he'd been bridging through a Cloud Function. He wanted a native MCP server.
