How to integrate Api sports MCP with LlamaIndex

This guide walks you through connecting Api sports to LlamaIndex using the Composio tool router. By the end, you'll have a working Api sports agent that can show today's football fixtures for la liga, get head-to-head record for chelsea vs arsenal, list injured players in premier league this week through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Api sports account through Composio's Api sports MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Api sports logoApi sports
Api Key

Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.

67 Tools

Introduction

This guide walks you through connecting Api sports to LlamaIndex using the Composio tool router. By the end, you'll have a working Api sports agent that can show today's football fixtures for la liga, get head-to-head record for chelsea vs arsenal, list injured players in premier league this week through natural language commands.

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

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

Also integrate Api sports with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Api sports
  • Connect LlamaIndex to the Api sports MCP server
  • Build a Api sports-powered agent using LlamaIndex
  • Interact with Api sports through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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

The Api sports MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Api sports account. It provides structured and secure access to rich sports data, so your agent can fetch fixtures, analyze team stats, retrieve player info, and explore historical match data on your behalf.

  • Live fixture and match retrieval: Instantly access upcoming and past football fixtures, filterable by league, team, date, or season for up-to-date match information.
  • Detailed match statistics and events: Have your agent pull granular match data, including goals, cards, substitutions, and in-depth statistics like possession, fouls, and passes for any fixture.
  • Team, coach, and player insights: Effortlessly fetch team rosters, coach histories, and individual player statistics or injury reports, making it easy to analyze team lineups and track player performance over time.
  • Head-to-head comparisons and historical data: Ask your agent to compare two teams’ direct matchups, review historical data, or examine league rounds, helping you make informed predictions or reports.
  • Dynamic country and league exploration: Let your agent discover available countries, leagues, and competitions, then drill down by code or search to tailor your sports data queries to specific needs.

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

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Api sports account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Api sports

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Api sports access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called api sports_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["api_sports"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Api sports actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, api sports)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Api sports tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Api sports
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Api sports tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Api sports
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Api sports, then start asking questions.

Complete Code

Here's the complete code to get you started with Api sports and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["api_sports"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Api sports actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Api sports to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Api sports tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Get AFL Games

Tool to retrieve AFL games and matches.

Get AFL Game Player Statistics

Tool to retrieve player statistics from AFL (Australian Football League) game(s).

Get AFL Seasons

Tool to get the list of available seasons for AFL.

Get AFL Standings

Tool to retrieve AFL standings for a league.

Get Baseball Games Head-to-Head

Tool to get head-to-head baseball games between two teams.

Get Basketball Bets

Tool to get all available basketball bet types.

Get Basketball Bookmakers

Tool to get all available basketball bookmakers.

Get basketball statistics

Tool to get basketball statistics for a team in a given league and season.

Get Formula 1 Circuits

Tool to get the list of available Formula 1 circuits.

Get Coaches

Tool to fetch coaches and their career history.

Get Countries

Tool to fetch available countries for league queries.

Get Fighters Records

Tool to get fighter career statistics.

Get Fixtures

Tool to retrieve football fixtures/matches.

Get fixtures events

Tool to get events (goals, cards, substitutions, VAR, etc.

Get Head-to-Head Fixtures

Tool to get head-to-head fixtures between two teams.

Get Fixture Lineups

Tool to retrieve starting XI and substitutes for a fixture.

Get fixtures players

Tool to get player statistics from a fixture.

Get Fixtures Rounds

Tool to get the rounds for a league or cup.

Get fixture statistics

Tool to get statistics for a fixture.

Get Formula 1 Competitions

Tool to retrieve Formula 1 competitions (Grand Prix races).

Get Formula 1 Races

Tool to retrieve Formula 1 race information for a given season.

Get Formula 1 Starting Grid

Tool to retrieve the starting grid for a Formula 1 race.

Get games events

Tool to get events (goals, penalties, etc.

Get AFL Games Quarters

Tool to retrieve AFL game quarter scores.

Get game statistics by teams

Tool to get team statistics from a game by ID.

Get Injuries

Tool to get injured or suspended players.

Get Leagues

Tool to retrieve leagues and cups.

Get League Seasons

Tool to get the list of available seasons for all leagues.

Get MMA Categories

Tool to fetch the list of all available MMA categories.

Get MMA Fighters

Tool to fetch MMA fighters data.

Get MMA Fights

Tool to retrieve the list of MMA fights according to given parameters.

Get MMA Fight Results

Tool to retrieve results from one or several MMA fights.

Get MMA Fighter Statistics

Tool to get fighter statistics from MMA fights.

Get NBA game statistics

Tool to get NBA game statistics including player stats for both teams.

Get NFL Standings Conferences

Tool to retrieve the list of available conferences for the NFL to be used in the standings endpoint.

Get Odds

Tool to fetch pre-match odds.

Get Odds Bets

Tool to get all available pre-match bet types.

Get Odds Bookmakers

Tool to list all available pre-match bookmakers.

Get In-Play Odds

Tool to fetch in-play odds for fixtures in progress.

Get Live Odds Bets

Tool to fetch all available bet types for in-play odds.

Get Odds Mapping

Tool to get the list of available fixture IDs for the odds endpoint.

Get Players

Tool to get player statistics.

Get Players Profiles

Tool to get the list of all available players.

Get Players Seasons

Tool to list all available seasons for player statistics.

Get Players Squads

Tool to get player squads.

Get player statistics

Tool to get player statistics for a specific basketball game.

Get Players Teams

Tool to get the list of teams and seasons in which a player played during his career.

Get Players Top Assists

Tool to get the 20 best players (top assists) for a league or cup.

Get Players Top Red Cards

Tool to get the 20 players with the most red cards for a league or cup.

Get Players Top Scorers

Tool to get the 20 best players (top scorers) for a league or cup.

Get Players Top Yellow Cards

Tool to get the 20 players with the most yellow cards for a league or cup.

Get Predictions

Tool to get predictions about a fixture.

Get Formula 1 Driver Rankings

Tool to retrieve Formula 1 driver rankings for a season.

Get Fastest Laps Rankings

Tool to get the ranking of the fastest laps for a Formula 1 race.

Get Race Rankings

Tool to retrieve rankings for a specific Formula 1 race.

Get Formula 1 Team Rankings

Tool to retrieve Formula 1 team rankings for a specific season.

Get Sidelined

Tool to get sidelined information (injuries, suspensions, etc.

Get Standings Divisions

Tool to retrieve the list of available divisions for an NFL competition to be used in the standings endpoint.

Get Standings Groups

Tool to retrieve the list of available groups for a league to be used in the standings endpoint.

Get Standings Stages

Tool to retrieve the list of available stages for a league to be used in the standings endpoint.

Get Teams

Tool to retrieve available teams.

Get Team Seasons

Tool to get the list of seasons available for a team.

Get team statistics

Tool to get detailed statistics of a team for a given league and season.

Get Timezone

Tool to fetch the complete list of available timezones for fixture queries.

Get Transfers

Tool to get all available transfers for players and teams.

Get Trophies

Tool to get trophies for a player or coach.

Get Venues

Tool to retrieve available venues.

FAQ

Frequently asked questions

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

Yes, you can. LlamaIndex 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 Api sports tools.

Yes, absolutely. You can configure which Api sports 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 Api sports data and credentials are handled as safely as possible.

Start with Api sports.It takes 30 seconds.

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

Start building