MCP Fly Deployer

🚀 MCP Fly Deployer

A configuration generation tool designed to deploy Model Context Protocol (MCP) servers to Fly.io. This tool automates the creation of Dockerfile, fly.toml configuration, and deployment scripts, suitable for MCP servers based on standard input-output (stdio).

This project integrates supergateway to enable MCP stdio servers to communicate via SSE (Server-Sent Events) or WebSocket, facilitating seamless deployment to Fly.io's infrastructure.

✨ Features

• 🚀 Automatically generate Fly.io deployment configurations.
• 🐳 Dynamically generate Dockerfiles based on the runtime.
• ⚙️ Customizable fly.toml configurations.
• 🔧 Support multiple runtimes:
  • Python
  • Node.js
  • Go
  • Custom binaries
• 🔑 Manage environment variables and secrets.
• 🌐 Configurable regions and deployment options.

🛠️ How It Works

The MCP Fly Deployer utilizes supergateway to:

• Convert stdio-based MCP servers into SSE or WebSocket services.
• Enable remote access and debugging features.
• Automatically manage JSON-RPC versioning.
• Handle package metadata transmission.

For detailed information about the underlying gateway technology, please refer to the supergateway documentation.

📋 Prerequisites

• Python 3.13 or higher.
• pip (Python package manager).
• Installed and configured Fly.io CLI.
• Node.js and npm (for supergateway functionality).

📦 Installation

1. Clone the repository:

git clone https://github.com/yourusername/mcp-fly-deployer.git
cd mcp-fly-deployer

2. Create and activate a virtual environment:

python -m venv .venv
source .venv/bin/activate  # On Unix/macOS
# Or on Windows
.venv\Scripts\activate

3. Install dependencies:

uv sync

💻 Usage Examples

Basic Usage

1. Start the MCP server:

python mcp_server_generator.py

This server will run on the default port 8000, using SSE (Server-Sent Events) for transmission.

Advanced Usage

2. Send a request to generate a deployment plan with the following parameters:

{
    "server_command": "node",              # Command to run the target stdio server
    "server_args": ["index.js"],           # Arguments for the server command
    "runtime": "node",                     # Runtime type ('python', 'node', 'go', 'binary')
    "runtime_version": "20",               # Specific runtime version
    "dependencies": [],                    # List of dependencies
    "environment_variables": {},           # Environment variables
    "region": "us-east-1",                 # Deployment region
    "fly_app_id": "your_fly_app_id"        # Fly application ID
}

📚 Documentation

Supported Runtimes

• Python: Use the python runtime.
• Node.js: Use the node runtime, specifying versions like 16, 18, etc.
• Go: Use the go runtime, specifying versions like 1.20, etc.
• Custom Binaries: Deploy custom-built binaries.

Regions

The following Fly.io regions are supported:

• us-east-1
• us-west-2
• eu-central-1

🤝 Development and Contribution

To contribute to the project, please refer to CONTRIBUTING.md.

Issue Reporting

Encountered an issue or have a question? Please submit an issue in Issues.