Flyers

Developer docs

Get Flyers into your tools

Flyers is built for the CLI and AI agents. Install it in one line, or paste an install block into Claude Code or Codex and let the agent wire it up.

Let your agent install it

Just copy and paste to Claude Code, Codex, or ChatGPT.

Read https://flyers.dev/install.txt and set up Flyers (CLI + MCP) for me.

Use Flyers in Claude (one-click connector)

In Claude.ai (web/desktop) or Claude Code: Settings → Connectors → Add custom connector, paste the URL below, then sign in with GitHub or Google. No install, no token to paste. Then just ask Claude to "make this HTML fly" and get a short link back.

https://mcp.flyers.dev/mcp

Available tools (15 flyers_*): publish HTML, list links, set access (password / expiry / offline), rename, delete, and move links, plus team and branded-domain management. Each tool is described in the steps below and at flyers.dev/install.txt.

1 · Install the CLI

One line, then log in to link your account:

npm install -g @flyers-dev/cli
flyers login

2 · Make it fly

After your agent writes the HTML, one command publishes it and returns a short link:

flyers make it fly proposal.html
# ✈ https://flyers.dev/ab12c

Custom address (Chinese / Japanese too)

Add as to choose a memorable code. Use lowercase letters, numbers and hyphens — or Chinese / Japanese characters, which show as-is in the address bar. Length is 3–40 characters (2+ when it contains CJK); reserved and look-alike impersonation terms are blocked automatically.

flyers make it fly proposal.html as artzy-q3-review
# ✈ https://flyers.dev/artzy-q3-review

flyers make it fly proposal.html as 招募活動
# ✈ https://flyers.dev/招募活動

3 · Local MCP (Claude Desktop / Code, via the CLI)

For the local stdio method (instead of the connector above): sign in with flyers login and the MCP reuses that token automatically — no token needed in the config. To set it explicitly (remote / CI), run flyers token and put it in FLYERS_TOKEN:

{
  "mcpServers": {
    "flyers": {
      "command": "npx",
      "args": ["-y", "@flyers-dev/mcp"]
    }
  }
}

4 · Let an agent install it

Paste this URL to Claude Code or Codex; it reads the page and sets everything up itself:

https://flyers.dev/install.txt

5 · Teams & shared links

Create a team to share links with others. A team can be just you, or invite members by email and they join when they sign in with it. Team Links are visible to and managed by every member; My Links stay private. The free plan includes one team; Pro lifts that. Target a team when publishing by name or id:

flyers team create "Acme"          # you become its owner
flyers team invite t_ab12 [email protected]
flyers team ls                     # ids of teams you're in

flyers make it fly deck.html team Acme   # → a Team Link
flyers assign ab12c --team Acme    # move an existing link in
flyers assign ab12c --personal     # move it back to My Links

6 · Branded domains

A team owner can claim one flyers.dev subdomain per team. Links published to it read as your-brand.flyers.dev/code and resolve only on that host.

flyers domain add Acme spot       # → spot.flyers.dev (owner only)
flyers domain ls Acme              # show this team's branded domain

flyers make it fly deck.html on spot.flyers.dev   # publish onto it
flyers assign ab12c --domain spot.flyers.dev      # move a link onto it

Troubleshooting (connector)

  • Tools not showing: remove and re-add the connector in Claude, then complete the GitHub/Google sign-in again.
  • Sign-in stuck: make sure pop-ups/redirects are not blocked; after the provider login you are returned to Claude automatically.
  • A link won't open: it may be password-protected, expired, or taken offline — ask Claude to "list my links".
  • Revoke access: remove the connector in Claude, or email us to revoke your token. Questions & support: [email protected]