
ClipmivoAI
com.clipmivoaiPublished by clipmivoai.comv0.1.7Updated Oct 24, 2026
AI video workflows: model discovery, credit quotes, generation, private media and usage.
Overview
A local MCP server that lets an assistant create AI videos through the ClipmivoAI API: discover models, get credit quotes, generate, and manage media.
- What you can do
- Discover available video models and check account balance and usage with read access (video:read). Request credit quotes and submit video generation tasks with write access (video:write). Upload local media and download finished results when a files directory is configured (files:write). Track task status and resume queries after a wait timeout instead of creating duplicate tasks.
- When to use it
- Use it when you want an assistant to produce AI-generated videos through a ClipmivoAI account, with a quote reviewed before any paid generation. It suits users who already have ClipmivoAI credits and want generation driven from a local MCP client.
- Requirements
- A local stdio MCP client and the packaged server (README states Node.js 22+ and npm). A scoped ClipmivoAI API key in CLIPMIVO_API_KEY, created in the developer workspace, with scopes video:read, video:write and files:write as needed. An optional CLIPMIVO_API_URL for a trusted HTTPS deployment and an optional existing CLIPMIVO_FILES_DIR to enable file tools. Account credits are added separately on the website.
Installation
In SourceWeft
- Open ClipmivoAI in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ClipmivoAI developer tools
Create AI videos through the ClipmivoAI API, CLI, local MCP server or agent Skill. All clients use https://clipmivoai.com/api/v1, your scoped API key and your ClipmivoAI account balance.
English · 简体中文 · Website · API guide · OpenAPI
Choose your interface
Sign in at ClipmivoAI, create a scoped key in the API / CLI (Developer) workspace and add credits through the website. Read operations require video:read, quotes and generation require video:write, and media uploads require files:write. API requests create video tasks; they do not purchase credit top-ups.
Install
Requires Node.js 22+ and npm. Published downloads are hosted in GitHub Releases; these commands do not depend on an npm registry listing:
Set CLIPMIVO_API_KEY using your shell or secret manager. Never put a real key into this repository. For development:
First video
Review the current quote and confirm your spending limit. Follow the CLI quote confirmation example to add quoted_credits to a separate request file, then submit:
Keep the same confirmed request and idempotency key after an uncertain submission. A wait timeout is not a failed video; resume status queries instead of creating another task. Model options and prices can change: use live model discovery and quotes.
Credit billing and your application
Show credits_to_hold directly as Credits; do not multiply an API credit quote by 100. Credits are reserved before generation, then settled using actual usage where applicable. Unused reserved credits return to the balance. The reference conversion is 100 Credits = US$1; top-ups are purchased separately on the website.
For a customer-facing app, keep the ClipmivoAI key on your server. Keys on one account share its balance and account-level resources; they are not isolated reseller subaccounts. See application integration.
MCP
Configure a client that supports local stdio MCP:
Store the real key in your client's secret settings. On Windows use an existing directory such as C:/Users/you/Videos/Clipmivo; see the MCP guide if your client cannot resolve command shims. This is a local server, not a hosted MCP OAuth endpoint.
Skill
Copy skills/clipmivo-video into the skill directory supported by your agent. For Codex, use ~/.codex/skills/clipmivo-video. Restart or reload skills, then ask:
Use $clipmivo-video to create a video of a paper boat on a pond. Maximum generation spend: 25 Credits.
The Skill can use the installed MCP or CLI. It preserves existing budget authorization and requires a valid quote before paid submission. Installing the Skill does not create an API key or grant credits.
Support
Use GitHub issues for reproducible client bugs without credentials or private media. Account, payment and billing questions: [email protected]. Service use remains subject to the website's terms and privacy policy.
This repository contains public client tools and documentation, not the website backend.
Source: README.md at commit 431a7ca
Tools
0Version history
1- v0.1.7LatestOct 15, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts