Planyo Online Booking

@planyo check availability for resource 12345 from March 15-20, then show me any blackout periods that might conflict

Based on the Planyo API response, resource 12345 appears available March 15-20 with no existing reservations blocking those dates. However, there's a blackout period March 17-18 (marked as 'maintenance window') that would prevent bookings. The resource shows open slots March 15-16 and March 19-20. This example illustrates how the MCP queries availability and blackout data in sequence to give you a complete booking picture.

This example combines two read operations (availability check + blackout fetch) to surface scheduling conflicts. Requires valid resource_id and API key with read permissions. Planyo's availability API returns time-granular data, so responses can be verbose for resources with hourly slots.

@planyo create a reservation for resource 12345 on March 19 from 2-5pm for customer Jane Doe, email jane@example.com

Reservation created successfully. Planyo returned reservation ID 98765 for resource 12345, scheduled March 19, 14:00-17:00. Customer Jane Doe (jane@example.com) will receive a confirmation email per your site's notification settings. This example shows the MCP executing a write operation that commits data to Planyo's live system—the reservation now appears in your dashboard and triggers any configured workflows.

This write operation creates a real booking in your Planyo account. Requires API key with reservation-creation permissions. Side-effect: customer receives email, resource becomes unavailable for that slot, and any payment/deposit rules in your Planyo config apply immediately. Always verify availability first.

@planyo pull reviews for resource 12345 and draft a short marketing blurb highlighting the top-rated aspects customers mention

Fetched 23 reviews for resource 12345 (average rating 4.6/5). Customers consistently praise the 'spotless condition' (mentioned in 18 reviews) and 'responsive host communication' (14 mentions). Draft blurb: 'Guests love our meticulously maintained space and our team's quick responses—rated 4.6/5 by over 20 recent visitors.' This example demonstrates the MCP retrieving structured review data, then using AI reasoning to synthesize customer sentiment into marketing copy.

This synthesis example pairs Planyo's review API with the AI's summarization capability. Useful for generating social proof or identifying service gaps. Note that review volume and detail vary by resource—newly listed resources may return empty datasets. Requires read permissions on reviews.

When Planyo MCP works for daily desk reservations

A 6-person operations team managing a 40-desk coworking space uses Planyo to handle member bookings. The MCP shines here because the team needs to check availability, create reservations, and apply member coupons without leaving their AI workspace during morning check-ins. The Get Resource Availability and Add Reservation tools handle the 80% case—walk-in requests and same-day changes. The coupon tool lets them apply discounts inline when members ask about pricing. The threshold: if you're managing complex multi-resource bundles (conference room plus catering plus AV), Planyo's native UI is faster because the MCP doesn't expose package logic. For straightforward desk and meeting-room bookings under 100 reservations per week, this MCP cuts your context-switching in half.

Why Planyo MCP falls short for high-frequency class bookings

A 3-person studio running 15 yoga classes per week tried using the Planyo MCP to manage drop-in reservations during peak hours. The problem: the MCP's 7 tools don't include batch operations or waitlist management, so handling 8 simultaneous booking requests for a single class means 8 separate Add Reservation calls. The Get Resource Blackouts tool helps block instructor time-off, but there's no way to auto-confirm from a waitlist when someone cancels. If your booking volume stays under 30 reservations per day and you're mostly doing admin tasks—adding users, checking reviews, pulling coupon reports—the MCP saves time. Above that threshold, you're better off keeping Planyo's dashboard open. This integration is for low-frequency booking workflows, not high-throughput class scheduling.

When this MCP speeds up guest communication for small hosts

A 2-person property management team handling 5 vacation rentals uses the Planyo MCP to answer guest inquiries in Slack without opening the booking dashboard. When a potential guest asks about availability for a long weekend, the team checks Get Resource Availability and Get Resource Reviews in one AI prompt, then drafts a response with pricing and recent feedback. The Add Reservation tool closes the loop if the guest confirms. The win: the entire inquiry-to-booking flow happens in the team's existing chat workspace. The limit: Planyo's API key auth means the MCP can't differentiate between team members, so audit trails show all actions under one account. If you need per-user attribution or you're managing more than 10 properties, the lack of granular permissions becomes a problem. For small hosts doing under 50 bookings per month, this MCP eliminates 70% of dashboard visits.