
Vecmo
io.github.chibataku0815Published by GitHub account chibataku0815v0.1.0Updated Oct 24, 2026
Vector motion editor MCP: 26 typed tools to observe, validate and edit documents, then export code.
Overview
Vecmo's local MCP server gives an assistant 26 typed tools to observe, validate and edit vector motion documents and export runtime code.
- What you can do
- Observe and validate the typed scene/motion document of a Vecmo project
- Apply scene and motion edit commands to change a project
- Export artboards and motion artifacts as self-contained JS runtime code with typed declarations
- Work headlessly through the same command envelope used by the vmactl CLI
- When to use it
- Useful when you work with Vecmo vector-motion projects and want an assistant to inspect a scene, apply structured edits, or trigger code exports instead of editing by hand in the browser editor.
- Requirements
- Runs as a local stdio process launched from the repository (bun run mcp:agent) and needs the Bun runtime plus the Vecmo repo checked out; the README suggests adding the repo's .mcp.json to Claude Code or Cursor. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Vecmo 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
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,
vmactlfor 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
.dctlfile for DaVinci Resolve Studio 18+.
[hello-motion exported artifact playing standalone (48.2 KB gzip)]
Quick start
/ 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).
Try it
bun run dev, then open/?ref=hello-motion.- Export → Motion / Code → EMBED ("Motion Artifact", self-contained embeddable artifact).
- 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 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 — 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)
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 for the full command reference and 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 for the responsibility layers (app -> pages -> widgets -> features -> entities -> shared) and docs/codemap.md for where each subsystem lives.
Contributing
See 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.
Source: README.md at commit 63070cf
Tools
0Version history
1- v0.1.0LatestSep 16, 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