Story SDK MCP Server

What is Story SDK MCP Server?

Story SDK MCP Server provides tools that enable AI agents to interact with Story Protocol’s Python SDK. It handles IP asset registration, license management, royalty payments, NFT collection creation, and token operations through the Model Context Protocol.

How to use Story SDK MCP Server?

Install dependencies with uv sync, configure environment variables (wallet private key, RPC provider URL, optional PINATA_JWT for IPFS), then run uv run mcp dev server.py in the story-sdk-mcp directory. Connect to MCP clients like Cursor or Claude Desktop by adding the server as a stdio command using uv --directory <path> run server.py.

Key features of Story SDK MCP Server

• IPFS & Metadata: upload images, create and upload IP metadata (requires PINATA_JWT)
• License Management: get terms, mint license tokens, predict fees
• IP Asset Management: register NFTs, attach license terms, mint and register with terms
• NFT Collection Tools: create SPG NFT collections, get minting fee
• Revenue & Royalty: pay royalties, claim all revenue from child IPs
• Dispute & Token Tools: raise disputes, deposit/transfer WIP, check ERC20 balances, mint test ERC20 tokens

Use cases of Story SDK MCP Server

• Register an NFT as an Intellectual Property asset on Story Protocol
• Automate license token minting and royalty payment workflows
• Create and manage SPG NFT collections for IP asset registration
• Raise disputes against IP assets and claim revenue from child IPs

FAQ from Story SDK MCP Server

What dependencies does Story SDK MCP Server require?

Python 3.12+, the UV package manager, and project dependencies installed via uv sync.

What environment variables are needed?

A wallet private key and RPC provider URL are required. For IPFS tools, a PINATA_JWT must also be set.

How does Story SDK MCP Server communicate with clients?

It uses the stdio transport of the Model Context Protocol (MCP). Clients such as Cursor and Claude Desktop invoke the server as a subprocess via a uv command.

What blockchain and storage does it interact with?

It makes RPC calls to the Story Protocol blockchain and API calls to IPFS (via Pinata) for metadata and image storage.

Are there known limitations?

IPFS tools require a valid Pinata JWT. The server uses a single wallet private key for all blockchain transactions; test tokens can be minted if the contract has a public mint/faucet function.