# framefields vs sync. labs MCP server (slim)

> framefields scores 53.9 (D) to sync. labs's 51.5 (D) for video edit. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/framefields-vs-sync-labs-mcp.md (~4,300 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/framefields-vs-sync-labs-mcp.json · canonical https://www.anchorterminal.com/compare/framefields-vs-sync-labs-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

framefields scores 53.9 (D) on agent readiness against sync. labs MCP server's 51.5 (D), and leads in 5 of 7 scored categories. sync. labs MCP server leads on payments & pricing. Both do video edit.

- framefields: D 53.9, rank #930 of 1510 · https://www.anchorterminal.com/tools/framefields.min.md
- sync. labs MCP server: D 51.5, rank #1026 of 1510 · https://www.anchorterminal.com/tools/sync-labs-mcp.min.md
- framefields, good for Coding agents that write motion graphics, data stories, title cards and 3D product shots as code and render them locally or on their own GPU. Ahead on Reliability, 61 against 43; Agent ergonomics, 74 against 55; Security & auth, 45 against 38; Maintenance & community, 89 against 75. Also No key needed to call it; Free to start without a card.
- sync. labs MCP server, good for Agents that lip-sync or dub video into other languages. Ahead on Payments & pricing, 30 against 20. Also A hosted endpoint, with nothing to install; No incidents deducted, where framefields loses 5 points for them.

| Category | framefields | sync. labs MCP server |
| --- | --- | --- |
| Reliability (16%) | 61 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 81 |
| Agent ergonomics (13%) | 74 | 55 |
| Security & auth (14%) | 45 | 38 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 89 | 75 |
| Transparency & trust (7%) | 46 | 44 |

