Story MCP Hub

Overview

The Story MCP Hub is a consolidated platform that exposes two specialized Model Context Protocol (MCP) servers: StoryScan MCP and Story SDK MCP. Together, they give AI assistants—whether in Claude, IDEs, or custom tooling—direct, programmatic access to the Story Protocol ecosystem. By packaging blockchain queries, IPFS interactions, and licensing logic behind a single MCP interface, the hub removes the need for developers to write custom adapters for each external service.

The primary problem this server solves is integration friction. Developers building AI‑powered workflows often face disparate APIs for blockchain data, IPFS storage, and smart contract interactions. The hub aggregates these into a unified MCP schema, allowing an AI agent to request transaction histories, upload media, mint licenses, or transfer revenue with a single tool call. This reduces boilerplate code, lowers the cognitive load on developers, and ensures consistent error handling across services.

Key features include:

• Blockchain Query Toolset – Retrieve transactions, address overviews, token and NFT holdings, and interpret raw transaction data through StoryScan’s API.
• IPFS & Metadata Operations – Upload images, create metadata objects, and manage content storage via Pinata or other IPFS gateways.
• License Management – Fetch license terms, calculate minting fees, and mint license tokens on the Story Protocol blockchain.
• IP & NFT Management – Register intellectual property, attach license terms, mint NFTs, and create SPG (Story Protocol Governance) collections.
• Revenue & Token Handling – Deposit work‑in‑progress (WIP) funds, transfer WIP, pay royalties on behalf of creators, claim accumulated revenue, and raise disputes.

In real‑world scenarios, a content creator could prompt an AI assistant to “mint a new NFT for my latest artwork and attach the appropriate license terms.” The assistant would call the IPFS upload tool, invoke the license minting function, and register the NFT—all through MCP calls. Similarly, a marketplace bot could “fetch all pending royalty payouts for a user and claim them automatically.” The token tools handle the entire workflow, from querying balances to executing transfers.

Integration with AI workflows is seamless: any MCP‑compatible client can discover the server’s resources, prompt users for tool arguments, and receive structured responses. Because the hub centralizes authentication (e.g., API keys for StoryScan, wallet credentials for blockchain interactions), developers can focus on business logic rather than credential plumbing. The standout advantage is this single entry point that unifies multiple, otherwise siloed services into one coherent protocol—dramatically speeding up prototype development and reducing maintenance overhead.