# Vecmo

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/chibataku0815/vecmo  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/vecmo

## Description
Vector motion editor MCP: 26 typed tools to observe, validate and edit documents, then export code.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "vecmo": {
    "command": "npx",
    "args": ["-y","vecmo"]
  }
}
```

## Documentation & README

# Vecmo

A browser vector-motion editor that exports dependency-free runtime code.

- Export motion as code, not video: a self-contained JS runtime with typed `.d.ts`, not a rendered clip.
- Agent-native: a typed scene/motion document, `vmactl` for headless/live command work, and 26 MCP tools let an agent read and edit a project.
- GPU Look Graph effects (grain, halftone, riso, CRT, VHS, lens) export to a `.dctl` file for DaVinci Resolve Studio 18+.

![hello-motion exported artifact playing standalone (48.2 KB gzip)](https://raw.githubusercontent.com/chibataku0815/vecmo/HEAD/docs/media/hello-motion-artifact.gif)

## Quick start

```sh
bun install && bun run dev
```

`/` opens the editor. It runs entirely in the browser: local-first, and nothing in this build talks to a server.

Checks: `bun run check`. Build: `bun run build`. No test suite ships in this repo (see [CONTRIBUTING.md](https://github.com/chibataku0815/vecmo/blob/HEAD/CONTRIBUTING.md)).

## Try it

1. `bun run dev`, then open `/?ref=hello-motion`.
2. Export → **Motion / Code** → **EMBED** ("Motion Artifact", self-contained embeddable artifact).
3. Unzip the download: `hello-motion.runtime.js`, its `.d.ts`, a manifest, and a demo HTML page.

Other reference scenes live at `/?ref=<slug>`; see [`src/features/reference-scenes/model/registry.ts`](https://github.com/chibataku0815/vecmo/blob/HEAD/src/features/reference-scenes/model/registry.ts) for the full list.

Headless, without the GUI: `bun run export:motion-artifact -- --ref hello-motion --out ./out` writes the same four files (deterministic; `--commands plan.json` applies an agent edit plan first, `--dump-documents` emits raw scene/motion JSON for the MCP tools).

## Example consumer

[vecmo-example](https://github.com/chibataku0815/vecmo-example) — live at https://vecmo-example.pages.dev — is an unrelated Vite site that imports only the exported files at runtime (no Vecmo source, no SDK): a WebGL look-graph piece as hero, scroll-driven `seekProgress`, palette re-theming, a measured size ladder (49.8 KB / 118 KB / 198 KB gzip), Lighthouse 0.98 desktop / 0.91 mobile, a zero-leak mount/destroy probe, and one real MCP edit → CLI re-export loop.

## Export sizes (measured, gzip -9)

| Scene | Profile | Size |
| --- | --- | --- |
| `hello-motion` | EMBED (Motion Artifact) | 48.2 KB |
| Effects-heavy reference scenes (grain, masks, motion grammar) | EMBED (Motion Artifact) | 115–152 KB |

Reproduce: `bun run export:motion-artifact -- --ref <slug> --out ./out` (prints raw/gzip bytes and tier), or `bun run dev` → `/?ref=<slug>` → Export → EMBED → gzip the `<slug>.runtime.js` inside the zip.

Other export targets: WebGL player, PDF, WebM, SVG, and DCTL (DaVinci Resolve look export).

## MCP

Add the repo's `.mcp.json` to Claude Code or Cursor; it launches `bun run mcp:agent` (`scripts/vma-agent-mcp.ts`) as a local stdio server exposing 26 tools over a typed scene/motion document, for example `observe_document`, `apply_scene_commands`, and `export_artboard`. For headless or scripted work, `bun run vmactl` talks the same command envelope directly, without an MCP client. Read [`docs/agent-command-catalog.md`](https://github.com/chibataku0815/vecmo/blob/HEAD/docs/agent-command-catalog.md) for the full command reference and [`docs/live-mcp-agent-runbook.md`](https://github.com/chibataku0815/vecmo/blob/HEAD/docs/live-mcp-agent-runbook.md) for live-editing over the local relay (`bun run agent:bridge`).

## Scope

This repository is the editor: it runs fully in the browser, and nothing here talks to a server. The vecmo.dev hosted service (accounts, cloud projects, billing) is a separate, private backend and is not included.

## Architecture

Start at [`docs/architecture.md`](https://github.com/chibataku0815/vecmo/blob/HEAD/docs/architecture.md) for the responsibility layers (`app -> pages -> widgets -> features -> entities -> shared`) and [`docs/codemap.md`](https://github.com/chibataku0815/vecmo/blob/HEAD/docs/codemap.md) for where each subsystem lives.

## Contributing

See [CONTRIBUTING.md](https://github.com/chibataku0815/vecmo/blob/HEAD/CONTRIBUTING.md).

## License

The editor is AGPL-3.0-only. A developer layer (the agent/CLI toolkit, the runtime player control/manifest code, and `packages/editor-kernel`) is MIT; see `REUSE.toml` for the exact file list. Everything you export — the runtime JS, the WebGL player, their `.d.ts` files, and your scene/motion/backup documents — carries an added AGPL §7 permission (the Vecmo Runtime Output Exception), so you can embed exported artifacts in proprietary sites and owe nothing back for them. Details: [LICENSING.md](https://github.com/chibataku0815/vecmo/blob/HEAD/LICENSING.md).