Mocai CLI
Turn ordinary video into production-ready motion capture from your terminal or your AI agent. Mocai reconstructs the people in a clip and gives you rigged animation as FBX, GLB, USD or BVH, retargeted onto Mixamo, UE5 Manny or MetaHuman if you like.
The same tool ships on npm and PyPI. Use whichever runtime you have:
npx @mocai/cli process clip.mp4 # Node 18+
uvx mocai process clip.mp4 # Python 3.9+ (or: pipx install mocai)
Sign in
mocai login
This opens your browser to sign in to Mocai (a free account works) and stores
the sign-in in ~/.config/mocai/credentials.json (%APPDATA%\mocai on
Windows). Both the npm and the PyPI versions share it. If your browser can't
reach the CLI after you click Allow (WSL, SSH, containers), copy the address it
landed on and paste it into the terminal. For scripts and CI, set
MOCAI_API_KEY to a key from mocai.ai/app/developers
instead.
Process videos
mocai process clip.mp4 # FBX into ./mocai-out
mocai process takes/ --exports fbx,glb --rigs ue5 --out mocap
mocai process a.mp4 b.mov --kinds keypoints-json --json
Give files or folders (every video inside is processed). Videos upload in
parallel, process on Mocai's GPUs, and the exports land in --out
(default ./mocai-out).
| Option | Values |
|---|---|
--exports |
fbx, glb, usd, bvh (default fbx) |
--rigs |
mixamo, ue5, metahuman: also retarget and download fbx-<rig> |
--kinds |
usd-mesh, keypoints-json, keypoints-csv |
--max-persons N |
performers to capture (default: your plan's cap) |
--smoothing |
off, standard, strong |
--root-motion |
drop-in (default) or performer |
--no-hands |
skip hand and finger tracking |
--no-mesh |
skeleton only, no skinned performer mesh |
--json |
machine-readable result on stdout |
Other commands: mocai account (plan and usage), mocai takes,
mocai download <takeId> --kinds fbx,glb, mocai logout.
Use it from an AI agent (local MCP server)
mocai mcp runs a local MCP server, so Claude Desktop, Claude Code, Cursor and
other MCP clients can process the videos on your machine with one tool call
(process_videos). Add it to your client's MCP config:
{
"mcpServers": {
"mocai": { "command": "npx", "args": ["-y", "@mocai/cli", "mcp"] }
}
}
or with Python: "command": "uvx", "args": ["mocai", "mcp"]. Claude Code:
claude mcp add mocai -- npx -y @mocai/cli mcp. The first tool call opens your
browser to sign in.
Prefer a hosted connector instead (claude.ai, ChatGPT)? Add
https://api.mocai.ai/v1/mcp as a custom connector. See
mocai.ai/docs.
Exit codes
0 success, 1 a video or request failed, 2 usage error, 3 not signed in.
Metadata
Release files for mocai 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mocai-0.1.0.tar.gz | 20.5 kB | With provenance | Details for mocai-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mocai-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mocai-0.1.0-py3-none-any.whl |
Total release size: 45.9 kB
Release files / mocai-0.1.0.tar.gz
| Download URL | mocai-0.1.0.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad6167056eff74ed377a20a844354d9caaa4098f6fc8874b1c1a98f64f392497
|
|
BLAKE2b-256 checksum How to use checksums |
ba9f14af4c521d9174339a08662a74725477d96d009e5ef99d8e346c437dc4d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logRelease files / mocai-0.1.0-py3-none-any.whl
| Download URL | mocai-0.1.0-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
91e679ca97cf32b04bfd86a8ae4c353c884f3326b6becdbe9911bda3349faa77
|
|
BLAKE2b-256 checksum How to use checksums |
2d2decdc6d576b164376230dc2daf0e6ee91b77e8df14210c1457538c04b034e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logSecurity for mocai 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mocai-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.