Why we built MCP-first hosting
Deploys, logs, env vars, and rollback should be callable from the same place the code is being changed. That is the practical reason Percher is built around MCP.
Blog
Notes on deploys, MCP tooling, recovery contracts, performance fixes, and the trade-offs we hit while building Percher. Subscribe via RSS.
The agent recovery contract
Percher errors include a typed nextAction so assistants can recover from deploy failures without parsing prose or guessing the next tool call.
Self-hosting fonts fixed a 7-second first paint
A Percher app had fast server responses but a blank page for seven seconds. The culprit was a blocked Google Fonts request, not the app server.