AnimateMyTravel MCP server

• Registry namecom.animatemytravel/studioverified in the MCP registry

The registry name sits under animatemytravel.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-19
• Tools15
• Server calls itselfanimatemytravel-studio
• Server version1.1.0
• Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 220 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score77 of 100answers 100 · definitions 87 · context 100 · lowered by the warning signs below
• Answered100% of days8 of 8 daily checks
• Median first answer583 ms
• Space in an agent's context≈ 2,175 tokensthe definitions of all its tools (15), which an agent carries on every turn
• Tool definitionsB · 87 of 100
• Typed results0 of 15 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 12 of 15

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• studio_create_project

  Creates an anonymous project and returns the Studio link for the person plus an agent token for later edits. In one call it can start from a template (studio_list_templates), a guide example (studio_list_examples) or your own actions…

• studio_join_project

  Consumes a five-minute one-time pairing code shown by Studio.

• studio_list_capabilities

  Lists the live action registry. Call this before preparing or modifying a project.

• studio_describe_capabilities

  Returns schemas and examples for one or more Studio actions.

• studio_get_project_summary

  Reads the current revision and a compact timeline summary. Set includeProject only when complete raw data is needed.

• studio_apply_actions

  Atomically applies one or more registered actions. Non-conflicting stale edits are rebased; conflicting edits are rejected.

• studio_validate_project

  Checks entity, track, clip, timing, and reference integrity.

• studio_get_guide

  Everything needed to build a story in one read: the fastest paths, how pieces combine (frame, shapes, move, mark, say, link, data, look), a complete example and the actions with their schemas. Read it once before building from scratch.

• studio_list_templates

  Ready-made stories to fill in (a trip with stops, visited countries, an invasion, a growing empire, World War I and II, data maps, breaking news…). Pass one to studio_create_project as template { id, values }; values not given keep the…

• studio_list_examples

  Finished stories from the guides (a wildfire spreading, the euro year by year, a bar chart race, a war map, a train trip…). Start from one with studio_create_project example, then adapt places, texts and numbers with studio_apply_actions.

• studio_find_places

  Real coordinates for cities, towns and landmarks ([lat, lng], from OpenStreetMap) and the countries Studio can draw (with isoA2). Use it instead of guessing coordinates.

• studio_request_preview

  Asks an open Studio browser to render a frame locally.

• studio_request_export

  Asks an open Studio browser to render and download the video locally.

• studio_get_job

  Checks a local browser preview/export request.

• studio_export_json

  Returns the portable .amtstudio.json content without collaboration secrets.