MCP Fly Deployer

Name: MCP Fly Deployer
Author: NakulRajan

@NakulRajan

Repository

About MCP Fly Deployer

MCP server that provides docker files for stdio based MCP server to be deployed on platform like Fly.IO

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-fly-deployer": {
      "command": "python",
      "args": [
        "-m",
        "venv",
        ".venv"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Fly Deployer?

MCP Fly Deployer is a configuration generator that automates Dockerfiles, fly.toml files, and deployment scripts for deploying stdio-based Model Context Protocol (MCP) servers to Fly.io. It integrates supergateway to convert stdio MCP servers into SSE or WebSocket services for remote access.

How to use MCP Fly Deployer?

Clone the repository, create and activate a Python virtual environment, and install dependencies with uv sync. Start the server by running python mcp_server_generator.py (listens on port 8000 via SSE transport), then send a request with parameters such as server_command, server_args, runtime, runtime_version, and optional settings like target_port, app_name, and primary_region.

Key features of MCP Fly Deployer

Automated Fly.io deployment configuration generation
Dynamic Dockerfile generation based on runtime
Customizable fly.toml configuration
Support for Python, Node.js, Go, and custom binaries
Environment variables and secrets management
Configurable regions and deployment options

Use cases of MCP Fly Deployer

Deploy a Node.js MCP server to Fly.io with automatic Dockerfile creation
Deploy a Python MCP server with a specified requirements.txt
Deploy a Go MCP server or a custom binary as a Fly.io app
Generate deployment plans for multiple MCP servers with different runtimes

FAQ from MCP Fly Deployer

What are the prerequisites for using MCP Fly Deployer?

Python 3.13 or higher, pip, the Fly.io CLI installed and configured, and Node.js with npm (for supergateway functionality).

How does MCP Fly Deployer convert stdio to SSE/WebSocket?

It uses supergateway to convert stdio-based MCP servers into SSE or WebSocket services, handle JSON-RPC versioning automatically, and manage package metadata transmission.

What runtimes are supported?

Python, Node.js, Go, and custom binary (binary). Runtime versions can be specified (e.g., Node.js 20).

What is the default transport and port?

The server uses SSE transport and listens on port 8000 by default.

Can I specify a deployment region?

Yes, use the primary_region parameter. Common regions include ord (Chicago), iad (Northern Virginia), dfw (Dallas), lax (Los Angeles), and bom (Mumbai).