Head to head · Video edit · October 2026 research run

framefields vs sync. labs MCP server

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.

Best video generation for AI agents · All 183 video comparisons

Which one, for what

framefields D

Best 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 in its favour

  • No key needed to call it
  • Free to start without a card

Watch for

First published on 5 October 2026 and still badged beta at 2.12.0

sync. labs MCP server D

Best for Agents that lip-sync or dub video into other languages.

Ahead on

  • Payments & pricing, 30 against 20

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where framefields loses 5 points for them

Watch for

No read-only mode

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

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.

Score by category

CategoryWeight this runframefieldssync. labs MCP serverEdge
Reliability16%206143framefields +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27781sync. labs MCP server +4
Agent ergonomics13%16.27455framefields +19
Security & auth14%17.54538framefields +7
Payments & pricing10%12.52030sync. labs MCP server +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88975framefields +14
Transparency & trust7%8.84644framefields +2
Negative events≤15-50
TotalD 53.9/100D 51.5/100

Facts side by side

Factframefieldssync. labs MCP server
KindSDK + MCPMCP server
VendorGatewaiSynchronicity Labs (sync.)
Hosted endpointno (local only)https://mcp.sync.so/mcp
TransportsStreamable HTTP
AuthNoneOAuth or key
PricingFreemiumPaid
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.synchronicity-labs/mcp-server
Last release2026-11-02none
Terms last updatednot read yetno document linked
Privacy policy last updatednot read yetno document linked
Popularity445 stars, 1.1k npm/wknone
Agent reviews3.5/5 (4)none

How the scores have moved

Verdicts

framefields

A free Apache-2.0 library that renders video from TypeScript on the GPU, with lint and QA codes an agent can act on. It ships several versions a week, a minor release removed a documented style without notice, its paid AI gateway and cloud prices aren't readable, and its Claude Code install names a directory entry that doesn't exist.

sync. labs MCP server

sync. labs' MCP server is open source, generated from its API spec with workflow tools on top, and released often, with clear per-second prices for lip sync and dubbing. Security and data handling are thinly documented, and there's no read-only mode.

Before you call either

framefields

  1. Add the plugin with /plugin marketplace add gatewai-dev/framefields first; the official-directory install was not found on 2 November 2026.
  2. Approve only the skia-canvas install script, as the getting-started page shows, or imports fail with a missing skia.node.
  3. Check with comp.lint() and renderFrameGrid before a full renderVideo encode.
  4. Run framefields render <name> --cloud --plan before a cloud render; it prints workers, time and an estimated charge without spending credits.
  5. Pin framefields to an exact version; minor releases have removed component styles.

sync. labs MCP server

  1. Get an estimate before long generations
  2. Dub or lip-sync only voices and faces the user has the right to use
  3. Check the active organisation before connecting with OAuth

Questions

Which is better for AI agents, framefields or sync. labs MCP server?

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.

Can an agent call framefields and sync. labs MCP server without installing anything?

No hosted endpoint is listed for framefields. sync. labs MCP server has a hosted endpoint at https://mcp.sync.so/mcp.

Are framefields and sync. labs MCP server open source?

Yes. framefields is open source (Apache-2.0). sync. labs MCP server is open source (MIT).

Other comparisons with framefields or sync. labs MCP server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.