AI Video Atlas MCP server
online · 100% uptimecom.aivideoatlas/atlas·v1.0.0Plan AI video shots: model picks, sourced prompts, prompting guides and real $/s costs.
0 stars
Reviews
Write oneNobody has reviewed AI Video Atlas yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AI Video Atlas tools (10)
write = sends, deletes, buys or postsbest_promptFreeGet the full, sourced prompt that best matches a shot (free text or a slug from find_shot), optionally for a target model. Returns the exact prompt text as the creator posted it, the creator credit and source, the model it was made with, and factual adaptation notes when the target model differs (other Atlas shots on the target model and its current supported price). Atlas never claims how a prompt will perform on a model it was not made with; treat adaptation notes as guidance.
find_shotFreeSearch AI Video Atlas's library of 106 sourced AI video shots (real prompts that creators posted, with the model used, an estimated cost and a link to the original). Use this FIRST when the user describes a shot, scene, style or job ("product ad with a rotating can", "anime fight", "lip sync dialogue", "drone over mountains"). Filters: shot_type (ads, music, shorts, characters, product, cinematic, lipsync, anime), model (e.g. kling, veo, seedance), max_cost_usd (estimated cost of the clip; when the prompt states no length we use a 5-second clip). Returns prompt excerpts; call best_prompt with a slug for the full prompt. Do not use for prices alone (use get_prices) or for tools/workflows (use get_workflow).
fix_promptFreeAlias of refine_shot. Fix a generated shot that came out wrong. Pass the prompt you used, the model, the mode and what went wrong in plain words ("feet sliding", "face drifted", "line cut off", "too glossy", "label morphing"), plus optional frame notes. Returns a diagnosis, specific prompt changes (from Atlas craft fixes and a per-model failure-mode library, credited), a revised prompt, and an escalation ladder: same-model fixes first (prompt, seed/variation, references, duration), then a mode change, then a model switch only as a last resort with the consistency cost stated. Adapt the revised prompt to the user's voice; no generation is run.
get_guideFreePrompting guidance from AI Video Atlas, sourced from vendor prompting docs (Google, BytePlus, Runway, Luma, MiniMax, Alibaba, LTX, xAI, fal) plus proven Atlas examples. Pass model (kling, veo, seedance, runway, luma, hailuo, wan, ltx, grok-imagine…) for prompt structure, camera language, what the model responds to, things to avoid and known limits; or topic (shot-vocabulary, tagging, consistent-characters, i2v-vs-r2v, setup-playbooks). Every item carries its source URL; items marked atlas-editorial are our summary, not a vendor claim. Call with no arguments to list what exists. Use before writing a prompt for a specific model.
get_pricesFreeVendor-stated AI video prices per second from AI Video Atlas's tracker, each with its source URL and the date we checked it. Filter by model family or host. Legacy, deprecated and discontinued rows are excluded unless include_legacy=true (then they are flagged by status). Use for "how much does X cost", "cheapest model", or before quoting any cost.
get_workflowFreeHow-to workflows, tools and model guides for AI video, grouped by job: consistent-character (Keep a character consistent), lip-sync (Lip sync & talking heads), product-ad (Product ads & UGC), camera (Direct the camera), long (Longer & multi-shot videos), i2v (Animate a still image), edit (Edit or restyle footage), upscale (Upscale & smooth), local (Run it on your own GPU), models (Models & hosts). Pass job for a curated list, query for free text (e.g. "comfyui lipsync", "upscale to 4k"), or slug for one item in full. Returns sources, creators, license and price as stated.
plan_shotsFreeGoal: a usable take on the first generation, so fewer paid generations per shot. First review and rewrite the beat list (see brief_review): Atlas parses briefs with rules, so fix non-shots, missing subjects, placeholder lines and generic coverage before writing prompts. If the user names a model or mode, pass it in model/mode (it is kept for every shot unless the docs rule it out). Returns a GUIDANCE PACKAGE, not final prompts: you (the agent) write each full video prompt yourself from it. Per shot: model + mode decision with reasons, the per-model/per-mode prompt structure and tips, 2-3 credited proven example prompts, capabilities/limits/prices with sources, techniques and director rules (practitioner hints at low weight), required assets with image-gen guidance, an 11-section quality checklist, and a starter draft (starting point only, never paste it as-is). If the user names a model or mode, pass it in model/mode (or keep it verbatim in description): Atlas keeps it for every shot unless the vendor docs rule it out, and explains why in user_named. Write each final prompt as flowing, sectioned prose sentences (subject/action, camera/lens/movement, location/light/color, style, audio), never field labels like speaker_id: or Subject:, and without stock filler phrases. Also returns intake (questions to ask the user + stated assumptions) and package_markdown (readable). Plan a multi-shot AI video from a plain description (deterministic, built only from Atlas data; no AI generation). Output is staged: decide (model/mode/clip length/aspect/cost with reasons and capability checks), direct (shot list with per-model prompts), assets (every reference/frame with status needs-generation|user-supplied|approved), image_prompts, and steps, which include a STOP: get the user to approve assets before generating any video. Global directives (same X in every shot, vertical, no text, style) apply to all shots; questions and request wording are never planned as shots; an explicit shot count is honored; clips longer than an endpoint's documented max are split. The description is split into beats (sentences, clauses, and cues like "then", "cut to", "close-up", "wide"). For each beat it returns a shot type; a recommended model endpoint with its current vendor-stated $/s and source; the generation mode to use (t2v, i2v, reference-to-video, start/end frame, v2v, lip sync; only modes the vendor docs confirm) with a one-line reason; image prompts for any input frames, plus a shared character/product reference sheet when shots must match; an adapted prompt built from the best-matching sourced example (credited and linked), an estimated cost (5 s per shot by default), and a how-to workflow when one applies (lip sync, consistent character…). It also returns a total. budget_usd (total) and/or max_per_shot steer it to cheaper supported endpoints; each shot also offers a cheaper alternative with its cost, and the plan says if the budget can't be met. Use this for "plan / storyboard / make me a video of…" requests; use find_shot for a single shot. Before presenting, adapt the wording to the user's voice, context and brand (names, tone, product details), but keep the prices, models, modes, clip lengths and reference tags exactly as returned.
recommend_modelFreeRecommend which AI video model to use for a shot, with the evidence: how many sourced Atlas shots of that kind were made with each model, the cheapest supported vendor-stated $/s, and an estimated total for the clip length and number of clips. Pass budget_usd (total) and/or max_per_shot to drop models whose estimate exceeds it; over-budget models are listed with their cost. Each row includes the generation modes the vendor docs confirm (t2v, i2v, reference-to-video, start/end, v2v, lip sync; unknown where docs do not say). Legacy, deprecated and discontinued models are never recommended. Filters by the required mode FIRST (detected from the shot text or the mode argument; endpoints whose docs say unknown are excluded), then ranks the cheapest qualifying endpoint first and notes when a pricier one has more proof. Includes each endpoint's max clip length and splits long clips.
refine_shotFreeGet to a usable take in as few further generations as possible when a shot came out wrong. Pass the prompt you used, the model, the mode and what went wrong in plain words ("feet sliding", "face drifted", "line cut off", "too glossy", "label morphing"), plus optional frame notes. Returns a diagnosis, specific prompt changes (from Atlas craft fixes and a per-model failure-mode library, credited), a revised prompt, and an escalation ladder: same-model fixes first (prompt, seed/variation, references, duration), then a mode change, then a model switch only as a last resort with the consistency cost stated. Adapt the revised prompt to the user's voice; no generation is run.
whats_newFreeWhat is new in AI Video Atlas: the newest sourced shots and guides added in the last N days (default 7), newest first, with X like counts where we have them ("new" otherwise). Use for "what's new in AI video", weekly roundups, or trend questions. For the full weekly digest (new models, price changes, new shots, legacy prices) read https://aivideoatlas.com/digest/latest.json.
Public scan report
scanner v0.1.10 · 2026-10-12 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 687ms20/20
- Tool poisoning10 tool descriptions checked13/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; website matches verified namespace8/10
Findings (1)
- lowUnusually long tool description (over 2,000 characters)
poison.long-descriptiontool plan_shots: …Goal: a usable take on the first generation, so fewer paid generations per shot. First review and rewrite the beat list (see brief_review): Atlas parses briefs with rules, so fix non-shots, missing subjects, placeholder lines and generic coverage before writing prompts. If the user names a model or mode, pass it in model/mode (it is kept for every shot unless the docs rule it out). Returns a GUIDANCE PACKAGE, not final prompts: you (the agent) write each full video prompt yourself from it. Per shot: model + mode decision with reasons, the per-model/per-mode prompt structure and tips, 2-3 credited proven example prompts, capabilities/limits/prices with sources, techniques and director rules (practitioner hints at low weight), required assets with image-gen guidance, an 11-section quality checklist, and a starter draft (starting point only, never paste it as-is). If the user names a model or mode, pass it in model/mode (or keep it verbatim in description): Atlas keeps it for every shot unless the vendor docs rule it out, and explains why in user_named. Write each final prompt as flowing, sectioned prose sentences (subject/action, camera/lens/movement, location/light/color, style, audio), never field labels like speaker_id: or Subject:, and without stock filler phrases. Also returns intake (questions to ask the user + stated assumptions) and package_markdown (readable). Plan a multi-shot AI video from a plain description (deterministic, built only from Atlas data; no AI generation). Output is staged: decide (model/mode/clip length/aspect/cost with reasons and capability checks), direct (shot list with per-model prompts), assets (every reference/frame with status needs-generation|user-supplied|approved), image_prompts, and steps, which include a STOP: get the user to approve assets before generating any video. Global directives (same X in every shot, vertical, no text, style) apply to all shots; questions and request wording are never planned as shots; an explicit shot count is honored; clips longer than an endpoint's documented max are split. The description is split into beats (sentences, clauses, and cues like "then", "cut to", "close-up", "wide"). For each beat it returns a shot type; a recommended model endpoint with its current vendor-stated $/s and source; the generation mode to use (t2v, i2v, reference-to-video, start/end frame, v2v, lip sync; only modes the vendor docs confirm) with a one-line reason; image prompts for any input frames, plus a shared character/product reference sheet when shots must match; an adapted prompt built from the best-matching sourced example (credited and linked), an estimated cost (5 s per shot by default), and a how-to workflow when one applies (lip sync, consistent character…). It also returns a total. budget_usd (total) and/or max_per_shot steer it to cheaper supported endpoints; each shot also offers a cheaper alternative with its cost, and the plan says if the budget can't be met. Use this for "plan / storyboard / make me a video of…" requests; use find_shot for a single shot. Before presenting, adapt the wording to the user's voice, context and brand (names, tone, product details), but keep the prices, models, modes, clip lengths and reference tags exactly as returned.…
How AI Video Atlas compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 80% of 4,460 AI and agents servers
- Tools
- 10
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 1,206 ms
- faster than 6% of 2,331 AI and agents servers
What its tools let an agent do: 10 read
Install AI Video Atlas in Claude Code, Cursor or VS Code
claude mcp add --transport http atlas https://mcp.aivideoatlas.com/mcp
What the publisher says
From the AI Video Atlas repository's README, as published. We do not edit it. Read it on GitHub
AI Video Atlas MCP server
Give your AI agent a video director. This is the open-source MCP server (and REST API) behind AI Video Atlas. It lets Claude, ChatGPT, Cursor, Gemini, Grok Bot or any MCP client plan AI video shots, pick models, find sourced prompts, and price a clip using vendor-stated $/second, all from Atlas data.
- Live endpoint: https://mcp.aivideoatlas.com/mcp (streamable HTTP, no auth, free)
- REST API: https://mcp.aivideoatlas.com/v1/. The OpenAPI spec is at https://mcp.aivideoatlas.com/openapi.json.
- Agent guide: https://aivideoatlas.com/agents/
It's read-only and deterministic: no AI generation happens on the server, and every answer is built from Atlas's sourced data, with links back to the original creators and vendor pages.
Connect
Claude (web and desktop): open claude.ai → Settings → Connectors, click Add custom connector, name it AI Video Atlas and paste https://mcp.aivideoatlas.com/mcp. No sign-in is needed. On Team and Enterprise plans, an owner may need to add the connector first. Claude Code:
claude mcp add --transport http ai-video-atlas https://mcp.aivideoatlas.com/mcpChatGPT: custom MCP connectors need developer mode, a beta for paid plans (Pro, Business, Enterprise, Edu). It isn't available on Free. Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode. Then click Create, name it AI Video Atlas, paste the URL and set authentication to No authentication. Building a custom GPT instead? Go to Configure → Actions → Import from URL and use https://mcp.aivideoatlas.com/openapi.json.
Cursor: use the one-click "Add to Cursor" button on https://aivideoatlas.com/agents/, or add this to ~/.cursor/mcp.json:
{"mcpServers":{"ai-video-atlas":{"url":"https://mcp.aivideoatlas.com/mcp"}}}Gemini: Gemini CLI (free):
gemini mcp add --transport http ai-video-atlas https://mcp.aivideoatlas.com/mcpIn the Gemini app, custom connected apps are limited to Gemini Spark on personal Google accounts in the US (18+). If you have it, add a custom app with the URL above. Gems can't connect to outside tools.
Grok Bot: paste this into your Grok Bot chat:
Add this MCP server: name aivideoatlas, URL https://mcp.aivideoatlas.com/mcp (no key needed).Grok Bot confirms before adding it, and the tools are available from your next message.
Any MCP client / API: use the URL above (streamable HTTP, no auth). For plain HTTP:
curl "https://mcp.aivideoatlas.com/v1/find_shot?query=drone+shot&limit=3"VS Code, Windsurf and other MCP clients take the same URL.
Tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
AI Video Atlas: common questions
- Is AI Video Atlas MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the AI Video Atlas safety report
- How do I install AI Video Atlas?
- It runs remotely at mcp.aivideoatlas.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does AI Video Atlas need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is AI Video Atlas maintained?
- The last commit was 24 days ago (2026-10-11). The latest release is v1.0.0.
- Is AI Video Atlas up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of AI Video Atlas?
- Servers from other publishers that do the same job: llmtrim MCP server, Figma Context MCP server and Claude Real Video MCP server.
- How does AI Video Atlas compare with other AI and agents MCP servers?
- safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 10 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to AI Video Atlas
Same job from other publishers: the closest match first, then the best rated.
- llmtrimMCP server and proxy that compresses LLM prompts, tool output, and replies to cut token cost.not reviewedEstablishedA
- Figma ContextGive your coding agent access to your Figma data. Implement designs in any framework in one-shot.not reviewedWidely usedB
- Claude Real VideoLet any LLM watch a video locally — and search everything it has ever watched.not reviewedEstablishedA
- Agent-Native PlanStructured visual plans and PR recaps with diagrams, prototypes, annotations, and sharingnot reviewedEstablishedA
- Watch SkillWatch video and live sessions, keep timestamped evidence, and verify an agent's own work.not reviewedEstablishedB