The whole resort, run through an MCP server. Sierra’s app and website can be operated by an AI agent through one set of tools: ask it to update a lift, and the app and sierraattahoe.com both change within seconds, with the change logged.
The problem
A ski resort’s day is a string of status changes: a lift on wind hold, a gate opening, a lodge closing early. Guests check the website, the app and the trail map, and each one has to say the same thing. When those surfaces are kept up by hand, in separate tools, they drift, and guests stop trusting all of them.
What we built
One Laravel backend at app.sierraattahoe.com runs the Sierra-at-Tahoe app on iOS, Android and the web, plus an Apple Watch app. Resort data (lifts, trails, snow, weather) comes from Sierra’s own WordPress site, and changes sync both ways between the two.
On top of that sits an MCP server: the same operations the staff admin offers, exposed as tools an AI agent can call.
- Operations. Open or close lifts, trails, Huckleberry gates and terrain parks; set hours and storm-day closures; check the connection to the website.
- Guests. Send push notifications to a chosen audience, answer feedback, look up riders, grant XP for service recovery.
- Commerce. Keep dining venues the same on the website and in the app, manage mobile ordering notices, rewards and the store.
- Reporting. Engagement, leaderboards, most-skied trails and weather, read from live data.
How it stays safe
An agent with the keys to a resort needs rules, so the server enforces them rather than trusting the agent.
- Every call is audit-logged: who called which tool, when, and the outcome.
- Destructive actions come back as a preview first, with a token the same call must repeat to go through.
- Status changes are version-stamped, and an optional key stops a repeated request from changing anything twice.
- Guests’ privacy holds here too. The live map counts riders on the mountain, but only people who opt in appear by name.
The result
Sierra’s team can run the mountain by asking for what they want. Lift and trail updates are the everyday example: when a lift goes on wind hold, one request updates that lift and the trails it serves in the app and on sierraattahoe.com at once, and the log shows who asked.
“Throughout our website build, Justin and the Zao team solved the big problems we brought them, then kept going, creating solutions I wouldn’t have thought to ask for that save my team time. When we decided to build a new mobile app, they were the obvious call. What they delivered is a powerhouse: fully integrated with our website and something our guests are going to lean on all season. We can’t wait to get it in their hands. I look forward to every chance I get to work with Justin and his team, and I recommend them without hesitation.”
Sarah Sherman, Director of Sales + Marketing, Sierra-at-Tahoe