Fly Io

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/pulsemcp-com-fly-io

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

9 read · 9 write · 2 delete · 3 not yet classified

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (23)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• check_fly_registry_image

  Check if an image exists in Fly.io's private registry (registry.fly.io). Verifies whether a specific image tag exists in the Fly.io registry. Use this to confirm an image is available before creating or updating Fly machines to use it. **Fly Registry:** - Images are stored at registry.fly.io/<app_name>:<tag> - Only accessible by your Fly.io account - Automatically authenticated via your Fly API token **Parameters:** - app_name: Fly app name (the image repository) - tag: Image tag to check **Returns:** - Whether the image exists in the registry - Full image reference if it exists (for use w…

• create_app

  Create a new Fly.io application. Creates an empty app that can then have machines deployed to it. **Returns:** - Created app ID and name - Organization info - Initial status **Use cases:** - Set up a new application before deploying machines - Create apps in specific organizations - Initialize app with custom network settings **Note:** App names must be globally unique across all of Fly.io.

• create_machine

  Create a new machine (VM) in a Fly.io application. Deploys a Docker image as a new machine with specified configuration. **Returns:** - Created machine ID and name - State (started or stopped) - Region and IP - Applied configuration **Use cases:** - Deploy new instances of an application - Scale out by adding more machines - Create machines with specific resource configurations **Examples:** - Basic: image="nginx:latest" - With resources: image="myapp:v1", cpus=2, memory_mb=512 - With env vars: image="myapp:v1", env={"DATABASE_URL": "..."}

• delete_app

  Delete a Fly.io application. Permanently deletes an app and all associated resources. **Warning:** This action is irreversible. All machines, volumes, and data will be lost. **Returns:** - Confirmation of deletion **Use cases:** - Clean up unused applications - Remove test or development apps - Free up app name for reuse **Note:** Use force=true to delete apps with running machines.

• delete_machine

  Delete a machine from a Fly.io application. Permanently removes a machine and all its data. **Warning:** This action is irreversible. All data on the machine will be lost. **Returns:** - Confirmation of deletion **Use cases:** - Remove unused machines - Scale down by removing instances - Clean up failed deployments **Note:** Use force=true to delete running machines. Otherwise, stop the machine first.

• get_app

  Get details for a specific Fly.io application. Returns detailed information about an app including its status, organization, and configuration. **Returns:** - App ID and name - Current status - Organization details - Network configuration **Use cases:** - Check the status of a specific app - Get app details before deploying machines - Verify app configuration

• get_logs

  Get logs for an app or specific machine. Retrieves recent logs from Fly.io machines. Can filter by region or specific machine. **Returns:** - Log output from the app's machines **Use cases:** - Debug application errors - Monitor app behavior - Check deployment status - Investigate crashes

• get_machine

  Get details for a specific machine in a Fly.io application. Returns detailed information about a machine including its configuration. **Returns:** - Machine ID and name - Current state - Region and private IP - Full configuration (image, env vars, resources) - Created and updated timestamps **Use cases:** - Check detailed machine configuration - Debug machine issues - Verify machine settings before updates

• get_machine_events

  Get recent events for a machine. Retrieves the event log for a machine, showing state transitions, errors, and other lifecycle events. This is useful for debugging and monitoring machine behavior. **Returns:** - List of events with type, status, source, and timestamp - Exit event details when applicable (exit codes, signals, OOM status) **Use cases:** - Debug why a machine crashed or stopped - Monitor machine lifecycle events - Check for OOM (out of memory) kills - Verify successful deployments

• list_apps

  List all Fly.io applications you have access to. Returns a list of apps with their names, IDs, status, and organization info. **Returns:** - App name and ID - Current status (deployed, suspended, etc.) - Organization name and slug - Machine count **Use cases:** - Get an overview of all your deployed applications - Find an app name for use with other tools - Check app statuses across organizations

• list_machines

  List all machines in a Fly.io application. Returns all machines (VMs) running in the specified app. **Returns:** - Machine ID and name - Current state (started, stopped, etc.) - Region - Image being used - Private IP address **Use cases:** - See all running instances of an app - Check machine states - Get machine IDs for other operations

• list_releases

  List releases for a Fly.io application with their Docker image references. Returns a list of releases showing deployment history and image versions. **Returns:** - Release version and ID - Status (stable, in-progress) - Description and reason - User who created the release - Docker image reference for each release - Creation timestamp **Use cases:** - View deployment history - Track image versions across releases - Debug deployment issues - Identify who deployed what

• machine_exec

  Execute a command on a machine. Runs a command on a specific Fly.io machine and returns the output. This is equivalent to "fly machine exec". **Returns:** - The command output (stdout) **Use cases:** - Run diagnostic commands - Check file contents - Execute maintenance scripts - Debug application issues - Inspect running processes

• pull_fly_registry_image

  Pull an image from Fly.io's private registry (registry.fly.io) to local Docker. Downloads an image that was previously pushed to the Fly.io registry to your local Docker daemon. This is useful for inspecting images currently running on Fly machines or debugging deployments. **Fly Registry:** - Images are stored at registry.fly.io/<app_name>:<tag> - Only accessible by your Fly.io account - Automatically authenticated via your Fly API token **Parameters:** - app_name: Fly app name (the image repository) - tag: Image tag to pull **Returns:** - Confirmation of successful pull - Full image refe…

• push_new_fly_registry_image

  Push a local Docker image to Fly.io's private registry (registry.fly.io). This tool uploads a Docker image from your local machine to Fly.io's registry, making it available to run on Fly machines. After pushing, you can use the image reference with create_machine or update_machine to deploy containers. **Fly Registry:** - Images are stored at registry.fly.io/<app_name>:<tag> - Only accessible by your Fly.io account - Automatically authenticated via your Fly API token **Parameters:** - source_image: Local Docker image to push (must exist in local Docker) - app_name: Fly app name (determines …

Signals

Stars

81

Forks

10

Open issues

26

Contributors

4

Last commit (this folder)

Jun 14, 2026 (4 months ago)

Last release

Jun 17, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

com.pulsemcp/fly-io

Version

0.1.7

Auth

API key

Packages

npm fly-io-mcp-server

License

MIT

Repository

github.com/pulsemcp/mcp-servers

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql