Storykit Mcp

Give an AI structured data and get back a relevant, hosted StoryKit widget. The agent searches by intent, maps rows to the selected schema, and receives an opaque expiring resource link. Widget HTML, CSS, JavaScript, descriptors, and embed snippets are not exposed through the MCP tools.

No API key or signup is required. The public service is rate-limited per caller IP.

Connect

Remote Streamable HTTP:

claude mcp add --transport http storykit https://asset.storykit.space/api/v1/mcp

Local stdio client:

claude mcp add storykit -- npx -y storykit-mcp

Other MCP clients can use the same remote URL or run npx -y storykit-mcp. The setup guide is at asset.storykit.space/mcp.

Workflow

Ask the agent for the outcome, not a component implementation:

Visualize these CPU readings with a StoryKit widget: user 31, system 12, idle 57.

The agent then:

1. calls find_widgets with the display intent and available field names,
2. selects a result whose dataSchema fits the real rows,
3. calls render_widget, and
4. presents the returned hosted resource link.

For health, location, account, device, or other personal data, the agent must obtain user consent before sending rows. Bound payloads are limited, encrypted at rest, deleted after their configured lifetime, and never echoed by render_widget. The opaque URL is the access grant, so treat it as a secret.

Tools

The old asset-fetch, source, snippet, and bundle tools are intentionally not part of this server.

Limits and privacy

• Maximum 200 rows and 64 KB per render.
• Default lifetime is 30 days; maximum is 365 days.
• Renders are immutable. Create a new resource when the underlying data changes.
• Do not send credentials, access tokens, direct identifiers, or data the user has not authorized.
• STORYKIT_API_BASE can point the stdio package at another StoryKit deployment.

MIT. Created with love by Story Kit.