How to integrate Fly MCP with CrewAI

This guide walks you through connecting Fly to CrewAI using the Composio tool router. By the end, you'll have a working Fly agent that can deploy latest image to fly in tokyo, list all running fly apps by region, scale up your fly app to 3 instances through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Fly account through Composio's Fly MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

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

This guide walks you through connecting Fly to CrewAI using the Composio tool router. By the end, you'll have a working Fly agent that can deploy latest image to fly in tokyo, list all running fly apps by region, scale up your fly app to 3 instances through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Fly account through Composio's Fly MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Fly with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Fly connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Fly
  • Build a conversational loop where your agent can execute Fly operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Fly connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Fly via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Fly MCP URL
6

Create a Composio Tool Router session for Fly

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["fly"])

url = session.mcp.url
What's happening:
  • You create a Fly only session through Composio
  • Composio returns an MCP HTTP URL that exposes Fly tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["fly"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Fly through Composio's Tool Router. The agent can perform Fly operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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. CrewAI 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