How to integrate Polygon io MCP with LlamaIndex

This guide walks you through connecting Polygon io to LlamaIndex using the Composio tool router. By the end, you'll have a working Polygon io agent that can get daily summary for aapl stock, retrieve latest news on tsla ticker, check if nyse market is open now through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Polygon io account through Composio's Polygon io MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Polygon io logoPolygon io
Api Key

Polygon io provides powerful APIs for real-time and historical market data—covering stocks, options, forex, and crypto. Instantly access reliable financial data to power your applications or trading strategies.

60 Tools

Introduction

This guide walks you through connecting Polygon io to LlamaIndex using the Composio tool router. By the end, you'll have a working Polygon io agent that can get daily summary for aapl stock, retrieve latest news on tsla ticker, check if nyse market is open now through natural language commands.

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

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

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

The Polygon io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Polygon io account. It provides structured and secure access to real-time and historical financial market data, so your agent can pull ticker lists, fetch stock summaries, analyze technical indicators, and surface news updates on your behalf.

  • Comprehensive ticker discovery and lookup: Instantly retrieve detailed lists of supported stock, forex, crypto, and option tickers to power your trading dashboards or research tools.
  • Daily summary and technical analysis: Ask your agent to fetch daily price summaries, calculate exponential moving averages, MACD, or RSI for any supported ticker and timeframe.
  • Financial events and dividend insights: Pull up historical dividend distributions, keep tabs on scheduled market holidays, and plan trading activities around real exchange calendars.
  • Up-to-date market status monitoring: Have your agent check real-time market open/close statuses and trading conditions across multiple exchanges and asset classes.
  • Automated news aggregation for securities: Let your agent gather the latest news articles, sentiment analysis, and headlines for specific tickers, helping you stay informed with minimal effort.

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

Getting API Keys for OpenAI, Composio, and Polygon io

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 Polygon io 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 polygon io_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: ["polygon_io"],
    },
  );

  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 Polygon io 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, polygon io)
  • 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 Polygon io 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 Polygon io
  • 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 Polygon io 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 Polygon io
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

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

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

Get All Tickers

Tool to retrieve a comprehensive list of supported ticker symbols across all asset classes.

Get Condition Codes

Tool to retrieve a unified list of trade and quote condition codes and their definitions.

Get Crypto EMA

Tool to calculate Exponential Moving Average (EMA) technical indicator for a crypto ticker.

Get Crypto MACD

Tool to calculate Moving Average Convergence/Divergence (MACD) technical indicator for a crypto ticker.

Get Crypto Open/Close

Tool to get the open, close, high, low, and volume for a cryptocurrency pair on a specific date.

Get Crypto RSI

Tool to calculate the Relative Strength Index (RSI) for a cryptocurrency ticker.

Get Crypto SMA

Tool to calculate Simple Moving Average (SMA) technical indicator for a cryptocurrency ticker.

Get Daily Open/Close

Tool to get the daily open, close, after-hours, and pre-market prices for a stock on a specific date.

Get Dividends

Tool to retrieve a historical record of cash dividend distributions for a given ticker.

Get Economy Inflation Indicators (Enhanced)

Tool to retrieve key indicators of realized inflation including CPI and PCE price indexes with comprehensive date filtering.

Get Exponential Moving Average

Tool to retrieve the Exponential Moving Average for a stock ticker.

Get SEC Filing

Tool to retrieve detailed information about a specific SEC filing by filing ID.

Get SEC Filing File

Tool to download a specific file from an SEC filing.

Get Forex EMA

Tool to calculate Exponential Moving Average (EMA) technical indicator for a forex pair.

Get Forex MACD

Tool to calculate Moving Average Convergence/Divergence (MACD) technical indicator for a forex pair.

Get Forex Real-Time Currency Conversion

Tool to convert amounts between currency pairs using real-time forex rates.

Get Forex RSI

Tool to calculate the Relative Strength Index (RSI) technical indicator for a forex pair.

Get Forex SMA

Tool to calculate Simple Moving Average (SMA) technical indicator for a forex pair.

Get Futures Quotes

Tool to get real-time quote information for futures contracts with bid/ask prices, sizes, and timestamps.

Get Grouped Daily Market Summary

Tool to retrieve daily OHLCV data for the entire market for a given date.

Get Historic Forex Ticks

Tool to get historic ticks for a currency pair on a specific date.

Get Inflation Expectations

