You can put an app on FlyNode without opening the dashboard to click through a wizard. Pick the line that describes you. The links go straight to the right guide for your stack.
| I want to… | Easiest way |
|---|---|
| Deploy an app by talking to Claude | Connect Claude to FlyNode (one address, nothing to install) |
| Deploy from my terminal | The flynode command |
| Deploy on every push to GitHub | GitHub Actions |
| Deploy any app from a GitHub repository | Deploy a GitHub Repository |
| Deploy from a private repository | Deploy a Private Repository |
| Deploy a repo that comes with its own database (Docker Compose) | Deploy a Docker Compose App and Its Database |
| Add a database to my app | Add a Database to Your App |
| Migrate a MERN app (MongoDB, Express, React, Node) | Migrate a MERN Stack App to FlyNode |
| Migrate a Next.js app with Postgres | Migrate a Next.js App and Its Postgres Database |
| Migrate a Laravel app with MySQL | Migrate a Laravel App and Its MySQL Database |
| Move any other site or stack | Move your site to FlyNode |
Connect Claude to FlyNode (apps)
This is the quickest way for an app. You add FlyNode to Claude once, sign in, and then say "deploy this". There is nothing to install and no token to copy.
Before you start
- A FlyNode account with an active Cloud Workspace.
- Your project on GitHub and pushed. FlyNode builds from the repository, not from the files on your computer. If it is not on GitHub yet, in your project folder run:
git init
git add .
git commit -m "First commit"
gh repo create my-app --private --source . --push
gh is the GitHub command line tool (cli.github.com, then gh auth login once). Do not commit .env files. A public repository works straight away; a private one needs a deploy key first, see Deploy a Private Repository. Your app must listen on the port in the PORT variable and answer on /.
Add FlyNode in claude.ai or Claude Desktop
- In Claude open Settings > Connectors and choose Add custom connector. (On Team and Enterprise plans an organization owner may need to add it first.)
- Name:
FlyNode - Remote MCP server URL:
https://mcp.flynode.io/mcp - Leave the Advanced settings empty and click Add, then Connect.
- A FlyNode page opens. Sign in if asked. Check the app name, choose what Claude may do (Deploy is right for most people, Read only lets it look but not change), optionally limit it to one Workspace, and click Approve.
- Back in Claude, start a new chat and say, for example: Deploy https://github.com/you/your-repo to FlyNode as my-app.
The first time Claude uses a FlyNode tool it asks you to allow it. Choose allow. Claude then creates the app, adds any database you asked for, starts the build, waits for it, checks the address and gives you the link. If the build fails it reads the log, tells you what is wrong and, for your own repository, can suggest the fix.
Add FlyNode in Claude Code
claude mcp add --transport http flynode https://mcp.flynode.io/mcp
Then start Claude Code, type /mcp, choose flynode and follow the sign-in in your browser (the same approve page). Add --scope user after claude mcp add to have it in every project. In your project folder say: deploy this to FlyNode. Claude Code can also push your code to GitHub for you first.
What Claude can and cannot do
- It can create and redeploy apps, read status and logs, add a database or a custom domain, set variables, and roll back to an earlier version.
- It can never read the value of a variable or a database password, change billing, manage your account or team, or delete an app. To delete, use the dashboard.
Secrets: never paste them into the chat
If your app needs API keys or passwords, tell Claude: my app needs secret variables. Claude gives you a private link that works once and expires in 15 minutes. Open it, paste your .env content on the FlyNode page, and save. The values go straight to FlyNode and never pass through the conversation.
Disconnect
In FlyNode open Settings > API tokens > Connected apps and press Disconnect. Claude loses access at once.
Deploy from your terminal
For people who like commands. It needs Node.js 20 or newer (node -v).
- Install:
npm install -g @flynode/mcp(this gives you theflynodecommand; check withflynode help). - Sign in:
flynode login. The terminal prints a link and a short code such asG2KA-8D3Rand opens your browser. Check that the code on the page matches, choose Deploy and press Approve. The terminal saysSigned in as you@example.com. (Or use a token from Settings > API tokens:flynode login --token fn_live_xxx.) - In your project folder, with the code pushed to GitHub:
flynode deploy. It creates the app, builds it and printsLive: https://.... Add--db postgresql(or mysql, mariadb, mongodb, redis) for a database,--env-file .env.productionto send variables,--branch namefor another branch, and--post-deploy "php artisan migrate --force"to run a command (for example a Laravel migration) after every successful deploy.
| Command | What it does |
|---|---|
flynode status | State, address, a live check, last deploys. |
flynode logs -f | Follow what the app prints (--build for the build log). |
flynode env push .env.production | Send variables from a local file and redeploy. flynode env list shows names only. |
flynode redeploy / flynode rollback <commit> | Rebuild, or put an earlier version back. |
flynode open, flynode apps, flynode logout | Open the app, list apps, forget the saved token. |
The first deploy writes a .flynode.json file. Commit it so teammates and CI deploy to the same app.
Deploy on every push (GitHub Actions)
- Do one deploy from your computer first, so
.flynode.jsonexists, and commit it. - In FlyNode create a token: Settings > API tokens, name it, choose Deploy, create, and copy it (shown once).
- In your GitHub repository open Settings > Secrets and variables > Actions > New repository secret, name it
FLYNODE_TOKENand paste the token. - Add
.github/workflows/deploy.yml:
name: Deploy to FlyNode
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
- run: npx -y -p @flynode/mcp flynode deploy --branch main
env:
FLYNODE_TOKEN: ${{ secrets.FLYNODE_TOKEN }}
Advanced: Claude with a token and your own files
The connector above cannot read files on your computer. If you want Claude Code to send a local .env file directly, use the local server instead: create a token in Settings > API tokens and run
claude mcp add flynode --env FLYNODE_TOKEN=fn_live_xxx -- npx -y @flynode/mcp
For Claude Desktop, put the same server in claude_desktop_config.json (Settings > Developer > Edit Config):
{
"mcpServers": {
"flynode": {
"command": "npx",
"args": ["-y", "@flynode/mcp"],
"env": { "FLYNODE_TOKEN": "fn_live_xxx" }
}
}
}
A token can do the same as the connector, plus delete apps if you create it with Full access. It can never read variable values or passwords. Treat it like a password: revoke it in Settings if it leaks.
Troubleshooting
| You see | Do this |
|---|---|
| Claude says it cannot reach the server, or the sign-in fails | Check the address is exactly https://mcp.flynode.io/mcp. Remove the connector, add it again, and approve once more. You can also press Disconnect in FlyNode Settings first. |
| The approve page says the request expired | Go back to Claude and press Connect again. The page is valid for 15 minutes. |
| Build fails | Ask Claude to read the build log. Common causes: no start script, or the app does not listen on the PORT variable. |
| App deploys but shows an empty page or 502 | Make the app listen on process.env.PORT and on 0.0.0.0. |
This folder has no Git remote (command line) | Put the project on GitHub (see Before you start). |
Could not find remote branch | Push the branch, or name the right one (older repositories use master). |
Good to know
- Databases you ask for are created and connected for you; their connection variables are added to the app automatically.
- Your plan limits (apps, memory) apply exactly as in the dashboard.
- Everything Claude or a token does is recorded in your activity log.
Still stuck?
Open a support ticket from your dashboard and include the container name.