Vivideo Toolchain
The developer + agent integration layer for the Vivideo API — a shared client, an MCP server, a CLI, and Skills. Agents are a primary user, not an afterthought.
Everything sits on top of the public API (the source of truth). No backend business logic is duplicated here — the toolchain only adds client-side ergonomics and guardrails.
Architecture
One client, one set of types, derived from packages/core/openapi.yaml. The MCP server and CLI both call @vivideo/core — there is exactly one representation of each request/response, so the tools, CLI, docs and OpenAPI stay consistent.
@vivideo/core adds only client-side concerns, never business logic:
These complement — and never bypass — the API's own auth, rate limits, idempotency, credit checks, premium gates, ownership and error model.
Quick start
Once published: npm i -g @vivideo/cli (gives vivideo), and npx @vivideo/mcp for the server.
Docs
- MCP server — install, configure, connect to clients, tool reference
- CLI — install, auth, command reference, JSON & non-interactive use, exit codes
- Skills — install & use
- Workflows — human & agent, end to end
- Security, rate limits, idempotency, credits & premium, troubleshooting
Authentication & security
- Keys are read from (in order): explicit option →
VIVIDEO_API_KEY env → ~/.vivideo/config.json (written owner-only 0600).
- The key is never printed — all output passes through secret redaction;
configure stores it without echoing it.
- Keys are account-scoped secrets. Keep them server-side; one per integration so a leak is revocable in isolation.
Not included (honest scope)
- Cancellation — the public API has no cancel endpoint, so no cancel tool/command is offered. Failed/stuck renders are auto-refunded by the API.
- Agent/chat mode — not exposed by the public API, so not in the toolchain.
- Nothing here publishes to npm, provisions DNS, or deploys — those are external steps (see the final section of docs/mcp.md).
Development
Requires Node ≥ 18.17.