MCP.so
ログイン

MCP Fly Deployer

@NakulRajan

MCP Fly Deployer について

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

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

python

トランスポート

stdio

公開者

NakulRajan

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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).

コメント

「その他」の他のコンテンツ