How to integrate Polymarket US MCP with LangChain

This guide walks you through connecting Polymarket US to LangChain 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 LangChain 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.

Get started for freeGet a demo
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 LangChain 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 LangChain 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

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Polymarket US project to Composio
  • Create a Tool Router MCP session for Polymarket US
  • Initialize an MCP client and retrieve Polymarket US tools
  • Build a LangChain agent that can interact with Polymarket US
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Polymarket US functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Polymarket US tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['polymarket_us']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Polymarket US tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Polymarket US tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "polymarket_us-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Polymarket US MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Polymarket US tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Polymarket US related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Polymarket US and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['polymarket_us']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "polymarket_us-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Polymarket US related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Polymarket US through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
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.

FRAMEWORKS

How to build Polymarket US MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Polymarket US MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Polymarket US MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Polymarket US MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Polymarket US MCP with Claude Cowork

Codex logo

Codex

Use Polymarket US MCP with Codex

OpenClaw logo

OpenClaw

Use Polymarket US MCP with OpenClaw

Hermes logo

Hermes

Use Polymarket US MCP with Hermes

CLI logo

CLI

Use Polymarket US MCP with CLI

Google ADK logo

Google ADK

Use Polymarket US MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Polymarket US MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Polymarket US MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Polymarket US MCP with LlamaIndex

CrewAI logo

CrewAI

Use Polymarket US MCP with CrewAI

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. LangChain 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
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies