Parky — Park Planning
Find supported Disney and Universal parks and rides, check fresh posted waits and park hours, and explore crowd forecasts.
What it can do
- Parky Find Experience: Use this when a visitor names or describes a park or ride and you need its canonical Parky ID. Searches only parks in Parky's current Disney and Universal release scope. It does
- Parky Get Waits: Use this when a visitor asks for current posted ride waits or operating status at one supported park. Resolve the park ID first. Waits older than 30 minutes are unavailable, not curre
- Parky Get Hours: Use this when a visitor asks about operating hours for one supported park within the next seven park-local days. Resolve the park ID first. Schedule windows have guest-facing categori
What data it sees
Do you need an account
No: the server works without sign-in
Find supported Disney and Universal parks and rides, check fresh posted waits and park hours, and explore crowd forecasts. Read-only public connector for individual park planning.
How to connect
How to connect Parky — Park Planning to Claude
The server address to paste into Claude settings:
https://park-planning--parky.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Parky — Park Planning to ChatGPT
The server address to paste into ChatGPT settings:
https://park-planning--parky.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Parky — Park Planning to Cursor
The server address to paste into Cursor settings:
https://park-planning--parky.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (4)
Raw names from tools/list. Only developers need these.
| parky_find_experience | Use this when a visitor names or describes a park or ride and you need its canonical Parky ID. Searches only parks in Parky's current Disney and Universal release scope. It does not retrieve current wait times. |
| parky_get_waits | Use this when a visitor asks for current posted ride waits or operating status at one supported park. Resolve the park ID first. Waits older than 30 minutes are unavailable, not current; this tool does not predict future waits. |
| parky_get_hours | Use this when a visitor asks about operating hours for one supported park within the next seven park-local days. Resolve the park ID first. Schedule windows have guest-facing categories and labels; Early Entry is an eligibility-based window, not a separate ticketed event. These are reported schedules, which the operator may change. |
| parky_get_crowd_outlook | Use this when a visitor asks how crowded one supported park may be within the next 30 park-local days. Resolve the park ID first. Returns a forecast and range, not a guarantee or a live wait. |