Open Sea Automation

What This Skill Does

This skill automates Open Sea operations through Composio's Open Sea toolkit via Rube MCP. It allows users to interact with the Open Sea NFT marketplace programmatically. It's designed for developers and NFT enthusiasts looking to automate tasks related to buying, selling, and managing NFTs.

When to Use

• Automate NFT purchases on Open Sea.
• List NFTs for sale on Open Sea.
• Manage NFT inventory on Open Sea.
• Monitor NFT prices and trends.
• Retrieve NFT metadata from Open Sea.
• Integrate Open Sea with other applications.

Key Features

• Automates Open Sea tasks via Rube MCP.
• Uses Composio's Open Sea toolkit.
• Requires an active Open Sea connection.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow for Open Sea operations.

Manual Installation

Automate Open Sea operations through Composio's Open Sea toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/open_sea

Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available).
• Active Open Sea connection via RUBE_MANAGE_CONNECTIONS with toolkit open_sea.
• Always call RUBE_SEARCH_TOOLS first to get current tool schemas.

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit open_sea If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Open Sea operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Open Sea task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["open_sea"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Automate Open Sea operations through Composio's Open Sea toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/open_sea

Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available).
• Active Open Sea connection via RUBE_MANAGE_CONNECTIONS with toolkit open_sea.
• Always call RUBE_SEARCH_TOOLS first to get current tool schemas.

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit open_sea If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Open Sea operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Open Sea task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["open_sea"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference