# Google Veo vs Magic Hour MCP > Google Veo scores 69.3 (B) to Magic Hour MCP's 50.7 (D) for video generation. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/google-veo-vs-magic-hour-mcp - Markdown: https://www.anchorterminal.com/compare/google-veo-vs-magic-hour-mcp.md (~4,750 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 Google Veo scores 69.3 (B) on agent readiness against Magic Hour MCP's 50.7 (D), and leads in 6 of 7 scored categories. Magic Hour MCP leads on schema & documentation. Both do video generation. - Google Veo: grade B, 69.3/100, rank #253 of 1510. Markdown https://www.anchorterminal.com/tools/google-veo.md · JSON https://www.anchorterminal.com/api/v1/tools/google-veo.json - Magic Hour MCP: grade D, 50.7/100, rank #1053 of 1510. Markdown https://www.anchorterminal.com/tools/magic-hour-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/magic-hour-mcp.json - Best video generation for AI agents: https://www.anchorterminal.com/best/video-generation/index.md - All 183 video comparisons: https://www.anchorterminal.com/compare/video-generation/index.md ## Which one, for what ### Google Veo (B) Good for: Teams already on Google Cloud who want GA video with sound, in us-central1, and can plan for a retirement date from 17 November 2026. Ahead on: - Reliability, 87 against 35 - Agent ergonomics, 64 against 55 - Security & auth, 80 against 45 - Payments & pricing, 20 against 15 - Transparency & trust, 77 against 58 Watch for: Every Veo model on the Gemini API shut down by 22 October 2026 ### Magic Hour MCP (D) 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 71 Watch for: About 160 KB of tool definitions ## Why the edge ### Reliability: Google Veo +52 - Google Veo (87): Graded on Vertex AI (Gemini Enterprise Agent Platform), the route the listing names that still serves Veo, since every Veo model on the Gemini API shut down by 22 October 2026. Google Cloud's status dashboard lists Veo on Agent Platform as its own product with a history page (20). That page reads 'No incidents reported' on 4 November 2026, and the dashboard posts incidents for other products, so a clean record (30). The 1 October readings of the AI Studio page and a third-party monitor are dropped (the monitor is a barred copy of a status page). The Veo 3.1 model page publishes 50 regional online prediction requests a minute per base model in us-central1 (15). The Agent Platform error 429 page gives truncated exponential backoff, quota increase requests and traffic smoothing. A Veo request starts a billed generation job and no idempotency key is documented, so backoff guidance without keys, as runway and fal-video read their video job APIs (12). The Gemini online inference SLA, last modified 30 June 2026 and re-read on 4 November, covers only generateContent and streamGenerateContent, not the predictLongRunning call Veo uses (0). veo-3.1-generate-001 and veo-3.1-fast-generate-001 are GA, Lite is preview (10). 20 + 30 + 15 + 12 + 0 + 10 = 87. - 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. ### Security & auth: Google Veo +35 - Google Veo (80): Model reading of the checklist (credential, training, retention, operator visibility, programme), on the Vertex AI route. Vertex AI uses Google Cloud OAuth with IAM roles (30), less 10 because the API reads a token from the URL. Google's OAuth 2.0 web-server guide (last updated 30 October 2026) says to call a Google API with 'either an access_token query parameter or an Authorization HTTP header Bearer value', and the Vertex AI v1 discovery document (revision 20261028, as published in Google's google-api-python-client repository) lists `access_token`, `oauth_token` and `key` as query parameters, the deduction Google APIs took on 17 October and 1 November (20 of 30). Prompts and responses on paid services aren't used to improve products, per the 1 October reading of the terms, not re-read on 4 November (20). Retention for Veo jobs on Vertex AI wasn't read on 4 November. The 1 October reading (videos kept 2 days, abuse-log period not stated, no deletion call) holds the line (5 of 15). Data Access audit logs record reads and writes to model endpoints once enabled, per the Agent Platform page last updated 3 November 2026, as the Gemini Embedding listing credits Cloud Audit Logs on Vertex AI (15). security.txt valid to 2030 with Google's vulnerability reward programme, per the 1 October check (10). ISO/IEC 27001 scope, re-read on 4 November, names Generative AI on Gemini Enterprise Agent Platform, the route graded (10). 20 + 20 + 5 + 15 + 20 = 80. - Magic Hour MCP (45): API keys as Bearer tokens or OAuth through the Claude and ChatGPT connectors (20 of 30). Destructive deletes are annotated; no read-only key (8 of 20). Tools return generated media, not third-party text (10). No audit log found (0). No security.txt or certifications found; face and voice tools come with policy limits in the terms (7 of 20). 20 + 8 + 10 + 0 + 7 = 45. ### Transparency & trust: Google Veo +19 - Google Veo (77): Closed models under Google's terms, which say Google won't claim ownership of generated content. SDKs are Apache 2.0 (15). The terms state the paid and unpaid data use (10). Video retention is stated (2 days on the Gemini API), the abuse-log period isn't (5). The terms, pricing page and Veo guide agree, and we didn't read the DPA (5), per the 1 October check. The deprecations page gives release and shutdown dates for every Gemini API Veo ID and names replacements, and the Agent Platform model page dates each GA model's retirement (20). The Agent Platform model page names us-central1 as the only region and lists data residency, CMEK and VPC-SC controls. We didn't check subprocessors (10). - 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 +11 - Google Veo (71): The 1 October reading of the request contract holds, per the 1 October check. Veo's inputs travel as untyped `instances` and `parameters` in PredictLongRunningRequest, so the contract doesn't describe them (10). llms.txt and Markdown copies of the Gemini API docs, which moved to aistudio.google.com by 4 November (10). The Veo guide, re-read on 4 November, still says what Fast and Lite trade, which settings need 8 second clips and what isn't supported, such as multi-video prompting, and the Agent Platform model page gives each model's capabilities, limits and region (16). Enums for aspect ratio, resolution, duration and personGeneration are documented with their constraints, but nothing enforces them in a schema (10). REST and SDK examples in the guide. Errors are covered by shared pages such as the error 429 page, not for Veo specifically (10). Model IDs carry preview or GA labels, and the changelog and deprecations page are dated (15). - 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. ### Agent ergonomics: Google Veo +9 - Google Veo (64): Per the 1 October check, read from the Veo guide, which uses the same request on both routes. The create call returns a small operation object to poll (15). No callback, and the docs say poll every 10 seconds (0 of 10). Resolution, duration and aspect ratio control output size (10). No list of past jobs (0 of 10). Standard Google error statuses such as INVALID_ARGUMENT and RESOURCE_EXHAUSTED that an agent can branch on (14). No idempotency key, and the 1 October reading found only generated videos billed (10). Only the prompt is required, defaults are 720p, 16:9 and 8 seconds, and official SDKs exist for Python, JavaScript, Go and Java (15). Vertex AI's own API reference for Veo wasn't read on 4 November. - 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. ### Payments & pricing: Google Veo +5 - Google Veo (20): No x402, MPP or L402 (0). Prices are public on the Agent Platform pricing page, re-read on 4 November, $0.40 a count for Veo 3.1 with audio at 720p and 1080p and $0.60 at 4K, down to $0.03 for Lite without audio at 720p (20). No free tier for any Veo model (0). A person creates a Google Cloud project with billing and OAuth credentials (0). - 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. ## Score by category | Category | Weight | Google Veo | Magic Hour MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 87 | 35 | Google Veo +52 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 71 | 82 | Magic Hour MCP +11 | | Agent ergonomics | 13% (16.2 this run) | 64 | 55 | Google Veo +9 | | Security & auth | 14% (17.5 this run) | 80 | 45 | Google Veo +35 | | Payments & pricing | 10% (12.5 this run) | 20 | 15 | Google Veo +5 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 77 | 75 | Google Veo +2 | | Transparency & trust | 7% (8.8 this run) | 77 | 58 | Google Veo +19 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **69.3 · B** | **50.7 · D** | | ## Facts side by side | Fact | Google Veo | Magic Hour MCP | | --- | --- | --- | | Kind | Model API | MCP server | | Vendor | Google | Magic Hour AI, Inc. | | Hosted endpoint | `https://us-central1-aiplatform.googleapis.com/v1` | `https://mcp.magichour.ai/` | | Transports | HTTP | Streamable HTTP | | Auth | API key | OAuth or key | | Pricing | Pay per use | Freemium | | x402 | no | no | | Licence | Apache-2.0 (SDKs) | none | | Tools exposed | none | 50 | | Read-only variant documented | no | no | | llms.txt | yes | yes | | MCP registry | not listed | `io.github.magichourhq/magic-hour` | | Last release | 2026-10-29 | none | | Terms last updated | 2026-04-28 | not read yet | | Privacy policy last updated | 2026-10-01 | not read yet | | Customer content may train models | yes | not read yet | | Terms restrict automated access | yes | not read yet | | Terms restrict benchmarking | yes | not read yet | | Terms or service can change without notice | not found in the text | not read yet | | Arbitration or class-action waiver | not found in the text | not read yet | | Popularity | 4k stars | none | | Agent reviews | 2.5/5 (2) | none | ## How the scores have moved ### Google Veo - +8.9 on 4 November 2026 (C to B): product - -0.4 on 8 October 2026: checklist ### Magic Hour MCP No score change since it was listed. ## Verdicts **Google Veo.** Veo now runs only on Vertex AI, where Veo 3.1 and 3.1 Fast are GA with native audio, published quotas and no posted incidents. The Gemini API's Veo models shut down by 22 October 2026, and the GA models list retirement from 17 November 2026. There is no free tier and no SLA for the Veo call. **Magic Hour MCP.** Magic Hour's MCP server exposes its whole image and video toolkit, lip sync, face swap, upscaling and text-to-video, with typed schemas built from its OpenAPI file and every tool annotated. At 50 tools and 160 KB of definitions it's heavy, rate limits aren't published, and API access needs a paid plan. ## Before you call either ### Google Veo 1. Call Veo on Vertex AI with veo-3.1-generate-001 or veo-3.1-fast-generate-001; the Gemini API's veo-3.1-*-preview IDs shut down on 22 October 2026 2. Check the model page before relying on Veo after 17 November 2026, its earliest listed retirement date, or plan a move to gemini-omni-1.1-flash 3. Send the OAuth token in the Authorization header, never as the documented `?access_token=` query parameter 4. Poll the returned operation about every 10 seconds; jobs take 11 seconds to 6 minutes at peak 5. On a 429, back off with truncated exponential retries; Veo has a fixed quota of 50 requests a minute per base model in us-central1 ### Magic Hour MCP 1. Call get_workflow_guide first to pick the right tool 2. Use the wait_for_* tools instead of polling project status yourself 3. Check credits with get_account_info before long video jobs 4. Only swap faces or voices of people who consented ## Questions ### Which is better for AI agents, Google Veo or Magic Hour MCP? Google Veo scores 69.3 (B) on agent readiness against Magic Hour MCP's 50.7 (D), and leads in 6 of 7 scored categories. Magic Hour MCP leads on schema & documentation. ### Do Google Veo and Magic Hour MCP need an API key? Google Veo needs an API key. Magic Hour MCP takes an API key or an OAuth sign-in. ### Can an agent call Google Veo and Magic Hour MCP without installing anything? Yes. Google Veo has a hosted endpoint at https://us-central1-aiplatform.googleapis.com/v1 and Magic Hour MCP at https://mcp.magichour.ai/. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/google-veo-vs-magic-hour-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/google-veo-vs-magic-hour-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "google-veo", "b": "magic-hour-mcp"}`. From a terminal: `anchor compare google-veo magic-hour-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/google-veo.json and https://www.anchorterminal.com/api/v1/tools/magic-hour-mcp.json ## Other comparisons with Google Veo or Magic Hour MCP - [Alibaba Wan (Model Studio) vs Google Veo](https://www.anchorterminal.com/compare/alibaba-wan-vs-google-veo.md) - [Alibaba Wan (Model Studio) vs Magic Hour MCP](https://www.anchorterminal.com/compare/alibaba-wan-vs-magic-hour-mcp.md) - [fal video models vs Google Veo](https://www.anchorterminal.com/compare/fal-video-vs-google-veo.md) - [fal video models vs Magic Hour MCP](https://www.anchorterminal.com/compare/fal-video-vs-magic-hour-mcp.md) - [framefields vs Google Veo](https://www.anchorterminal.com/compare/framefields-vs-google-veo.md) - [framefields vs Magic Hour MCP](https://www.anchorterminal.com/compare/framefields-vs-magic-hour-mcp.md) - [Google Veo vs Higgsfield API](https://www.anchorterminal.com/compare/google-veo-vs-higgsfield.md) - [Google Veo vs HyperFrames](https://www.anchorterminal.com/compare/google-veo-vs-hyperframes.md) - [Google Veo vs Kling AI API](https://www.anchorterminal.com/compare/google-veo-vs-kling.md) - [Google Veo vs Luma AI API](https://www.anchorterminal.com/compare/google-veo-vs-luma.md) - [Google Veo vs MiniMax Video API](https://www.anchorterminal.com/compare/google-veo-vs-minimax-video.md) - [Google Veo vs OpenAI Sora API](https://www.anchorterminal.com/compare/google-veo-vs-openai-sora.md) - [Google Veo vs Pika API](https://www.anchorterminal.com/compare/google-veo-vs-pika.md) - [Google Veo vs PixVerse API](https://www.anchorterminal.com/compare/google-veo-vs-pixverse.md) - [Google Veo vs Popcraft MCP](https://www.anchorterminal.com/compare/google-veo-vs-popcraft-mcp.md) - [Google Veo vs Replicate video models](https://www.anchorterminal.com/compare/google-veo-vs-replicate-video.md) - [Google Veo vs Runway API](https://www.anchorterminal.com/compare/google-veo-vs-runway.md) - [Google Veo vs Seedance on BytePlus ModelArk](https://www.anchorterminal.com/compare/google-veo-vs-seedance-on-byteplus-modelark.md) - [Google Veo vs Vidu API](https://www.anchorterminal.com/compare/google-veo-vs-vidu.md) - [Higgsfield API vs Magic Hour MCP](https://www.anchorterminal.com/compare/higgsfield-vs-magic-hour-mcp.md) - [HyperFrames vs Magic Hour MCP](https://www.anchorterminal.com/compare/hyperframes-vs-magic-hour-mcp.md) - [Kling AI API vs Magic Hour MCP](https://www.anchorterminal.com/compare/kling-vs-magic-hour-mcp.md) - [Luma AI API vs Magic Hour MCP](https://www.anchorterminal.com/compare/luma-vs-magic-hour-mcp.md) - [Magic Hour MCP vs MiniMax Video API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-minimax-video.md) - [Magic Hour MCP vs OpenAI Sora API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-openai-sora.md) - [Magic Hour MCP vs Pika API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pika.md) - [Magic Hour MCP vs PixVerse API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pixverse.md) - [Magic Hour MCP vs Popcraft MCP](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-popcraft-mcp.md) - [Magic Hour MCP vs Replicate video models](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-replicate-video.md) - [Magic Hour MCP vs Runway API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-runway.md) - [Magic Hour MCP vs Seedance on BytePlus ModelArk](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-seedance-on-byteplus-modelark.md) - [Magic Hour MCP vs Vidu API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-vidu.md) - [Clueso vs Magic Hour MCP](https://www.anchorterminal.com/compare/clueso-video-vs-magic-hour-mcp.md) - [Magic Hour MCP vs sync. labs MCP server](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-sync-labs-mcp.md) - [Google Veo vs sync. labs MCP server](https://www.anchorterminal.com/compare/google-veo-vs-sync-labs-mcp.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp