How to integrate Fly MCP with Google ADK

GET STARTED FOR FREE
Framework Integration Gradient
Fly Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Fly to Google ADK 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 my fly app to 3 instances through natural language commands.

This guide will help you understand how to give your Google ADK 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.

TL;DR

Here's what you'll learn:
  • Get a Fly account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Fly
  • Build an agent that connects to Fly through MCP
  • Interact with Fly using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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.

Supported Tools & Triggers

Tools
Add WireGuard PeerTool to add a WireGuard peer connection to a Fly.
Check App Name AvailabilityTool to validate an app name for Fly.
Check JobsExecute GraphQL queries against the Fly.
Check User Only TokenCheck whether the authentication token only allows user access.
Create Health Check JobTool to create a health check job for monitoring application endpoints in Fly.
Create Check Job RunTriggers a run of an existing health check job on Fly.
Create Delegated WireGuard TokenTool to create a delegated WireGuard token for peer management in a Fly.
Create Third-Party ConfigurationTool to create a third-party service configuration for discharging macaroon caveats.
Delete Delegated WireGuard TokenTool to delete a delegated WireGuard token from a Fly.
Delete OrganizationTool to delete a Fly.
Delete Remote BuilderTool to delete a remote builder configuration for a Fly.
Delete Third Party ConfigurationTool to delete a third-party service configuration from Fly.
Detach Postgres ClusterTool to detach a Postgres cluster from a Fly.
Establish SSH KeyTool to establish an SSH key for a Fly.
Fetch Nodes by IDsFetches a list of node objects from Fly.
Get Add-OnTool to find a Fly.
Get Add-On ProviderTool to query information about a specific Fly.
Get app detailsTool to retrieve detailed information about a specific Fly.
Get CertificateTool to retrieve a certificate by its ID from Fly.
Get Current Token InfoTool to get information about the current authentication token.
Get Latest Image DetailsTool to retrieve the latest available tag details for a given image repository from Fly.
Get Latest Image TagTool to retrieve the latest available image tag for a Fly.
Get MachineTool to get a single machine by ID from Fly.
Get Nearest RegionTool to retrieve the nearest Fly.
Get Node by IDTool to fetch an object by its globally unique ID using Fly.
Get OrganizationTool to find a Fly.
Get Personal OrganizationTool to retrieve the user's personal organization details from Fly.
Get PlacementsTool to get placement recommendations for Machines in Fly.
Get Platform InformationTool to retrieve Fly.
Get Products and PricingTool to retrieve Fly.
Get RegionsTool to get the list of available Fly.
Get Viewer InfoTool to retrieve the authenticated user's account information from Fly.
Issue CertificateTool to issue an SSH certificate for accessing Fly.
List Add-On PlansTool to list available add-on service plans from Fly.
List Add-OnsTool to list add-ons associated with an organization in Fly.
List AppsTool to list all Fly Apps in an organization.
List Apps via GraphQLList all Fly.
Check LocationsRetrieve all available Fly.
List MachinesTool to list Fly.
List Organization MachinesTool to list all Machines across all apps in a Fly organization.
Remove WireGuard PeerTool to remove a WireGuard peer connection from a Fly.
Set Apps V2 DefaultTool to configure whether new apps in an organization use Apps V2 by default on Fly.
Update Third-Party ConfigurationTool to update an existing third-party service configuration for discharging macaroon caveats.
Validate ConfigTool to validate a Fly.
Validate WireGuard PeersTool to validate WireGuard peer IP addresses in a Fly.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Fly via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["fly"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Fly operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

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

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["fly"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Fly operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Fly with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Fly using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Fly tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Fly MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Fly MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Fly MCP with Claude Agent SDK

LangChain

LangChain

Use Fly MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Fly MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Fly MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Fly MCP with LlamaIndex

CrewAI

CrewAI

Use Fly MCP with CrewAI

Claude Code

Claude Code

Use Fly MCP with Claude Code

Codex

Codex

Use Fly MCP with Codex

FAQ

What are the differences in Tool Router MCP and Fly MCP?

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.

Can I use Tool Router MCP with Google ADK?

Yes, you can. Google ADK 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.

Can I manage the permissions and scopes for Fly while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free