otherapi_key

OpenSea

OpenSea is the world's first and largest NFT marketplace for NFTs and crypto collectibles.

Verdict

OpenSea MCP lets your team read NFT marketplace data, create listings and offers, and fulfill orders without leaving Switchy. @mention it to check collection floor prices, list tokens for sale, build trait-based offers, or pull account profiles. Useful for teams managing NFT drops, tracking portfolio performance, or automating marketplace actions. Setup requires an OpenSea API key with appropriate rate limits — free tier keys work for read operations but paid plans unlock higher throughput for listing and offer creation. Fulfillment tools return transaction data you'll still execute onchain separately.

Common use cases

  • Check floor prices before listing NFTs
  • Build trait offers for collection sweeps
  • Monitor account activity across wallets
  • Automate listing updates during drops
  • Pull fulfillment data for onchain execution

Integration

Vendor
OpenSea
Category
other
Auth
API_KEY
Tools
24
Composio slug
open_sea

Tools

  • Build criteria offer

    Build a portion of a criteria offer including the merkle tree needed to post an offer.

  • Cancel order

    Offchain cancel a single order, offer or listing, by its order hash when protected by the signedzone. protocol and chain are required to prevent hash collisions. please note cancellation is only assured if a fulfillment signature was not ve

  • Create criteria offer

    Create a criteria offer to purchase any nft in a collection or which matches the specified trait.

  • Create item offer

    Create an offer to purchase a single nft (erc721 or erc1155).

  • Create listing

    List a single nft (erc721 or erc1155) for sale on the opensea marketplace.

  • Fulfill listing

    Retrieve all the information, including signatures, needed to fulfill a listing directly onchain.

  • Fulfill offer

    Retrieve all the information, including signatures, needed to fulfill an offer directly onchain.

  • Get account

    Get an opensea account profile including details such as bio, social media usernames, and profile image.

  • Get all listings by collection

    Get all active, valid listings for a single collection.

  • Get all offers by collection

    Get all active, valid offers for the specified collection. this includes individual and criteria offers.

  • Get best listing by nft

    Get the best listing for an nft.

  • Get best listings by collection

    Get the cheapest priced active, valid listings on a single collection.

  • Get best offer by nft

    Get the best offers for an nft.

  • Get collection

    Get a single collection including details such as fees, traits, and links.

  • Get collections

    Get a list of opensea collections with optional filtering and pagination.

  • Get collection stats

    Get stats for a single collection on opensea.

  • Get contract

    Get a smart contract for a given chain and address.

  • Get events

    Get a list of events from opensea based on various filters like timestamps and event types.

  • Get listings

    Get the complete set of active, valid listings.

  • Get nft

    Get metadata, traits, ownership information, and rarity for a single nft.

  • Get order

    Get a single order, offer or listing, by its order hash. protocol and chain are required to prevent hash collisions.

  • Get payment token

    Get a smart contract for a given chain and address.

  • Get traits

    Get the traits in a collection.

  • Refresh nft metadata

    Refresh metadata for a single nft.

Setup

Setup guide

  1. 11. Go to opensea.io/account/settings/developer and generate an API key (free or paid tier depending on your volume needs). 2. In Switchy, open your workspace settings and navigate to Integrations. 3. Find OpenSea in the MCP directory and click Connect. 4. Paste your API key when prompted and confirm the connection. 5. Open any Space and type '@OpenSea get account' followed by a wallet address to test — you should see profile details returned in seconds. 6. To create listings or offers, ensure your API key has write permissions enabled in OpenSea's developer portal. 7. When building criteria offers or fulfilling orders, the MCP returns transaction payloads you'll sign and submit through your wallet separately.

What teammates see: by default, memories from OpenSea are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Check Collection Floor

@OpenSea what's the floor price and total listings for Bored Ape Yacht Club right now?
Open in a Space →

List Token for Sale

@OpenSea create a listing for my token at 0x1234...abcd contract address, token ID 5678, priced at 2 ETH with 7 day expiration.
Open in a Space →

Build Trait Offer

@OpenSea build a criteria offer for any Azuki with 'Red Hair' trait, offering 8 ETH per token, valid for 3 days.
Open in a Space →

Fulfill Active Listing

@OpenSea get fulfillment details for the listing at order hash 0xabc123... so I can complete the purchase onchain.
Open in a Space →

Pull Account Profile

@OpenSea get the account profile for wallet address 0x9876...fedc including bio and social media handles.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@OpenSea what's the floor price for Bored Ape Yacht Club right now, and show me the 3 cheapest listings with their token IDs

Output

Based on current OpenSea data, BAYC floor is 28.5 ETH. Here are the three lowest-priced listings: Token #7453 at 28.5 ETH (listed 2 hours ago), Token #9201 at 28.9 ETH (listed 6 hours ago), and Token #3847 at 29.1 ETH (listed 1 day ago). Each listing includes the seller's wallet address and expiration timestamp. Note this is illustrative—actual floor prices fluctuate minute-to-minute based on market activity.

Notes

Demonstrates read-heavy collection querying. OpenSea's API returns live marketplace data, but you need an API key with appropriate rate limits. High-traffic collections may have dozens of listings at floor price simultaneously, so results can shift between queries. No blockchain interaction required for browsing.

Prompt

