Vecmo MCP server
io.github.chibataku0815/vecmo·v0.1.0Vector motion editor MCP: 26 typed tools to observe, validate and edit documents, then export code.
0 stars
Reviews
Write oneNobody has reviewed Vecmo yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Vecmo tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 40 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Vecmo compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 63/100
- higher than 19% of 4,461 AI and agents servers
Install Vecmo in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Vecmo repository's README, as published. We do not edit it. Read it on GitHub
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+.
Quick start
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).
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=; 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 --out ./out (prints raw/gzip bytes and tier), or bun run dev → /?ref= → Export → EMBED → gzip the .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 observedocument, applyscenecommands, and exportartboard. 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
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-16downgradeB → Cscore 63
Vecmo: common questions
- Is Vecmo MCP server safe?
- With care: it is graded C, so read the findings first (63/100). Read the Vecmo safety report
- Does Vecmo need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Vecmo maintained?
- The last commit was 60 days ago (2026-09-06). The latest release is v0.1.0.
- What can I use instead of Vecmo?
- Servers from other publishers that do the same job: Agent-Native Slides MCP server, Godot MCP server and Superlog MCP server.
Alternatives to Vecmo
Same job from other publishers: the closest match first, then the best rated.
- Agent-Native SlidesAgent-Native Google Slides - generate and edit React presentationsnot reviewedEstablishedA
- Godot MCPAgent-driven Godot playtesting: editor control, input injection, game-time stepping, live state.not reviewedEstablishedA
- SuperlogOpen-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.not reviewedEstablishedA
- CHAP CoordinatorAuditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.not reviewedEstablishedA
- OpenflowkitArchitecture diagrams for your agent: draw on the live OpenFlowKit canvas or edit diagram files.not reviewedEstablishedA