Launching MCP Servers on Fly.io

Source: fly.io Date: 2025-06-09 URL: https://fly.io/blog/mcp-launch/

Summary

Release announcement for fly mcp launch, a command that deploys MCP servers to Fly.io with a single command including secret injection (--secret SLACK_BOT_TOKEN=...), client configuration (--claude, --server slack), and remote process management. The post is part announcement, part critique of the MCP ecosystem’s current friction (manual JSON editing across tools, local security surface, OAuth complexity) and positions Fly as solving all three.

Implications

MCP integration thread. fly mcp launch is the productized version of the earlier flyctl MCP prototype — it’s the moment the pattern moves from “rough in” to “ships with docs.” The three problems named (config fragmentation, local security, OAuth) are real and Fly’s remote execution model (MCP server runs in a Fly Machine, not on your laptop) directly addresses the security surface issue. This creates a meaningful wedge against running MCP servers locally: remote MCP via Fly is more auditable, more scalable, and doesn’t expose your local machine’s filesystem to a model’s tool calls. This is an early form of “trusted MCP execution environment” — a category that will matter as agentic workloads become sensitive.