Scenivia

Why

Scenivia turns a SaaS product into a short launch or feature film, built from a catalogue of designed templates you stay in control of. This plugin gives Claude Code the same controls you have in the Studio.

Install

Three steps, about a minute.

1. Add the marketplace and install the plugin in Claude Code:

/plugin marketplace add Scenivia/claude-plugin/plugin install scenivia@scenivia

2. Ask for a film. The first Scenivia call opens the consent page in your browser: sign in, choose what the agent may do, done.

3. Watch it come together in your Scenivia Studio, and export when you like it.

claude plugin marketplace add Scenivia/claude-pluginclaude plugin install scenivia@scenivia

The plugin adds one skill and the connection to the Scenivia MCP server at https://api.scenivia.com/mcp. It holds no secret.

Use it in other apps

The same server works in any app that speaks MCP over HTTP with OAuth. The address is always https://api.scenivia.com/mcp; the consent page opens on first use, exactly as in Claude Code.

claude mcp add --transport http scenivia https://api.scenivia.com/mcp

{ "mcpServers": { "scenivia": { "url": "https://api.scenivia.com/mcp" } } }

{ "servers": { "scenivia": { "type": "http", "url": "https://api.scenivia.com/mcp" } } }

{ "mcpServers": { "scenivia": { "serverUrl": "https://api.scenivia.com/mcp" } } }

Connect your account

There is nothing to copy or paste: Claude Code opens the Scenivia consent page and the browser hands the agent its token. Run /mcp to see the connection, reconnect or sign out.

The plugin asks for read and edit. Exporting needs render, which you grant when Scenivia asks for it on the first export. Disconnect the agent at any time from Account › Security: its token stops working at once.

[!NOTE] Access to the MCP server is opened account by account. Until it is open for yours, every call answers 404.

What to ask

Make a 30 second launch film for https://example.com in Scenivia, from a template.
Which Scenivia templates would suit a developer tool? Show me the previews.
In my "Launch week" project, change the opening title to "Ship docs in minutes".
Repaint the film in our brand colours and use the logo I uploaded.
Check that the film exports cleanly, then render it and give me the link.

The agent always asks before it starts an export, since an export spends credits.

Tools

32 tools, grouped by what they work on.

Arguments, outputs and JSON Schemas: capabilities.md · catalog.json

Limits and credits

[!TIP] Nothing is charged until an export succeeds. A failed export costs nothing, and a retry costs credits only if it succeeds.

• Credits are bought in Scenivia, never through the agent. Out of credits, the agent says so and stops.
• Writing a storyboard from a prompt uses your plan's generation allowance, not credits.
• Three exports run at once per account; a fourth waits for one to end.
• 120 tool calls a minute per account; template and component browsing, 60 calls an hour.
• Pictures come in from a public HTTPS address (PNG, JPEG or WebP), with the same checks as an upload.
• Placing a template, or adding and removing a shot, lands in your Studio: the agent prepares it, you see it when you open the project.

Every bound: limits.md

Support

Questions, a bug, an idea: [email protected] · scenivia.com

License

Free to install and use with Scenivia, commercial work included. See LICENSE.