How to integrate College football data MCP with Google ADK

Framework Integration Gradient
College football data Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting College football data to Google ADK using the Composio tool router. By the end, you'll have a working College football data agent that can show betting lines for this week's games, get tv schedule for sec games this weekend, list advanced box scores for ohio state, summarize team talent rankings for 2024 through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a College football data account through Composio's College football data 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 College football data account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for College football data
  • Build an agent that connects to College football data through MCP
  • Interact with College football data 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 College football data MCP server, and what's possible with it?

The College football data MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your College Football Data account. It provides structured and secure access to comprehensive college football stats, schedules, advanced analytics, and recruiting data, so your agent can fetch game results, analyze team performance, retrieve broadcast info, and explore historical metrics on your behalf.

  • Retrieve game schedules and results: Instantly fetch upcoming games, past scores, and matchup outcomes filtered by season, week, team, or conference.
  • Analyze advanced team and player stats: Have your agent pull in-depth box scores, advanced metrics, and season-long analytics to compare team or player performance.
  • Access media and broadcast information: Quickly get details on TV, radio, and streaming coverage for selected games, including broadcast schedules and platforms.
  • Review team talent and recruiting rankings: Let your agent track composite team talent scores and recruiting class data across seasons for any program.
  • Explore historical conference and division data: Effortlessly trace a team's conference membership history, division alignment, and related metadata over time.

Supported Tools & Triggers

Tools
Advanced Box ScoreTool to retrieve advanced box score metrics for a single college football game.
Advanced Game StatsTool to retrieve advanced team metrics at the game level.
Advanced Season Stats by TeamTool to retrieve advanced season metrics aggregated by team and season.
Betting LinesTool to fetch betting lines and totals by game and provider.
Composite Team TalentTool to fetch composite team talent rankings by season.
Conference Memberships HistoryTool to retrieve historical conference memberships for teams, including years active and division.
Divisions by ConferenceTool to list FBS/FCS conference divisions with active years and metadata.
Get Drive DataTool to retrieve drive-level data and results.
Get Game MediaTool to retrieve game media information and broadcast schedules (TV, radio, web, etc.
Get Games and ResultsTool to retrieve games and results for a given season/week/team.
Get Player Game StatsTool to fetch player statistics at the game level.
Get Team Game StatsTool to fetch team statistics at the game level.
List Coaches and HistoryTool to get coaching records and history.
List ConferencesTool to list all college football conferences.
List FBS TeamsTool to list FBS teams for a given season.
List FCS TeamsTool to list FCS teams for a given season and conference.
List TeamsTool to list college football teams.
List Venues and StadiumsTool to list college football venues with metadata (name, capacity, location, etc.
NFL Draft PicksTool to list NFL Draft picks.
NFL Draft PositionsTool to list NFL draft positions.
NFL Draft TeamsTool to list NFL teams used in draft endpoints.
Play-by-Play DataTool to fetch play-by-play data for college football games.
Play Stats PlayerTool to fetch player-level stats tied to individual plays.
Play Stat TypesTool to fetch all play-level stat type definitions.
Player PPA by GameTool to retrieve player-level PPA/EPA broken down by game.
PPA Player By SeasonTool to fetch player-level PPA/EPA aggregated by season.
Predict Expected Points (EP)Tool to get expected points by down, distance, and field position.
PPA Team By GameTool to retrieve team Predicted Points Added (PPA) by game.
Rankings PollsTool to retrieve weekly human/computer poll rankings.
Elo RatingsTool to retrieve Elo ratings for college football teams.
SP+ RatingsTool to retrieve SP+ team ratings.
SRS RatingsTool to retrieve Simple Rating System (SRS) team ratings.
Recruiting Group DictionaryTool to list recruiting position group aggregations.
Recruiting Transfer PortalTool to retrieve transfer portal entries for a given season.
Returning Production by TeamTool to fetch Bill Connelly–style returning production splits by team and season.
Season Stats PlayerTool to fetch basic season stats aggregated by player and season.
Season Team StatsTool to get basic season stats aggregated by team and season.
Season Types DictionaryTool to list season types.
Team Matchup HistoryTool to retrieve head-to-head team matchup records over a date range.
Team season recordsTool to fetch team season records by year with optional filters.
Get Team RosterTool to fetch roster for a given team and season.

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 College football data 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=["college_football_data"],
)

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 College football data 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 College football data and Google ADK:

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=["college_football_data"],
)

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 College football data operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate College football data 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 College football data MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and College football data MCP?

With a standalone College football data MCP server, the agents and LLMs can only access a fixed set of College football data tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from College football data 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 College football data tools.

Can I manage the permissions and scopes for College football data while using Tool Router?

Yes, absolutely. You can configure which College football data 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 College football data 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.