@OpenSea create a listing for my NFT at contract 0x1234...abcd, token ID 42, priced at 0.5 ETH, expiring in 7 days

Output

Listing created successfully. Your NFT (token #42 from contract 0x1234...abcd) is now listed at 0.5 ETH with expiration set for 7 days from now. The listing uses Seaport protocol and requires your wallet signature to finalize onchain. Order hash: 0x9876...5432. You can cancel this listing anytime via the cancel_order tool before a buyer fulfills it. Gas fees apply only when the sale completes.

Notes

Shows the write-action workflow for creating marketplace listings. This example illustrates the response structure—actual usage requires wallet connectivity and signature authorization. The MCP prepares the listing payload but doesn't execute blockchain transactions directly. You must handle signature prompts in your wallet interface separately.

Prompt

@OpenSea pull all active offers on my wallet's NFTs and draft a summary of which ones are worth accepting based on current floor prices

Output

You have 4 active offers across your collection. Two offers exceed floor: Token #156 offered at 1.2 ETH (floor: 0.9 ETH, +33% premium), and Token #203 offered at 2.5 ETH (floor: 2.1 ETH, +19% premium). The other two offers are below floor and likely not worth accepting unless you need immediate liquidity. Token #156's offer expires in 18 hours—consider accepting soon if you want to capture that premium before expiration.

Notes

Combines OpenSea's offer-retrieval tools with AI reasoning to provide actionable insights. Requires API access to fetch offer data, then the AI synthesizes floor-price context. This example is illustrative—real floor prices and offer counts depend on your wallet's holdings. Rate limits apply when querying multiple collections simultaneously.

Use-case deep-dives

NFT marketplace integration for gaming studio

When OpenSea MCP fits a web3 game's in-house marketplace

A 6-person game studio building a collectible card game wants players to trade cards peer-to-peer without leaving Discord. The OpenSea MCP is the right call if your cards are already ERC-1155 tokens on a chain OpenSea supports and you need listing/offer flows that mirror the main marketplace. The create_listing and fulfill_offer tools handle the signature dance so your bot can post trades and close deals without custom smart contract work. The threshold: if you're launching a new collection or need custom royalty splits that OpenSea's standard contracts don't cover, you'll hit the API's constraints fast and should build direct on Seaport instead. For studios with existing OpenSea presence who want chat-native trading, this MCP saves two weeks of integration work.

DAO treasury NFT liquidation

Offloading DAO-owned NFTs through Slack commands

A 12-person DAO holds 40 NFTs from grants and airdrops and wants treasury managers to list or accept offers without touching MetaMask during monthly calls. The OpenSea MCP works if the DAO uses a multisig that can pre-sign transactions and the assets are on Ethereum or Polygon. The cancel_order and create_item_offer tools let the team propose and revoke listings in Slack threads, then batch-execute onchain later. The trade-off: OpenSea's API requires the signedzone protocol for offchain cancellations, so if your multisig setup doesn't support that signature type, you'll cancel onchain and pay gas every time. For DAOs doing fewer than 10 trades a quarter with standard multisigs, this MCP turns a 20-minute MetaMask ritual into a 2-minute Slack vote.

Customer support for NFT marketplace

When support agents need read-only OpenSea lookups

A 3-person support team at an NFT analytics startup fields questions about why a user's listing isn't showing up or what offers are live on a collection. The OpenSea MCP is overkill here because 22 of the 24 tools are write operations that require wallet signatures, and support agents only need the get_account tool to pull profile data. You're better off with a lightweight REST wrapper or the OpenSea API directly in your ticketing system. The MCP makes sense only if the same workspace also has a product team that posts test listings or builds offer trees for QA, so the write tools get used daily. For pure support lookup workflows, the auth overhead and unused tool surface make this MCP a poor fit.

Frequently asked

What does the OpenSea MCP let me do in Switchy?

The OpenSea MCP lets your team create and manage NFT listings and offers directly from Switchy. You can list NFTs for sale, make offers on collections or specific tokens, fulfill existing listings or offers, and retrieve account profiles. It handles the merkle tree construction and signature gathering needed for onchain transactions, so you don't need to interact with OpenSea's interface manually.

Do I need an OpenSea API key to connect this MCP?

Yes. The OpenSea MCP requires an API key from your OpenSea developer account. You'll need to generate one at opensea.io/developers and paste it into Switchy during setup. The key authenticates all requests, so keep it secure—anyone with access can create listings and offers on your behalf.

Can the OpenSea MCP actually execute trades or just prepare them?

It prepares trades but doesn't execute them. Tools like fulfill_listing and fulfill_offer return all the data and signatures needed to complete a transaction onchain, but you still need to submit that transaction through a wallet. The MCP handles the complex API work; your wallet handles the blockchain interaction and gas fees.

Why use this instead of just browsing OpenSea's website?

Use the MCP when you're managing NFT operations programmatically or alongside other work in Switchy. If you're listing dozens of items, monitoring floor prices, or building offers based on trait data, the MCP saves you from clicking through OpenSea's UI repeatedly. For one-off purchases, the website is faster.

Who on my team should connect the OpenSea MCP?

Whoever manages your NFT portfolio or treasury. This person needs access to your OpenSea API key and should understand the financial implications of creating listings and offers. Since the MCP can initiate transactions worth real money, limit access to team members who actively work with your NFT holdings.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.