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
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago