About Rubiic
Rubiic MCP connects AI clients to Rubiic for creating videos from briefs and rendering them to MP4. It also supports exports such as GIFs, stills, carousels, and captions, with project creation and review handled through an agent workflow.
Key features
- 01Start a video project from a brief
- 02Answer review questions during creation
- 03Render videos to MP4
- 04Export GIFs, stills, carousels, and captions
- 05Attach PDFs as source material
Use cases
- 01Create a video from a plain-language brief
- 02Render a completed project and retrieve its MP4
- 03Export scene visuals for social posts
- 04Generate captions for a video
MCP support
Provides a hosted MCP server at https://rubiic.com/api/mcp for Rubiic video creation and export tools. MCP clients can connect using OAuth sign-in or a personal access token, depending on client support.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://rubiic.com/api/mcpclaude mcp add --transport http com-rubiic-rubiic https://rubiic.com/api/mcp{"mcpServers":{"com-rubiic-rubiic":{"type":"http","url":"https://rubiic.com/api/mcp"}}}Open in Cursor{"servers":{"com-rubiic-rubiic":{"type":"http","url":"https://rubiic.com/api/mcp"}}}Open in VS Code{"mcpServers":{"com-rubiic-rubiic":{"type":"http","url":"https://rubiic.com/api/mcp"}}}{"mcpServers":{"com-rubiic-rubiic":{"serverUrl":"https://rubiic.com/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://rubiic.com/api/mcpAuth requiredTools
Details
From the project READMERubiic MCP
Make videos with Rubiic from Claude and any other MCP client. Describe a video in plain language, answer the agent's review questions, then render it to MP4. From any scene you can also export a GIF, still images, a carousel or captions.
https://github.com/user-attachments/assets/c3945c16-6663-488c-9518-151e29e27e33
Made with Rubiic. Captions: media/rubiic-mcp-explainer.srt.
One MCP server does everything:
https://rubiic.com/api/mcp
This repository holds no server code. Rubiic runs the server, and this repo is how you connect to it:
- a Claude Code plugin with the server and the
rubiicskill - copy-paste configs for other clients
- the tool reference
- a small scripted example
You need a Rubiic account. Everything you do over MCP is billed to it, the same as in the app. See what costs credits.
Claude (Desktop, claude.ai, mobile)
- Open Settings → Connectors → Add custom connector.
- Name it
Rubiicand pastehttps://rubiic.com/api/mcp, then click Add and Connect. - rubiic.com opens. Sign in if you need to, check that the page names
claude.aias where it will send you back, and click Allow access.
That's it. There's no token to copy. To disconnect, remove the connector in Claude or click Disconnect under Connected apps on rubiic.com/account. Disconnecting takes effect within the hour.
Claude Code
/plugin marketplace add rubiic-hq/rubiic-mcp
/plugin install rubiic@rubiic
Claude Code asks for a personal access token once and keeps it in your
system's secure credential store. Create one under Account → API tokens on
rubiic.com. It starts with rbc_ and is
shown once, so copy it right away. The plugin adds the server and the
rubiic skill, which teaches the agent how to poll, when a call spends
credits, and how to handle downloads.
If you'd rather not use the plugin, see clients/claude-code.md.
Other clients
| Client | Config |
|---|---|
| Cursor | clients/cursor.json |
| VS Code | clients/vscode.json |
| Codex CLI | clients/codex.toml |
These use a personal access token as a bearer. The server also supports MCP sign-in (OAuth), so a client that implements it can leave the header out and sign in through rubiic.com instead. That path has been verified with Claude's connectors; other clients vary.
To teach any other agent how to use Rubiic, point it at the skill: https://rubiic.com/skills/rubiic/SKILL.md.
Make a video
Ask Claude something like:
Make a 30-second vertical video explaining how a heat pump works, then render it and give me the MP4.
It starts the video with agent_start and answers the review questions (it may
pass them to you). It then looks up the new project with get_project, renders
it, and hands you the download. You can attach PDFs for Rubiic to work from.
Full reference: docs/tools.md.
After connecting, ask it to run connection_status. That's a free check that
the connection works end to end.
Known limits
- Every
agent_startis a new project. You can't continue or revise an existing video over MCP yet. To revise one, use the app. - Access is account-wide. A connected app or a token can do everything your account can over MCP, including spending credits. There are no read-only or spend-limited grants yet.
Upgrading from 0.1
0.1 used two servers: rubiic-agent for the agent_* tools and rubiic for
the rest. Everything is on rubiic now. /plugin update rubiic@rubiic picks it
up; if you added the servers by hand, remove rubiic-agent. Its URL keeps
working for anything still pointed at it.
Repository layout
.claude-plugin/ Claude Code plugin + marketplace manifests
.mcp.json the plugin's server
skills/rubiic/ the agent skill (mirrors https://rubiic.com/skills/rubiic/SKILL.md)
registry/ the MCP Registry entry
clients/ configs for other MCP clients
docs/ tool reference
examples/ a scripted client
media/ the explainer video, its poster and captions
skills/rubiic/SKILL.md is published from Rubiic's own codebase. Edits made
here are overwritten. Open an issue instead, and CI checks that this copy
matches what rubiic.com serves.
Support
- Bugs and questions: open an issue
- Security: see SECURITY.md. Please don't file those publicly.
License
MIT. The license covers this repository only; your use of the Rubiic service is governed by the terms.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.