mcp-themeparks
ThemeParks.wiki MCP — live theme park wait times, schedules, and attraction data.
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Power your agent
URL của chính nhà phát hành. Không phải endpoint của PlugMCP.
Host a copy with our keys and logs.
https://gateway.pipeworx.io/themeparks/mcpNút Claude ở trên mở Claude với tên và URL đã được điền sẵn. Bạn vẫn cần xác nhận tại đó.
claude mcp add --transport http io.github.pipeworx-io-themeparks https://gateway.pipeworx.io/themeparks/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-themeparks": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/themeparks/mcp" ] } }}claude_desktop_config.json
URL từ xa hay một lệnh trên máy của bạn? Hai cách cài đặt khác nhau thế nào
Chạy trên PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
MởTừ nhà phát hành
ThemeParks.wiki MCP — live theme park wait times, schedules, and attraction data.
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
ThemeParks.wiki MCP — live theme park wait times, schedules, and attraction data. Keyless. Covers…
| Tool | Description |
|---|---|
list_destinations | List all theme park destinations (Disney, Universal, Six Flags, SeaWorld, etc.) and their parks. Use this first to discover the PARK entity id, then feed that id to get_wait_times / get_schedule / get_entity. |
get_wait_times | Live theme park wait times — how long is the wait for an attraction right now. Returns standby and single-rider ride queue minutes plus operating status for every attraction in a park (e.g. Disney / Universal ride queues). Pass a PARK entity_id from list_destinations. |
get_schedule | Park operating hours — opening and closing times for a theme park over the coming weeks. Pass a PARK entity_id from list_destinations. |
get_entity | Metadata for any theme park entity (destination, park, attraction, restaurant, or show): name, type, location, timezone, and parent ids. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"themeparks": {
"url": "https://gateway.pipeworx.io/themeparks/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/themeparks/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/list_destinations \
-H 'Content-Type: application/json' \
-d '{}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_destinations. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"themeparks": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-themeparks"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-themeparks
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Themeparks data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
ThemeParks.wiki MCP — live theme park wait times, schedules, and attraction data. Keyless. Covers…
{ "mcpServers": { "io.github.pipeworx-io-themeparks": { "url": "https://gateway.pipeworx.io/themeparks/mcp", "headers": {} } }}Công cụ
Chưa có danh sách công cụ. Máy chủ từ xa sẽ có danh sách sau lần kiểm tra tình trạng đầu tiên.
Câu hỏi thường gặp
Sao chép cấu hình http cho Cursor, Claude Desktop, Claude Code hoặc VS Code trên trang này. Cấu hình dùng bản cài đặt của nhà phát hành, không phải proxy của PlugMCP.
Nhà phát hành liệt kê các biến môi trường sau: PIPEWORX_API_KEY.
Themeparks được truy cập qua HTTP.
Kiểm tra lần cuối: 2026-11-13. ThemeParks.wiki MCP — live theme park wait times, schedules, and attraction data. Keyless. Covers…