This server exposes Disney ride status and wait times as on-demand MCP tools, backed by the ThemeParks.wiki API.
get_ride_status: Check whether a Disney ride is currently operating, down, or closed, including standby wait and today's park hours.
get_wait_time: Get the current standby wait time in minutes for a Disney ride.
Supports six Disney parks: Magic Kingdom, EPCOT, Hollywood Studios, Animal Kingdom, Disneyland (CA), and California Adventure.
Accepts park names, aliases, or entity IDs, and matches ride names by partial or near-miss wording (e.g., "space mountain", "tron").
Returns resolved park/ride names, status codes with plain-English glosses, and wait times; distinguishes down/closed/virtual queue from no posted wait.
Ambiguous ride names return candidate matches instead of failing.
Runs over stdio and is designed for MCP clients like Claude Desktop.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ParkAlert MCP What's the standby wait for Rise of the Resistance at Hollywood Studios?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that exposes Disney ride status and wait times as on-demand tools, backed by the ThemeParks.wiki API.
This is the pull-based sibling of ParkAlert,
a PWA that polls the same API on a timer and pushes a notification through ntfy.sh
when a ride goes down or comes back up. ParkAlert answers "tell me when something
changes." This server answers "what is the situation right now, because I just asked."
The API client is ported from ParkAlert's server/themeparks.js; the polling loop,
the transition detection, the trip codes, and the notification fan-out are all
deliberately left behind.
Tool | Arguments | Answers |
|
| Is this ride operating, down, or closed right now? |
|
| How long is the standby line right now? |
Both tools accept a park by name, alias, or ThemeParks.wiki entity ID ("Magic Kingdom", "dhs", "epcot"), and a ride by however a person would say it. Partial and near-miss names such as "space mountain" or "tron" are matched, and an ambiguous name comes back with the candidates it could have meant.
Supported parks: Magic Kingdom, EPCOT, Hollywood Studios, Animal Kingdom,
Disneyland (CA), California Adventure. Add more by appending to PARKS in
src/parkalert_mcp/parks.py.
Related MCP server: Disney Parks MCP Server
Requires Python 3.10 or newer, which is the mcp SDK's floor. Note that the
system python3 on macOS may well be older than that, so name the interpreter
explicitly rather than relying on whatever python3 resolves to.
python3.12 -m venv .venv
.venv/bin/pip install -e .requirements-lock.txt records the exact versions this server is known to work
against, captured from a working environment. It exists because the dependency
that matters here is a moving target: mcp 2.0 renamed FastMCP to MCPServer,
so a rebuild that quietly resolved to a different major version would fail at
import with no hint as to why. To reproduce the known-good environment instead of
resolving fresh versions:
python3.12 -m venv .venv
.venv/bin/pip install -r requirements-lock.txt
.venv/bin/pip install --no-deps -e .Regenerate the lockfile after changing dependencies:
.venv/bin/pip freeze --exclude-editable > requirements-lock.txtThe --exclude-editable flag is load-bearing. A plain pip freeze writes this
project back out as a -e git+https://...@<commit> line, which would send a
future rebuild off to clone the repository rather than installing the checkout
already in hand.
.venv/bin/pip install -e ".[dev]"
.venv/bin/python -m pytestThe suite covers the two functions that decide what a caller's words mean:
find_attraction in themeparks.py and resolve_park in parks.py. Both run
offline, against a capture of real Magic Kingdom and EPCOT attraction data frozen
in tests/conftest.py. The tests therefore describe the matching rules and their
precedence, not today's ride list, and a ride opening or closing upstream will not
turn them red.
One test does reach the network. It fetches /live for all six park entity IDs
and asserts that each still returns attractions, which is precisely the failure
the offline tests cannot see. It is marked network and deselected by default,
so it runs only when asked for:
.venv/bin/python -m pytest -m networkThe server speaks stdio, so it is launched by its client rather than run as a long-lived service. To exercise it by hand:
.venv/bin/python -m parkalert_mcp.serverFor an interactive tool browser, the MCP Inspector works against the same command:
npx @modelcontextprotocol/inspector .venv/bin/python -m parkalert_mcp.serverAdd the server to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"parkalert": {
"command": "/Users/austin/parkalert-mcp/.venv/bin/python",
"args": ["-m", "parkalert_mcp.server"]
}
}
}The absolute path to the venv's Python matters: Claude Desktop does not run through
a login shell, so a bare python would not resolve to this environment. Restart
Claude Desktop after editing, then look for the tools under the connectors icon.
Built by Austin Vodrazka with Claude.
Check whether a Disney ride is currently operating, down, or closed.
Use this for "is X broken / open / running right now" questions. Returns the live status straight from ThemeParks.wiki along with the ride's current standby wait and today's park hours for context.
Args: park: Park name, alias, or ThemeParks.wiki entity ID. One of: Magic Kingdom, EPCOT, Hollywood Studios, Animal Kingdom, Disneyland (CA), California Adventure. ride: Attraction name as a person would say it; near-misses and partial names such as "space mountain" or "tron" are matched.
Returns: A dict with the resolved park and ride names, the status code and a plain-English gloss of it, the standby wait in minutes (None when the ride is not posting one), and today's opening/closing times.
| Name | Required | Description | Default |
|---|---|---|---|
| park | Yes | ||
| ride | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals that the data is live from ThemeParks.wiki, what is returned (status code, plain-English gloss, standby wait, park hours), and that wait times may be None when not posted. It also explains fuzzy ride-name matching, which is useful behavioral context beyond the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and front-loaded: the key use case appears first, followed by the live data source, then the two arguments, then the detailed return value shape. Each sentence contributes useful information without unnecessary filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there is no output schema and no annotations, the description gives enough context for the agent to call the tool correctly: park values, ride matching behavior, semantic meaning of status and wait, and the shape of the response. It lacks the exact status-code enumerations, but the gloss is mentioned so the agent can interpret the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description fully compensates for the 0% schema coverage. It explains that park accepts names, aliases, or entity IDs, lists valid Disney parks, and clarifies that ride accepts natural-language names and near-misses. This is far richer than the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a precise verb and resource: 'Check whether a Disney ride is currently operating, down, or closed.' This clearly defines the tool's purpose and differentiates it from get_wait_time, since the core output is ride status rather than only a wait time.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use this for 'is X broken / open / running right now' questions, which is strong usage guidance. It doesn't explicitly tell the agent to use get_wait_time when only wait time is needed, but the primary use case is clear enough that an agent can infer the distinction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the current standby wait time, in minutes, for a Disney ride.
Use this for "how long is the line for X" questions. This is the posted standby wait only; Lightning Lane and virtual queue times are not included.
Args: park: Park name, alias, or ThemeParks.wiki entity ID. One of: Magic Kingdom, EPCOT, Hollywood Studios, Animal Kingdom, Disneyland (CA), California Adventure. ride: Attraction name as a person would say it; near-misses and partial names such as "space mountain" or "tron" are matched.
Returns:
A dict with the resolved park and ride names, the standby wait in
minutes, and the ride's status. wait_time_minutes is None when no wait
is posted, which is normal for a ride that is down, closed, or run as a
walk-up or virtual queue; check status to tell those apart.
| Name | Required | Description | Default |
|---|---|---|---|
| park | Yes | ||
| ride | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden, and it does well by explicitly stating the return value structure: 'wait_time_minutes is None when no wait is posted' and guides interpretation via 'check status to tell those apart.' It also mentions the tool performs name resolution and returns resolved names. The only minor gap is not disclosing any potential side effects or network calls, which are likely irrelevant here, but overall this is a strong behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with clear sections (summary, usage context, args, returns). It front-loads the core purpose and then provides necessary details. It is appropriately sized given the complexity and provides all necessary information without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's relative simplicity (2 string params, no output schema), this description is complete. It explains return semantics (None case and status field), gives examples of accepted input formats, and lists all valid park values. An agent has everything needed to call this tool correctly and interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, and it does: park gets a full list of accepted values and the concept of aliases/entity IDs, while ride explains fuzzy matching behavior with examples. This goes far beyond the schema's minimal definitions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb and resource: 'Get the current standby wait time, in minutes, for a Disney ride.' It goes beyond a simple definition by specifying the unit, the scope (standby only), and explicitly excluding Lightning Lane and virtual queue times, which also differentiates its behavior from siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a direct usage example ('use this for "how long is the line for X" questions') and clarifies what the tool does not cover (Lightning Lane, virtual queue). While it doesn't explicitly mention the sibling tool get_ride_status by name or provide when-to-use-exclusions beyond wait time, the context is clear enough for typical scenarios, though it could be more explicit about when to prefer the sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0get_ride_statusget_wait_timeScored across 2 tools
The two tools accept the same park/ride arguments and both return status plus wait time, so an agent could reasonably pick either for a wait or status question. However, the descriptions clearly steer status checks to get_ride_status and wait-time questions to get_wait_time, reducing confusion.
Both tools follow the same get_<resource>_<metric> pattern: get_ride_status and get_wait_time. The naming is predictable and mirrors the two core queries perfectly.
Two tools is on the thin side for a general-purpose MCP server, but the scope is intentionally narrow: live Disney ride status and standby wait times. The count feels minimal but not unreasonable for that focused domain.
The core domain is covered: agents can check whether a ride is operating, down, or closed, and get standby wait minutes with status context to interpret Nones. Minor gaps exist, such as no way to list all rides in a park, but the main user intents are served.
Get real-time bus arrival times for any Singapore bus stop by code, with optional service filterin…
Look up Pokémon, moves, abilities, items, natures, and type matchups from PokéAPI v2.
Provide real-time transportation data including bus arrivals, train service alerts, carpark availa…
Interact with the Stitch API using natural language commands.