Changelog

November 4, 2026

REST and MCP are one API

  • Every MCP tool is now one REST operation with the same name, inputs, answer and error codes. The tool name is the OpenAPI operationId; earlier ids stay in x-aliases and earlier paths in x-alias-of.
  • New endpoints: GET /v1/search, GET /v1/buses and GET /v1/parks/{park_id}/outages. Earlier bus and outage paths keep working.
  • ride_id is now a query parameter on waits, Lightning Lane and reliability.
  • Eight new MCP tools, 23 in all: parky_list_parks, parky_list_resorts, parky_get_resort, parky_list_park_rides, parky_get_park_ride, parky_get_crowd_actuals, parky_get_ride_history and parky_get_hotel_availability.
  • /mcp takes the same developer key as REST, with that key's limits.
  • MCP changes: parky_get_waits returns rides, not waits, in board order, with no cap or truncated flag. attribution is an object, not a string. Answers gain schema_version, docs_url and generated_at, and response_generated_at is gone. parky_get_ride_facts also returns live and reliability.
  • MCP limits now match REST: hours up to 60 days, park availability up to 31 days and 7 by default, replies up to 256 KB.
  • A required query parameter left out is now a 400 invalid_request.

October 5, 2026

Parky API launch

  • REST endpoints for parks, live waits, rides, hours, crowds, Lightning Lane, reliability and best times.
  • Showtimes and character meets, current weather and ride conditions, ride outages, observed crowds, and resort data: ticket prices, park reservations, hotel availability, event nights and Walt Disney World buses.
  • Live updates over WebSocket and Server-Sent Events.
  • Free keys with 120 requests a minute and 20,000 a day.
  • Eleven new MCP tools, fifteen in all: Lightning Lane, best time, ride reliability, ride facts, showtimes, outages, conditions, tickets, park reservations, buses and event nights.
  • Wait history: every change in a ride's posted wait over the last 7 days, at /v1/rides/{ride_id}/history.
  • Live streams now check for changes every 5 seconds, and live REST responses are at most 5 seconds old.
  • Readable, permanent IDs for every ride, show and meet (such as magic-kingdom_meet-mickey-at-town-square-theater). IDs sent before this change still work.