# framefields vs Magic Hour MCP (slim)

> framefields scores 53.9 (D) to Magic Hour MCP's 50.7 (D) for video generation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/framefields-vs-magic-hour-mcp.md (~4,800 tokens) · this version ~2,680 tokens · JSON https://www.anchorterminal.com/compare/framefields-vs-magic-hour-mcp.json · canonical https://www.anchorterminal.com/compare/framefields-vs-magic-hour-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 Magic Hour MCP's 50.7 (D), and leads in 4 of 7 scored categories. Magic Hour MCP leads on schema & documentation and transparency & trust. Both do video generation.

- framefields: D 53.9, rank #930 of 1510 · https://www.anchorterminal.com/tools/framefields.min.md
- Magic Hour MCP: D 50.7, rank #1053 of 1510 · https://www.anchorterminal.com/tools/magic-hour-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 35; Agent ergonomics, 74 against 55; Payments & pricing, 20 against 15; Maintenance & community, 89 against 75. Also No key needed to call it; Free to start without a card; Open source.
- Magic Hour MCP, good for Agents making short-form video and images, from talking photos and ads to lip-synced translations, on a credit plan. Ahead on Schema & documentation, 82 against 77; Transparency & trust, 58 against 46. Also A hosted endpoint, with nothing to install; No incidents deducted, where framefields loses 5 points for them.

| Category | framefields | Magic Hour MCP |
| --- | --- | --- |
| Reliability (16%) | 61 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 82 |
| Agent ergonomics (13%) | 74 | 55 |
| Security & auth (14%) | 45 | 45 |
| Payments & pricing (10%) | 20 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 89 | 75 |
| Transparency & trust (7%) | 46 | 58 |

| Fact (where they differ) | framefields | Magic Hour MCP |
| --- | --- | --- |
| Kind | SDK + MCP | MCP server |
| Vendor | Gatewai | Magic Hour AI, Inc. |
| Hosted endpoint | no (local only) | `https://mcp.magichour.ai/` |
| Transports |  | Streamable HTTP |
| Auth | None | OAuth or key |
| Licence | Apache-2.0 | none |
| Tools exposed | none | 50 |
| MCP registry | not listed | `io.github.magichourhq/magic-hour` |
| Last release | 2026-11-02 | none |
| Popularity | 445 stars, 1.1k npm/wk | none |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Reliability, framefields +26: 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.); Magic Hour MCP 35 (Status page at status.magichour.ai, all services online, with maintenance and previous incidents sections; no MCP component read (15). Incident history not read (5). No API rate limits found (0). No retry guidance found; wait_for_* tools poll long jobs (5 of 15). No SLA found (0). Not labelled beta (10). 15 + 5 + 0 + 5 + 0 + 10 = 35.)
- 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).); Magic Hour MCP 55 (50 tools totalling about 160 KB of definitions (5). list_saved_items and project getters; limited size controls (10 of 20). Error handling not documented (5 of 20). Every tool annotated, 14 read-only and the three deletes marked destructive (20). Few required inputs and SDKs (Python, Node and others listed in the docs) (15). 5 + 10 + 5 + 20 + 15 = 55.)
- 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.); Magic Hour MCP 75 (Changelog entries on 3, 4 and 5 November 2026 (30). More than three dated entries in 90 days (20). Changelog and support; issues on the public MCP repository not read (10 of 25). Registry entry io.github.magichourhq/magic-hour (0.1.1, 4 November) (15). No package health read (0). 30 + 20 + 10 + 15 + 0 = 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.)
- Transparency & trust, Magic Hour MCP +12: framefields 46 (Apache-2.0, an OSI licence, in LICENCE and the npm metadata (30). A privacy policy and terms of service for the hosted parts, effective 26 October 2026, say what the dashboard and gateway collect, that request bodies aren't kept, that output files are kept while the account is open and deleted on request, that content isn't used to train models, and that sharing goes to Cloudflare, fal, Dodo Payments, GitHub and Google. Retention has no periods in days and there is no DPA. NOTICE.md now states that vision models download on first use (18). No deprecation policy; the changelog names removed styles and exports without notice periods (3). The privacy policy names sub-processors and says data may be processed in the United States and Asia, and states no analytics trackers on the site; no telemetry was found in the library's source, which has no statement either way (15). 30 + 18 + 3 + 15 = 66.); Magic Hour MCP 58 (Closed service under terms naming Magic Hour AI, Inc., revised 3 October 2026 (15). The privacy policy says prompts, uploads and outputs aren't sold or used to train models, for free and paid accounts, and MCP requests are handled the same way; retention periods aren't given (20 of 30). No deprecation policy found (5 of 20). Subprocessors not read (10 of 20, model providers named in tool docs). 15 + 20 + 5 + 10 = 50.)
- Schema & documentation, Magic Hour MCP +5: framefields 77 (Read as a library. No OpenAPI or other formal contract; the package ships TypeScript declarations for every export and validates with zod, counted as 15 of 25 as for other SDKs (15). llms.txt at framefields.dev and a docs index at /docs/llms.txt with a Markdown version of every page and full and compact text files (10). Authoring rules, a workflow page and four skills say what to do and in what order, cheapest check first (15). Options are typed with enums, such as `quality` (very_low, low, high, very_high) and `codec` (h264, vp9, vp8), and job fields have defaults (12). Examples on every guide page; lint and QA codes, troubleshooting and worker error codes are each catalogued with a fix (14). Semantic versions with a changesets CHANGELOG.md in the repository, 2.4.0 to 2.12.0 added since 20 October; no GitHub releases and no changelog page on the site (11).); Magic Hour MCP 82 (All 50 tools read from tools/list with JSON Schema inputs and 29 enums, built from Magic Hour's OpenAPI specification (25). llms.txt (10). Long descriptions with a get_workflow_guide tool for choosing between them (17 of 20). Typed inputs with enums and no free-form objects (15). Worked examples; error responses not documented (5 of 15). Dated changelog with entries on 3 to 5 November 2026 (10 of 15, product changelog rather than MCP versions). 25 + 10 + 17 + 15 + 5 + 10 = 82.)
- Payments & pricing, framefields +5: 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.); Magic Hour MCP 15 (No machine payment protocol (0). Plan and credit-pack prices public, per-tool credit costs not read (10). 400 sign-up credits with no card, but API access sits on paid plans (5 of 20). A person signs up for a key in a browser (0). Tool discovery is open, but calls need a key (0). 0 + 10 + 5 + 0 = 15.)