How to integrate Open sea MCP with OpenAI Agents SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Open sea Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Open sea to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Open sea agent that can list my nft for sale on opensea, show all active listings in bored ape collection, create an offer for a specific cryptopunk, fetch my opensea profile details through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Open sea account through Composio's Open sea MCP server.

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

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Open sea
  • Configure an AI agent that can use Open sea as a tool
  • Run a live chat session where you can ask the agent to perform Open sea operations

What is open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

What is the Open sea MCP server, and what's possible with it?

The Open sea MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your OpenSea account. It provides structured and secure access to your NFT marketplace activity, so your agent can perform actions like listing NFTs for sale, creating and fulfilling offers, checking account details, and managing your marketplace orders on your behalf.

  • NFT listing automation: Quickly list any ERC721 or ERC1155 NFT for sale on OpenSea, specifying price and collection details—all handled by your agent.
  • Offer creation and management: Instruct your agent to create criteria-based or single-item offers to purchase specific NFTs or those matching certain traits within a collection.
  • Order and listing fulfillment: Let your agent retrieve all necessary information and signatures to fulfill existing listings or offers, making transactions seamless and secure.
  • Marketplace activity insights: Have the agent pull your profile details, fetch all active listings or offers for a given collection, and provide you with up-to-date marketplace snapshots.
  • Order cancellation and management: Direct your agent to cancel open orders, listings, or offers off-chain, helping you stay in control of your marketplace participation with ease.

Supported Tools & Triggers

Tools
Build criteria offerBuild a portion of a criteria offer including the merkle tree needed to post an offer.
Cancel orderOffchain cancel a single order, offer or listing, by its order hash when protected by the signedzone.
Create criteria offerCreate a criteria offer to purchase any nft in a collection or which matches the specified trait.
Create item offerCreate an offer to purchase a single nft (erc721 or erc1155).
Create listingList a single nft (erc721 or erc1155) for sale on the opensea marketplace.
Fulfill listingRetrieve all the information, including signatures, needed to fulfill a listing directly onchain.
Fulfill offerRetrieve all the information, including signatures, needed to fulfill an offer directly onchain.
Get accountGet an opensea account profile including details such as bio, social media usernames, and profile image.
Get all listings by collectionGet all active, valid listings for a single collection.
Get all offers by collectionGet all active, valid offers for the specified collection.
Get best listing by nftGet the best listing for an nft.
Get best listings by collectionGet the cheapest priced active, valid listings on a single collection.
Get best offer by nftGet the best offers for an nft.
Get collectionGet a single collection including details such as fees, traits, and links.
Get collectionsGet a list of opensea collections with optional filtering and pagination.
Get collection statsGet stats for a single collection on opensea.
Get contractGet a smart contract for a given chain and address.
Get eventsGet a list of events from opensea based on various filters like timestamps and event types.
Get listingsGet the complete set of active, valid listings.
Get nftGet metadata, traits, ownership information, and rarity for a single nft.
Get orderGet a single order, offer or listing, by its order hash.
Get payment tokenGet a smart contract for a given chain and address.
Get traitsGet the traits in a collection.
Refresh nft metadataRefresh metadata for a single nft.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Open sea project
  • Some knowledge of Python or Typescript

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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Open sea.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Open sea Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["open_sea"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only open_sea.
  • The router checks the user's Open sea connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Open sea.
  • This approach keeps things lightweight and lets the agent request Open sea tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Open sea. "
        "Help users perform Open sea operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Open sea and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Open sea operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Open sea.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Open sea and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["open_sea"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Open sea. "
        "Help users perform Open sea operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Open sea MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Open sea.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Open sea MCP Agent with another framework

Claude Agent SDK

Claude Agent SDK

Use Open sea MCP with Claude Agent SDK

Google ADK

Google ADK

Use Open sea MCP with Google ADK

LangChain

LangChain

Use Open sea MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Open sea MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Open sea MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Open sea MCP with LlamaIndex

CrewAI

CrewAI

Use Open sea MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Open sea MCP?

With a standalone Open sea MCP server, the agents and LLMs can only access a fixed set of Open sea tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Open sea and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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 Open sea tools.

Can I manage the permissions and scopes for Open sea while using Tool Router?

Yes, absolutely. You can configure which Open sea 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.

How safe is my data with Composio Tool Router?

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 Open sea data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free