Story SDK MCP Server

Created By
piplabsa year ago
An MCP server for the Story SDK
Overview

what is Story SDK MCP Server?

Story SDK MCP Server is a server that provides Model Context Protocol (MCP) tools for interacting with Story's Python SDK, enabling developers to manage intellectual property (IP) assets and licenses.

how to use Story SDK MCP Server?

To use the server, install the necessary dependencies, configure your environment variables, and run the server using the provided commands. You can then interact with the server using any MCP-compatible client.

key features of Story SDK MCP Server?

  • Retrieve license terms for specific IDs
  • Mint and register IP assets with terms
  • Mint license tokens
  • Send IP tokens to specified wallets
  • Upload images and metadata to IPFS via Pinata

use cases of Story SDK MCP Server?

  1. Managing IP assets for digital content creators.
  2. Minting NFTs and managing their metadata.
  3. Facilitating the transfer of IP tokens between wallets.

FAQ from Story SDK MCP Server?

  • What is the purpose of the Story SDK MCP Server?

It provides tools for managing IP assets and licenses using the Model Context Protocol.

  • How do I set up the server?

Follow the setup instructions to install dependencies and configure your environment.

  • Can I use this server with any AI framework?

Yes, the tools are accessible through the MCP protocol and can be used with any compatible client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
piplabs
Star
7
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

11 hours ago
Voyei

an hour ago