How to integrate Fly MCP with Claude Code

Manage your Fly directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Fly logoFly
Api KeyOauth2

Fly.io transforms containers into micro-VMs running globally. Instantly deploy apps close to your users for low latency and high availability.

45 Tools

Introduction

Manage your Fly directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Fly with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Fly to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Fly MCP server, and what's possible with it?

The Fly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fly account. It provides structured and secure access so your agent can perform Fly operations on your behalf.

Connecting Fly via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Fly) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Fly account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['fly'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http fly-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Fly. This URL will be used to connect Claude Code to Fly.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Fly
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Fly MCP to Claude Code

bash
claude mcp add --transport http fly-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (fly-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Fly MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your fly-composio entry in the list
  • This confirms that Claude Code can now access Fly tools

If everything is wired up, you should see your fly-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Fly

The first time you try to use Fly tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Fly
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Fly authorization flow
  • Return to the terminal and start using Fly through Claude Code

Once authenticated, you can ask Claude Code to perform Fly operations in natural language. For example:

  • "Deploy latest image to Fly in Tokyo"
  • "List all running Fly apps by region"
  • "Scale up my Fly app to 3 instances"

Complete Code

Here's the complete code to get you started with Fly and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['fly'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http fly-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Fly with Claude Code using Composio's MCP server. Now you can interact with Fly directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Fly operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Fly operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Fly action and event your agent gets out of the box.

Add WireGuard Peer

Tool to add a WireGuard peer connection to a Fly.

Check App Name Availability

Tool to validate an app name for Fly.

Check Jobs

Execute GraphQL queries against the Fly.

Check User Only Token

Check whether the authentication token only allows user access.

Create Health Check Job

Tool to create a health check job for monitoring application endpoints in Fly.

Create Check Job Run

Triggers a run of an existing health check job on Fly.

Create Delegated WireGuard Token

Tool to create a delegated WireGuard token for peer management in a Fly.

Create Third-Party Configuration

Tool to create a third-party service configuration for discharging macaroon caveats.

Delete Delegated WireGuard Token

Tool to delete a delegated WireGuard token from a Fly.

Delete Organization

Tool to delete a Fly.

Delete Remote Builder

Tool to delete a remote builder configuration for a Fly.

Delete Third Party Configuration

Tool to delete a third-party service configuration from Fly.

Detach Postgres Cluster

Tool to detach a Postgres cluster from a Fly.

Establish SSH Key

Tool to establish an SSH key for a Fly.

Fetch Nodes by IDs

Fetches a list of node objects from Fly.

Get Add-On

Tool to find a Fly.

Get Add-On Provider

Tool to query information about a specific Fly.

Get app details

Tool to retrieve detailed information about a specific Fly.

Get Certificate

Tool to retrieve a certificate by its ID from Fly.

Get Current Token Info

Tool to get information about the current authentication token.

Get Latest Image Details

Tool to retrieve the latest available tag details for a given image repository from Fly.

Get Latest Image Tag

Tool to retrieve the latest available image tag for a Fly.

Get Machine

Tool to get a single machine by ID from Fly.

Get Nearest Region

Tool to retrieve the nearest Fly.

Get Node by ID

Tool to fetch an object by its globally unique ID using Fly.

Get Organization

Tool to find a Fly.

Get Personal Organization

Tool to retrieve the user's personal organization details from Fly.

Get Placements

Tool to get placement recommendations for Machines in Fly.

Get Platform Information

Tool to retrieve Fly.

Get Products and Pricing

Tool to retrieve Fly.

Get Regions

Tool to get the list of available Fly.

Get Viewer Info

Tool to retrieve the authenticated user's account information from Fly.

Issue Certificate

Tool to issue an SSH certificate for accessing Fly.

List Add-On Plans

Tool to list available add-on service plans from Fly.

List Add-Ons

Tool to list add-ons associated with an organization in Fly.

List Apps

Tool to list all Fly Apps in an organization.

List Apps via GraphQL

List all Fly.

Check Locations

Retrieve all available Fly.

List Machines

Tool to list Fly.

List Organization Machines

Tool to list all Machines across all apps in a Fly organization.

Remove WireGuard Peer

Tool to remove a WireGuard peer connection from a Fly.

Set Apps V2 Default

Tool to configure whether new apps in an organization use Apps V2 by default on Fly.

Update Third-Party Configuration

Tool to update an existing third-party service configuration for discharging macaroon caveats.

Validate Config

Tool to validate a Fly.

Validate WireGuard Peers

Tool to validate WireGuard peer IP addresses in a Fly.

FAQ

Frequently asked questions

With a standalone Fly MCP server, the agents and LLMs can only access a fixed set of Fly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Fly and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Fly tools.

Yes, absolutely. You can configure which Fly scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Fly data and credentials are handled as safely as possible.

Start with Fly.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Fly tool your agent needs.Free to start.

Start building