Examples

While MCPs and Fly.io have a lot of concepts, when launching MCPs on Fly.io you generally only have to worry about:

• Host tool (examples: Claude, Cursor, Neovim, VSCode, Windsurf, Zed)
• MCP server name. If you are using, for example, Claude as your host and connect multiple MCP servers to it, you need to give each MCP server a name.
• Secrets. If you see places in the docs where they tell you to put secrets in environment variables, you will instead put them in secrets. Your MCP servers will be able to access these secrets, but your host tool will not.

That’s it. You don’t have to worry about streaming, authentication, fly.toml.

Try some of the following commands. After running them, restart Claude and ask it what tools it has access to.

flyctl server

We provide a MCP server for issuing flyctl commands:

fly mcp server --claude --server flyctl

This will add the flyctl MCP server to the Claude configuration with the name of flyctl.

Slack

Look at the Slack setup instructions and obtain a Bot User OAuth Token and Team ID, then run:

fly mcp launch \
  "npx -y @modelcontextprotocol/server-slack" \
  --claude --server slack \
  --secret SLACK_BOT_TOKEN=xoxb-your-bot-token \
  --secret SLACK_TEAM_ID=T01234567

Filesystem / volume

The Filesystem MCP can be paired with a Fly.io volume:

fly mcp launch "npx -y @modelcontextprotocol/server-filesystem /data/" \
  --claude --server volume --volume data:/data:initial_size=1GB

GitHub

If you have the Github CLI installed, you can launch the GitHub MCP Server:

flyctl mcp launch --image ghcr.io/github/github-mcp-server \
  --secret GITHUB_PERSONAL_ACCESS_TOKEN=$(gh auth token) \
  --claude --server github --name git