How to integrate Open sea MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Open sea Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Open sea to the Claude Agent 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 Claude Agent 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 Claude/Anthropic 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 Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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 Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Open sea account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Open sea functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Open sea
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["open_sea"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Open sea
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Open sea tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Open sea
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

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

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Open sea and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Open sea
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["open_sea"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Open sea tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

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

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Open sea through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
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

OpenAI Agents SDK

OpenAI Agents SDK

Use Open sea MCP with OpenAI Agents 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 Claude Agent SDK?

Yes, you can. Claude Agent 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