Fly Io MCP server
{
"mcpServers": {
"pulsemcp-fly-io": {
"command": "npx",
"args": [
"-y",
"fly-io-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-fly-io": {
"command": "npx",
"args": [
"-y",
"fly-io-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-fly-io": {
"command": "npx",
"args": [
"-y",
"fly-io-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"servers": {
"pulsemcp-fly-io": {
"command": "npx",
"args": [
"-y",
"fly-io-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "${input:agent_orchestrator_base_url}",
"FLY_IO_API_TOKEN": "${input:fly_io_api_token}"
}
}
},
"inputs": [
{
"id": "agent_orchestrator_base_url",
"type": "promptString",
"description": "Agent orchestrator base url",
"password": true
},
{
"id": "fly_io_api_token",
"type": "promptString",
"description": "Fly io api token",
"password": true
}
]
}{
"mcpServers": {
"pulsemcp-fly-io": {
"command": "npx",
"args": [
"-y",
"fly-io-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y fly-io-mcp-serverversion 0.1.7
What it does
This MCP server provides access to Fly.io infrastructure management, allowing you to interact with machines, applications, logs, and Docker images through MCP tools. It is for developers who want to manage their Fly.io deployments programmatically from MCP clients.
- Deploy, start, stop, or manage Fly.io machines and applications without leaving your MCP client.
- Access and inspect application logs from Fly.io deployments for debugging and monitoring.
- Work with Docker images associated with Fly.io apps as part of your deployment workflow.
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.