How to integrate AccuWeather MCP with LlamaIndex

This guide walks you through connecting AccuWeather to LlamaIndex using the Composio tool router. By the end, you'll have a working AccuWeather agent that can fetch current conditions, get hourly forecasts, retrieve your weather alerts, and report minute-by-minute precipitation through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a AccuWeather account through Composio's AccuWeather MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

AccuWeather logoAccuWeather
Api Key

AccuWeather is a global weather service providing current conditions, forecasts, MinuteCast precipitation, alerts, and lightning data. Use it for fast, localized forecasts and real-time weather alerts.

41 Tools

Introduction

This guide walks you through connecting AccuWeather to LlamaIndex using the Composio tool router. By the end, you'll have a working AccuWeather agent that can fetch current conditions, get hourly forecasts, retrieve your weather alerts, and report minute-by-minute precipitation through natural language commands.

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

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

Also integrate AccuWeather 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 AccuWeather
  • Connect LlamaIndex to the AccuWeather MCP server
  • Build a AccuWeather-powered agent using LlamaIndex
  • Interact with AccuWeather 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 AccuWeather MCP server, and what's possible with it?

The AccuWeather MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your AccuWeather account. It provides structured and secure access to global weather conditions, forecasts, alerts, precipitation updates, and storm data, so your agent can check current weather, plan around forecasts, monitor alerts, assess precipitation, and track tropical storms on your behalf.

  • Current conditions and forecasts: Have your agent check current conditions and retrieve hourly or daily forecasts for cities and other locations worldwide.
  • Weather alerts and alarms: Let the agent monitor active government weather alerts and threshold-based alarms for locations you care about.
  • Minute-by-minute rain and lightning: Direct your agent to assess near-term precipitation, forecast lightning probability, or review recent lightning strikes around chosen coordinates.
  • Tropical storm tracking: Instruct your agent to find active tropical storms and review their latest positions, observed paths, forecast tracks, intensity, and status.
  • Local weather context: Have your agent find locations, explore nearby cities, review lifestyle indices, or retrieve recent radar and satellite imagery for trip and activity planning.

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 AccuWeather account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and AccuWeather

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 AccuWeather 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 accuweather_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: ["accu_weather"],
    },
  );

  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 AccuWeather 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, accuweather)
  • 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 AccuWeather 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 AccuWeather
  • 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 AccuWeather 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 AccuWeather
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with AccuWeather 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: ["accu_weather"],
    },
  );

  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 AccuWeather 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 AccuWeather to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes AccuWeather 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 AccuWeather action and event your agent gets out of the box.

Autocomplete Locations

Return location-name suggestions for all locations, cities, or points of interest, optionally restricted to a country.

Get Administrative Area

Return one administrative area by country and administrative-area codes.

Get Country

Return one country by AccuWeather region and country codes.

Get Current Conditions

Return current weather observations for an AccuWeather location key, optionally including extended details and weather photos.

Get Daily Forecast

Return a 1, 5, 7, 10, or 15-day forecast for a location key.

Get Daily Indices

Return 1, 5, 10, or 15-day lifestyle-index forecasts for all indices, one group, or one index at an AccuWeather location.

Get Historical Current Conditions

Return the past 6 or 24 hours of current-condition observations for an AccuWeather location key.

Get Hourly Forecast

Return a 1, 12, 24, 72, or 120-hour forecast for an AccuWeather location key.

Get Index

Return metadata for one AccuWeather lifestyle index.

Get Index Group

Return the lifestyle indices belonging to one AccuWeather index group.

Get Lightning Forecast

Return forecast lightning probabilities for latitude/longitude coordinates.

Get Location

Return full location metadata for an AccuWeather location key.

Get MinuteCast Forecast

Return minute-by-minute precipitation conditions for latitude/longitude coordinates.

Get Radar and Satellite Imagery

Return recent radar and satellite image metadata and URLs for an AccuWeather location at a selected resolution.

Get Region

Return one AccuWeather region by region code.

Get Translation Group

Return translated strings for one AccuWeather translation group.

Get Tropical Storm Current Position

Return the latest observed position of a government-issued tropical storm.

List Active Tropical Storms

Return active government-issued tropical storms globally, by basin, or by basin and government storm ID.

List Administrative Areas

Return administrative areas globally or within a country, one provider page at a time.

List Countries

Return countries globally or within a specific AccuWeather region, one provider page at a time.

List Index Groups

Return lifestyle-index groups and their identifiers.

List Indices

Return all supported lifestyle indices and their identifiers.

List MinuteCast Color Codes

Return full or simplified color-code metadata used in MinuteCast precipitation output.

List Neighboring Cities

Return cities near an AccuWeather location key.

List Recent Lightning Strikes

Return recent lightning strikes within 1 to 60 miles of latitude/longitude coordinates as a GeoJSON FeatureCollection.

List Regions

Return AccuWeather geographic regions and their codes.

List Supported Languages

Return AccuWeather-supported languages with numeric IDs and language codes.

List Top Cities

Return top-ranked AccuWeather cities globally or within one region.

List Top City Conditions

Return current weather conditions for a requested number of globally ranked cities.

List Translation Groups

Return available AccuWeather translation groups and their identifiers.

List Tropical Storm Forecasts

Return forecast positions and intensity for a government-issued tropical storm.

List Tropical Storm Positions

Return the observed position history of a government-issued tropical storm.

List Tropical Storms by Year

Return government-issued tropical storms for a year, optionally filtered by basin and government storm ID.

List Tropical Storm Statuses

Return government-issued tropical storm status categories and wind-speed definitions globally or for one basin.

List Weather Alarms

Return threshold-based weather alarms for the next 1, 5, 10, or 15 days at an AccuWeather location.

List Weather Alerts

Return active government-issued weather alerts for a location key.

Resolve Language Identifier

Convert an AccuWeather language code to its numeric ID or a numeric language ID to its code.

Search Administrative Areas

Search administrative areas by required non-empty name text and optional country and administrative-area code filters, one 25-result provider page at a time.

Search City by IP Address

Resolve an IPv4 or IPv6 address to an AccuWeather city location.

Search Locations

Search cities, general locations, postal codes, or points of interest by text and optional geographic filters.

Search Locations by Coordinates

Find the nearest general location, city, or point of interest to latitude/longitude coordinates.

FAQ

Frequently asked questions

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

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

Start with AccuWeather.It takes 30 seconds.

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

Start building