Skip to content

feat: add Fly.io plugin - #79

Open
aezell wants to merge 1 commit into
Factory-AI:masterfrom
aezell:feat/fly-plugin
Open

aezell wants to merge 1 commit into
Factory-AI:masterfrom
aezell:feat/fly-plugin

Conversation

@aezell

@aezell aezell commented Nov 3, 2026

Copy link
Copy Markdown

Adds the Fly.io plugin to the Factory marketplace. It provides Fly.io resource operations through the hosted Fly MCP server and skills for persistent Sprite development: remote tests, checkpoints, authenticated previews, verified patch export, and resuming a workspace.

The contribution includes the native plugin, its marketplace entry, the fly and brand skill links required by catalog CI, and a README entry. The package is version 1.0.1 from superfly/fly-droid-plugin.

The plugin uses browser OAuth at https://mcp.fly.io, contains no credentials, and runs no local MCP server. Live use requires Factory model access and a Fly.io account; Python 3 enables the confirmation hooks. Local deployments additionally use flyctl. Resource creation can incur Fly.io charges.

Validation:

  • Anonymous Git clone, package validation, and all 18 confirmation-hook tests passed.
  • Droid 1.2.0 installed the public Git package in a fresh project and connected to 75 Fly MCP tools using existing OAuth authentication.
  • The proposed catalog package installed in another fresh project and connected to the same tools. A read-only Droid smoke test loaded the fly skill and called get_fly_context successfully without changing resources.
  • Factory's skill-directory CI script passed locally; all 25 package files match the validated distribution.
  • Earlier live validation ran three tests in an existing Sprite, checked its authenticated preview, and exported a hash-verified patch. Known runtime limitations and the exact test scope are recorded in VALIDATION.md.

Reviewer walkthrough: install fly@factory-plugins from this PR's marketplace, complete Fly OAuth with droid mcp auth, then ask Droid to use the Fly skill to inspect the authorized context. The plugin guide includes prerequisites and example prompts. No credentials or access to our test resources are needed; reviewers use their own Factory and Fly accounts.

Generated by Codex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant