How to integrate Polymarket US MCP with LlamaIndex

This guide walks you through connecting Polymarket US to LlamaIndex using the Composio tool router. By the end, you'll have a working Polymarket US agent that can list active polymarket us election markets, show your polymarket us open positions, check polymarket us market order books through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Polymarket US account through Composio's Polymarket US MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Polymarket US logoPolymarket US
Api Key

Polymarket US is the CFTC-compliant Polymarket product for verified United States users. Use it to access regulated prediction market data and account workflows through official API credentials.

44 Tools

Introduction

This guide walks you through connecting Polymarket US to LlamaIndex using the Composio tool router. By the end, you'll have a working Polymarket US agent that can list active polymarket us election markets, show your polymarket us open positions, check polymarket us market order books through natural language commands.

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

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

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

The Polymarket US MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Polymarket US account. It provides structured and secure access to your markets, orders, balances, positions, and activity, so your agent can discover markets, inspect prices, place or cancel orders, and monitor your portfolio on your behalf.

  • Market and event discovery: Have your agent find Polymarket US markets, events, subjects, series, and featured topics that match your interests.
  • Price and order book research: Let the agent check the best bid and offer, review market order books, inspect market details, and look up settlement information.
  • Order creation and management: Direct your agent to place one or several live orders, review open orders, close a position, or cancel selected or all open orders.
  • Portfolio monitoring: Instruct your agent to check account balances, review current positions, and summarize trades, deposits, withdrawals, resolutions, bonuses, and transfers.
  • Sports market exploration: Have your agent browse sports, leagues, teams, and related events, including markets for leagues such as the NBA or NFL.

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

Getting API Keys for OpenAI, Composio, and Polymarket US

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 Polymarket US 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 polymarket us_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: ["polymarket_us"],
    },
  );

  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 Polymarket US 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, polymarket us)
  • 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 Polymarket US 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 Polymarket US
  • 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 Polymarket US 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 Polymarket US
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

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

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

Cancel All Open Orders

Cancel all authenticated Polymarket US open orders, optionally scoped to specific market slugs.

Cancel Multiple Orders

Cancel up to 20 Polymarket US open orders in one request.

Cancel Order

Cancel one Polymarket US open order by exchange-assigned order ID.

Close Position Order

Create a live Polymarket US order intended to close an existing position in one market.

Create Multiple Orders

Submit up to 20 live Polymarket US orders in one request.

Create Order

Submit one live Polymarket US order.

Get Account Balances

Get the authenticated user's Polymarket US account balances.

Get Activities

Get authenticated Polymarket US portfolio activities such as trades, resolutions, deposits, withdrawals, referral bonuses, and transfers.

Get Event By ID

Get one Polymarket US event by numeric ID from the public gateway API.

Get Event By Slug

Get one Polymarket US event by slug from the public gateway API.

Get League By Slug

Get a current Polymarket US v2 league by slug.

Get Market BBO

Get the best bid and offer for one Polymarket US market by slug.

Get Market Book

Get the public order book for one Polymarket US market by slug.

Get Market By ID

Get one Polymarket US market by numeric ID from the public gateway API.

Get Market By Slug

Get one Polymarket US market by slug from the public gateway API.

Get Market Settlement

Get settlement information for one Polymarket US market by slug.

Get Markets For Subject

Discover Polymarket US markets associated with a subject ID.

Get Markets For Subject By Slug

Discover Polymarket US markets associated with a subject slug.

Get Open Orders

Get all open orders for the authenticated Polymarket US user.

Get Order

Get an authenticated user's Polymarket US order by exchange-assigned order ID.

Get Series By ID

Get a Polymarket US series by numeric ID.

Get Sport By Slug

Get a current Polymarket US v2 sport by slug.

Get Subject By ID

Get a Polymarket US subject entity by numeric ID.

Get Subject By Slug

Get a Polymarket US subject entity by slug.

Get Tag By ID

Get a Polymarket US topic, sport, or league tag by numeric ID.

Get Tag By Slug

Get a Polymarket US topic, sport, or league tag by slug.

Get User Positions

Get the authenticated user's Polymarket US trading positions across all markets or filtered by a specific market slug.

List Events

Discover Polymarket US events from the public gateway API.

List Events For League

List Polymarket US events for a current v2 league slug such as "nba" or "nfl".

List Events For Series

List Polymarket US sports events for a legacy v1 series ID.

List Events For Sport

List Polymarket US events for a current v2 sport slug such as "football" or "basketball".

List Featured Tags

List featured Polymarket US tag sections from the public gateway API.

List Leagues

List current Polymarket US sports leagues from the v2 public gateway API.

List Markets

Discover Polymarket US markets from the public gateway API.

List Series

List Polymarket US series from the public gateway API.

List Sports

List Polymarket US sports from the current v2 public gateway API.

List Sports Teams

List Polymarket US sports teams from the legacy v1 public gateway API.

List Sports Teams For Provider

List Polymarket US legacy v1 sports team mappings for a data provider.

List Subjects

List Polymarket US subject entities from the public gateway API.

List Tags

List ranked Polymarket US tags from the public gateway API.

Modify Multiple Orders

Modify up to 20 Polymarket US open orders in one request.

Modify Order

Modify one existing Polymarket US open order.

Preview Order

Preview a Polymarket US order without submitting it to the market.

Search Markets And Events

Search public Polymarket US markets and events for discovery.

FAQ

Frequently asked questions

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

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

Start with Polymarket US.It takes 30 seconds.

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

Start building