ParkAlert MCP
ParkAlert MCP
一个 MCP 服务器,将迪士尼乐园的游乐设施状态和等待时间作为按需工具暴露出来, 由 ThemeParks.wiki API 提供支持。
这是 ParkAlert 的拉取式姊妹项目,
后者是一个 PWA,它按定时器轮询同一 API,并在游乐设施关闭或恢复时通过 ntfy.sh
推送通知。ParkAlert 回答“当有变化时告诉我”。这个服务器回答“现在是什么情况,因为我刚刚问了”。
API 客户端是从 ParkAlert 的 server/themeparks.js 移植过来的;轮询循环、
状态转换检测、行程代码和通知分发都被有意地留下。
工具
工具 | 参数 | 回答 |
|
| 这个游乐设施现在是在运营、关闭还是已停止? |
|
| 现在标准排队要等多久? |
两个工具都接受公园的名称、别名或 ThemeParks.wiki 实体 ID (“Magic Kingdom”、“dhs”、“epcot”),以及游乐设施的名称——支持模糊匹配, 例如“space mountain”或“tron”这样的部分和近似名称,如果有歧义, 会返回它可能指的是哪些候选。
支持的公园:Magic Kingdom、EPCOT、Hollywood Studios、Animal Kingdom、
Disneyland (CA)、California Adventure。要添加更多公园,请在
src/parkalert_mcp/parks.py 中追加到 PARKS。
Related MCP server: mcp-themeparks
设置
需要 Python 3.10 或更高版本(mcp SDK 的最低要求)。
python3.12 -m venv .venv
.venv/bin/pip install -e .运行
服务器使用 stdio 通信,因此由客户端启动,而不是作为常驻服务运行。 要手动测试:
.venv/bin/python -m parkalert_mcp.server对于交互式工具浏览器,MCP Inspector 可以针对同一命令运行:
npx @modelcontextprotocol/inspector .venv/bin/python -m parkalert_mcp.serverClaude Desktop
将服务器添加到 ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"parkalert": {
"command": "/Users/austin/parkalert-mcp/.venv/bin/python",
"args": ["-m", "parkalert_mcp.server"]
}
}
}虚拟环境中 Python 的绝对路径很重要:Claude Desktop 不通过登录 shell 运行,
因此裸 python 无法解析到这个环境。编辑后重启 Claude Desktop,
然后在连接器图标下查找这些工具。
致谢
由 Austin Vodrazka 使用 Claude 构建。
Available Tools
2 toolsget_ride_statusA
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.
Inputs: park (required), ride (required).
get_wait_timeA
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.
Inputs: park (required), ride (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored 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.
Maintenance
Related MCP Connectors
Live Disney World & Disneyland wait times, dining drop alerts & Lightning Lane auto-booker.
Live ride status and wait times at 140 theme parks, with local time and weather.
Live Disney and Universal waits, Lightning Lane, best times, ride facts and crowds from Parky.
Live Walt Disney World waits, crowd forecasts, Lightning Lane sellouts and prices, dining drop odds.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides access to Disney parks data including attractions, dining locations, height requirements, Lightning Lane status, and other park information for Walt Disney World and Disneyland resorts through structured queries and fuzzy search.72MIT
- AlicenseNot gradedqualityCmaintenanceEnables access to live theme park wait times, schedules, and attraction data from ThemeParks.wiki.74 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables management of Atlassian Statuspage incidents, components, and subscribers through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying 80+ theme parks and destinations worldwide for their attractions, live ride wait times and statuses, and operating hours or show schedules through the ThemeParks parksapi library.MIT