| Fact (where they differ) | framefields | sync. labs MCP server |
| --- | --- | --- |
| Kind | SDK + MCP | MCP server |
| Vendor | Gatewai | Synchronicity Labs (sync.) |
| Hosted endpoint | no (local only) | `https://mcp.sync.so/mcp` |
| Transports |  | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Paid |
| Licence | Apache-2.0 | MIT |
| MCP registry | not listed | `io.github.synchronicity-labs/mcp-server` |
| Last release | 2026-11-02 | none |
| Terms last updated | not read yet | no document linked |
| Privacy policy last updated | not read yet | no document linked |
| Popularity | 445 stars, 1.1k npm/wk | none |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Agent ergonomics, framefields +19: framefields 74 (A library with no tool definitions to load. The four skills are 88 KB of Markdown and load only when a task matches (16). Output can be sized to the check, by one frame, a contact-sheet grid with a step, a frame range, a quality level, and on the worker an LFS include list (16). `comp.lint()` returns `{ severity, code, message, layerId }`, `renderVideo({ qa })` returns measured issues with times, and worker jobs fail with `{ code, message, phase, retryable, hint }` (18). Frames are a function of the frame number; worker jobs take an `idempotencyKey` and a `source.commit` pin, and renders accept an AbortSignal (16). Setup needs Node.js 22, an ES module project and an approved skia-canvas install script; TypeScript only (8).); sync. labs MCP server 55 (A generated catalogue filtered by client profile, curated for ChatGPT (15). Project history and estimates (12 of 20). Recovery tools; errors not documented (8 of 20). Annotations not read (5 of 20). OAuth or a key, npm package and library use (15). 15 + 12 + 8 + 5 + 15 = 55.)
- Reliability, framefields +18: framefields 61 (Read with the local-software lines, because the library and the renderer worker run on the owner's machines. Official npm package `framefields` with Node.js 22 or later stated in the README and getting-started page, though not in `engines` (20). The one public CI workflow still builds, typechecks and tests only the renderer worker on pushes to main, with GPU tests skipped, and the library's own Vitest suite isn't run in CI. Its pass state on 2 November couldn't be read (GitHub's pages and API refused); the last ten runs passed per the 20 October check (10). Seven bug issues filed on 13 October 2026 by an outside reporter were closed with fixes within a day, per the 20 October check. 2.9.3 (31 October) fixed prompted tracking that failed for every npm user since 2.9.0 the same day, because a peer package was never published (18). Changesets changelog with major, minor and patch entries, but 2.7.0, a minor release, removed TextReveal's `track` style, and 2.2.0 removed exports from `@framefields/client-utils`, a companion package (8). Version 2.12.0, but the README badge still says beta, so 5 of 15 (5). 20 + 10 + 18 + 8 + 5 = 61.); sync. labs MCP server 43 (Status page at status.sync.so with maintenance and previous incidents (20). History not read (5). No MCP limits found (0). The source has abort-signal handling and recovery guidance for long jobs (8 of 15). No SLA found (0). Version 0.2.4, not labelled beta (10). 20 + 5 + 0 + 8 + 0 + 10 = 43.)
- Maintenance & community, framefields +14: framefields 89 (Version 2.12.0 on 2 November 2026, the day of the check, per the repository's version bumps; npm wasn't readable (30). 19 version bumps from 2.4.0 to 2.12.0 in the 14 days since 20 October, 42 since 5 October, five of them betas (20). Outside bug reports of 13 October 2026 were fixed and closed within a day, per the 20 October check; issue and pull request reply times weren't re-read, and pull requests #39 to #52 and #64 to #77, all from the vendor's own branches, were merged between 21 October and 2 November (18). It is Gatewai's own package, current with the skills, which follow its version (15). Dependencies are current (zod 4, mediabunny 1.61.6 as a stated minimum), but CI covers only the worker and the GPU backend depends on `webgpu` 0.4, a pre-1.0 package (6). 30 + 20 + 18 + 15 + 6 = 89.); sync. labs MCP server 75 (v0.2.4 and commits on 7 November 2026 (30). Three tags in recent weeks (20). Issues not read (0). Official registry entry io.github.synchronicity-labs/mcp-server (15). CI with verify, publish and review workflows (10). 30 + 20 + 0 + 15 + 10 = 75. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Payments & pricing, sync. labs MCP server +10: framefields 20 (Open-source software with a hosted option, so pricing is scored on the hosted parts, as lightpanda's was. Since 2.4.0 (21 October) the package calls Gatewai's AI gateway, billed in prepaid credits, and since 2.11.0 (2 November) it renders on Gatewai's cloud GPUs. No x402, MPP or L402; an empty balance answers HTTP 402 with no machine payment scheme (0). The docs charge credits "based on model usage plus margin" at the price in the model catalogue, which framefields.dev/models draws by script, and no cloud GPU rate is published (`--plan` prints only an estimate), so no per-unit price could be read (0). The engine itself still renders locally for free with no account or card, and no free credit for the gateway was found (20). The gateway and cloud need a sign-in at framefields.dev/dashboard, a top-up through Dodo Payments and a key made there (0). 0 + 0 + 20 + 0 = 20.); sync. labs MCP server 30 (No machine payment protocol (0). Per-second prices published (20). A free try for short videos (10 of 20). A person signs up (0). 0 + 20 + 10 + 0 = 30.)
- Security & auth, framefields +7: framefields 45 (Read with the framework lines. The library takes no credentials for local rendering. The optional AI gateway and cloud renders take a `FRAMEFIELDS_API_KEY` from the dashboard, stored hashed with a per-key monthly spending limit, and the self-hosted worker uses one bearer key for all jobs plus a git token (15). The worker refuses repositories outside a required `FF_REPO_ALLOWLIST`, removes secrets from the environment before project code runs, shares node_modules read-only, and its README warns that allowed repositories' code runs in the worker's process. The getting-started page has the owner deny five of six dependency install scripts (12). It renders the owner's assets and returns no third-party text, apart from preview notes a person writes for the agent (10). Worker results report the rendered commit SHA, timings and GPU; no audit log (5). No SECURITY.md in the repository and no security.txt on 2 November (403 at /.well-known/, 404 at the root); OSV holds no advisory for `framefields`. npm provenance per the 20 October check (none on 2.3.2), not re-read. Vision models are fetched from pinned Hugging Face revisions with a SHA-256 check (3).); sync. labs MCP server 38 (OAuth per organisation, or an API key in the environment (22 of 30). No read-only mode (3 of 20). Media in and out, no third-party text (10). No audit log found (0). No security programme found (3 of 20). 22 + 3 + 10 + 0 + 3 = 38.)