How to integrate Polymarket US MCP with Vercel AI SDK v6

This guide walks you through connecting Polymarket US to Vercel AI SDK v6 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 Vercel AI SDK 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 Vercel AI SDK v6 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 Vercel AI SDK 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:
  • How to set up and configure a Vercel AI SDK agent with Polymarket US integration
  • Using Composio's Tool Router to dynamically load and access Polymarket US tools
  • Creating an MCP client connection using HTTP transport
  • Building an interactive CLI chat interface with conversation history management
  • Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

  • streamText: Core function for streaming responses with real-time tool support
  • MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
  • Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
  • OpenAI Provider: Native integration with OpenAI models

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

Prerequisites

Before you begin, make sure you have:
  • Node.js and npm installed
  • A Composio account with API key
  • An OpenAI API key
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 required dependencies

bash
npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv

First, install the necessary packages for your project.

What you're installing:

  • @ai-sdk/openai: Vercel AI SDK's OpenAI provider
  • @ai-sdk/mcp: MCP client for Vercel AI SDK
  • @composio/core: Composio SDK for tool integration
  • ai: Core Vercel AI SDK
  • dotenv: Environment variable management
4

Set up environment variables

bash
OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

  • OPENAI_API_KEY: Your OpenAI API key for GPT model access
  • COMPOSIO_API_KEY: Your Composio API key for tool access
  • COMPOSIO_USER_ID: A unique identifier for the user session
5

Import required modules and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});
What's happening:
  • We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
  • The dotenv/config import automatically loads environment variables
  • The MCP client import enables connection to Composio's tool server
6

Create Tool Router session and initialize MCP client

typescript
async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["polymarket_us"],
  });

  const mcpUrl = 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 mcp object contains the URL and authentication headers needed to connect to the MCP server
  • This session provides access to all Polymarket US-related tools through the MCP protocol
7

Connect to MCP server and retrieve tools

typescript
const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();
What's happening:
  • We're creating an MCP client that connects to our Composio Tool Router session via HTTP
  • The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
  • The type: "http" is important - Composio requires HTTP transport
  • tools() retrieves all available Polymarket US tools that the agent can use
8

Initialize conversation and CLI interface

typescript
let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to polymarket_us, like summarize my last 5 emails, send an email, etc... :)))\n",
);

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

rl.prompt();
What's happening:
  • We initialize an empty messages array to maintain conversation history
  • A readline interface is created to accept user input from the command line
  • Instructions are displayed to guide the user on how to interact with the agent
9

Handle user input and stream responses with real-time tool feedback

typescript
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;
  }

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

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • We use streamText instead of generateText to stream responses in real-time
  • toolChoice: "auto" allows the model to decide when to use Polymarket US tools
  • stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
  • onStepFinish callback displays which tools are being used in real-time
  • We iterate through the text stream to create a typewriter effect as the agent responds
  • The complete response is added to conversation history to maintain context
  • Errors are caught and displayed with helpful retry suggestions

Complete Code

Here's the complete code to get you started with Polymarket US and Vercel AI SDK:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["polymarket_us"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to polymarket_us, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

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

  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;
    }

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

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

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

Conclusion

You've successfully built a Polymarket US agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

  • Real-time streaming responses for a better user experience with typewriter effect
  • Live tool execution feedback showing which tools are being used as the agent works
  • Dynamic tool loading through Composio's Tool Router with secure authentication
  • Multi-step tool execution with configurable step limits (up to 10 steps)
  • Comprehensive error handling for robust agent execution
  • Conversation history maintenance for context-aware responses

You can extend this further by adding custom 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.

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. Vercel AI SDK v6 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