How to integrate Polymarket US MCP with CrewAI

This guide walks you through connecting Polymarket US to CrewAI 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 CrewAI 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 CrewAI 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 CrewAI 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:
  • Get a Composio API key and configure your Polymarket US connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Polymarket US
  • Build a conversational loop where your agent can execute Polymarket US operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Polymarket US connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
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

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Polymarket US via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_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 with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Polymarket US MCP URL
6

Create a Composio Tool Router session for Polymarket US

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["polymarket_us"])

url = session.mcp.url
What's happening:
  • You create a Polymarket US only session through Composio
  • Composio returns an MCP HTTP URL that exposes Polymarket US tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["polymarket_us"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Polymarket US through Composio's Tool Router. The agent can perform Polymarket US operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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. CrewAI 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