# How to connect Fly to Hermes Agent (paste one key, 45 tools)

> Connect Fly to Hermes with ClawLink: paste your Fly key once and 45 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/fly

Most guides for giving Hermes Agent Fly access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Fly setup: pair once in the browser and your always-on Hermes agent can act on Fly for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to Fly.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Fly** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect fly  # connect Fly (browser OAuth)
npx -y @useclawlink/cli actions fly  # list available actions
npx -y @useclawlink/cli run fly <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect Fly in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fly API key once.

Verify the connection by asking Hermes:

> Use Fly to check app name availability and walk me through the result in plain English.

### Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Fly is connected in the dashboard, that agent calls the same 45 Fly tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Fly MCP for Hermes

Looking for a Fly MCP server for Hermes Agent? ClawLink connects Fly to Hermes Agent and exposes 45 Fly tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Fly integration](https://claw-link.dev/openclaw/fly) works the same way.

## What the Hermes Agent Fly integration can do

45 Fly tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 45.

### 30 of 45 Fly tools for Hermes

| Tool | What it does |
|---|---|
| **Check app name availability** `fly_check_app_name_availability` | Validate an app name for Fly.io app creation |
| **Check jobs** `fly_check_jobs` | Execute GraphQL queries against the Fly.io checkJobs endpoint |
| **Check user only token** `fly_check_user_only_token` | Check whether the authentication token only allows user access |
| **Fetch nodes by IDS** `fly_fetch_nodes_by_ids` | Fetches a list of node objects from Fly.io given a list of IDs using the GraphQL nodes query |
| **Get add on** `fly_get_add_on` | Find a Fly.io add-on by ID, name, or provider |
| **Get add on provider** `fly_get_add_on_provider` | Query information about a specific Fly.io add-on provider (extension) by name |
| **Get app details** `fly_get_app_details` | Retrieve detailed information about a specific Fly.io application |
| **Get certificate** `fly_get_certificate` | Retrieve a certificate by its ID from Fly.io |
| **Get current token info** `fly_get_current_token_info` | Get information about the current authentication token |
| **Get latest image details** `fly_get_latest_image_details` | Retrieve the latest available tag details for a given image repository from Fly.io's registry |
| **Get latest image tag** `fly_get_latest_image_tag` | Retrieve the latest available image tag for a Fly.io Docker repository |
| **Get machine** `fly_get_machine` | Get a single machine by ID from Fly.io |
| **Get nearest region** `fly_get_nearest_region` | Retrieve the nearest Fly.io region to the requesting client based on network location |
| **Get node** `fly_get_node` | Fetch an object by its globally unique ID using Fly.io's GraphQL node query |
| **Get organization** `fly_get_organization` | Find a Fly.io organization by slug using the GraphQL API |
| **Get personal organization** `fly_get_personal_organization` | Retrieve the user's personal organization details from Fly.io |
| **Get placements** `fly_get_placements` | Get placement recommendations for Machines in Fly.io regions |
| **Get platform info** `fly_get_platform_info` | Retrieve Fly.io platform information including available regions, VM sizes, and flyctl version |
| **Get products** `fly_get_products` | Retrieve Fly.io product and price information via GraphQL |
| **Get regions** `fly_get_regions` | Get the list of available Fly.io regions with optional filtering |
| **Get viewer info** `fly_get_viewer_info` | Retrieve the authenticated user's account information from Fly.io |
| **List add on plans** `fly_list_add_on_plans` | List available add-on service plans from Fly.io |
| **List add ons** `fly_list_add_ons` | List add-ons associated with an organization in Fly.io |
| **List apps** `fly_list_apps` | List all Fly Apps in an organization |
| **List apps graphql** `fly_list_apps_graphql` | List all Fly.io applications with details including volumes, services, and VMs using GraphQL |
| **List check locations** `fly_list_check_locations` | Retrieve all available Fly.io health check locations |
| **List machines** `fly_list_machines` | List Fly.io machines using GraphQL API with pagination support |
| **List org machines** `fly_list_org_machines` | List all Machines across all apps in a Fly organization |
| **Validate config** `fly_validate_config` | Validate a Fly.io app configuration |
| **Validate wire guard peers** `fly_validate_wire_guard_peers` | Validate WireGuard peer IP addresses in a Fly.io organization |

## Example prompts

**Check App Name Availability**

> Use Fly to check app name availability and walk me through the result in plain English.

**Check Jobs**

> Use Fly to check jobs and walk me through the result in plain English.

**Check User Only Token**

> Use Fly to check user only token and walk me through the result in plain English.

**Fetch Nodes By Ids**

> Pull the relevant data from Fly, summarize it in plain English, and point out anything that needs attention.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Fly working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Fly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fly account becomes available to the agent without you building credential management. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Fly. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Fly actions to the runtime in a format your agent can reliably use. | 45 tools for Fly are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Fly to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Fly in the browser, and the 45 tools above work from chat. There is no SDK and no config file, and the Fly key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Fly
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### Connection succeeds but no tools appear
Reconnect Fly from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Fly tools
Fly tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Fly call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### Fly returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for Fly has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a Hermes Agent Fly integration?
Yes. ClawLink is the fastest way to connect Hermes to Fly: link your Fly account once in the browser and Hermes Agent can call the Fly API through 45 ready-made tools — no custom code or token handling.

### How do I connect Fly to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Fly in the dashboard and Hermes can use it from the next message — no config files, and the Fly key you paste is stored server-side instead of in your environment.

### How long does it take to connect Fly to Hermes Agent?
About two minutes. Sign in, click Connect next to Fly in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Fly up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Fly working from chat.

### Hermes paired but still can't use Fly
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [Hermes GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows
- [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services
- [Connect SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.