Tool to retrieve inflation expectations data from the Federal Reserve, including market-based rates and Cleveland Fed model estimates.

Get IPO Data

Tool to retrieve comprehensive information on Initial Public Offerings (IPOs), including upcoming and historical events.

Get Labor Market Data

Tool to retrieve labor market data including unemployment rate, labor force participation rate, average hourly earnings, and job openings.

Get MACD

Tool to retrieve the Moving Average Convergence/Divergence (MACD) for a stock ticker.

Get Market Holidays

Tool to retrieve upcoming market holidays and their corresponding open/close times.

Get Market Status

Tool to retrieve the current trading status across major exchanges and currency markets.

Get News

Tool to retrieve the most recent news articles for a specified ticker.

Get Options Contract Overview

Tool to retrieve comprehensive details about a specific options contract including contract type, exercise style, expiration date, strike price, and underlying ticker.

Get Options EMA

Tool to calculate Exponential Moving Average (EMA) technical indicator for an options ticker.

Get Options MACD

Tool to calculate Moving Average Convergence/Divergence (MACD) technical indicator for an options ticker.

Get Options RSI

Tool to calculate Relative Strength Index (RSI) technical indicator for an options ticker.

Get Options SMA

Tool to calculate Simple Moving Average (SMA) technical indicator for an options ticker.

Get Related Companies

Tool to retrieve tickers related to a given ticker based on similar business or market characteristics.

Get RSI

Tool to retrieve the Relative Strength Index (RSI) for a stock ticker.

Get Simple Moving Average

Tool to retrieve the Simple Moving Average (SMA) for any ticker (stocks, forex, crypto).

Get Splits

Tool to retrieve historical stock split events for a given ticker.

Get Stocks Custom Bars

Tool to retrieve aggregated historical OHLC and volume data for a stock over custom date ranges with configurable time windows.

Get Stocks Daily Market Summary

Tool to retrieve daily OHLC, volume, and VWAP data for all U.

Get Stocks Filings Risk Factors

Tool to retrieve risk factors identified in companies' 10K filings.

Get Stocks Filings Sections

Tool to retrieve raw text content from specific sections of SEC filings (10-K, 10-Q, etc.

Get Stocks Free Float

Tool to retrieve free float data for US-listed securities showing the most recent available number of shares available for public trading and the percentage of total shares outstanding.

Get Stocks Full Market Snapshot

Tool to retrieve a comprehensive snapshot of the entire U.

Get Stocks Income Statements

Tool to retrieve comprehensive income statement data including revenue, expenses, and net income from company SEC filings.

Get Stocks Previous Day Bar

Tool to retrieve the previous trading day's open, high, low, close (OHLC), and volume data for a stock ticker.

Get Stocks Risk Factor Taxonomies

Tool to retrieve the complete list of risk factor classifications used in the risk factors endpoint.

Get Stocks V1 Dividends

Tool to retrieve historical dividend payment records for US stocks with split-adjusted amounts and historical adjustment factors.

Get Short Interest Data

Tool to retrieve comprehensive FINRA short interest data that tracks the short selling metrics for securities on a specific settlement date.

Get Short Volume Data

Tool to retrieve short selling volume data for stock tickers.

Get Stocks V1 Splits

Tool to retrieve historical stock split and reverse split events for US equities with historical adjustment factors for price normalization.

Get Ticker Events

Tool to retrieve timeline of ticker change events such as symbol renaming or rebranding.

Get Ticker Overview

Tool to retrieve comprehensive details for a single ticker, including identifiers, industry, and branding assets.

Get Ticker Types

Tool to retrieve a list of all ticker types supported by Polygon.

Get Treasury Yields

Tool to retrieve daily market yields for US Treasury securities across standard maturities (1-month to 30-year).

List Exchanges

Tool to retrieve all exchanges supported by Polygon.

List Filing Files

Tool to retrieve files associated with an SEC filing by filing ID.

List SEC Filings

Tool to retrieve SEC filings from the Polygon.

List Options Contracts

Tool to list and filter options contracts by underlying ticker, type, expiration, strike, and more.

Last Quote for a Symbol

Tool to retrieve the last quote tick for a given stock symbol.

Last Trade for a Currency Pair

Tool to retrieve the last trade tick for a currency pair in the forex market.

FAQ

Frequently asked questions

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

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

Start with Polygon io.It takes 30 seconds.

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

Start building