ParkAlert MCP
ParkAlert MCP
Disney 놀이기구 운행 상태와 대기 시간을 온디맨드 도구로 제공하는 MCP 서버로, ThemeParks.wiki API를 기반으로 합니다.
이 서버는 ParkAlert의 풀(pull) 기반 형제 프로젝트입니다.
ParkAlert는 동일한 API를 타이머로 폴링하고, 놀이기구가 중단되거나 복구되면 ntfy.sh를 통해
알림을 푸시하는 PWA입니다. 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"]
}
}
}venv의 Python 절대 경로가 중요합니다. Claude Desktop은 로그인 셸을 거치지 않으므로
단순한 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