Supersaas

@supersaas list all schedules and show me which ones have appointments this week

Found 4 schedules in your SuperSaaS account: 'Team Consultations' (ID: 12345), 'Equipment Booking' (ID: 12346), 'Training Sessions' (ID: 12347), and 'Conference Rooms' (ID: 12348). Based on the schedule metadata, 'Team Consultations' and 'Conference Rooms' appear to have active bookings this week. Note that this MCP provides schedule configuration details but doesn't directly access appointment data—you'd need to query appointments separately for each schedule to see exact booking counts.

This example demonstrates the List Schedules tool combined with AI reasoning to help navigate your booking infrastructure. The MCP returns schedule IDs and names but doesn't automatically fetch appointment details—you'll need follow-up queries per schedule. Useful for account discovery when you're managing multiple booking calendars.

@supersaas create a new user named 'Jordan Chen' with email jordan@example.com and add them to the 'Premium Members' group

Successfully created user 'Jordan Chen' (ID: 98765) with email jordan@example.com in your SuperSaaS account. The user has been registered and can now make bookings. To add them to the 'Premium Members' group, you'll need to update their user record with the appropriate group assignment—this requires a separate update operation since group membership is managed through user field updates rather than the initial creation call.

This showcases the Create User tool's write capability. SuperSaaS separates user creation from group assignment, so you'll typically need a two-step workflow for full onboarding. The MCP requires an API key with user management permissions. Be aware that creating users directly affects your account's user count and may impact billing.

@supersaas check what custom fields are configured for our 'Team Consultations' schedule and suggest which ones we should require for new bookings

The 'Team Consultations' schedule (ID: 12345) has 5 custom fields configured: 'Project Name' (text), 'Department' (dropdown), 'Meeting Type' (radio), 'Special Requirements' (textarea), and 'Budget Code' (text). Based on typical consultation workflows, I'd recommend making 'Project Name', 'Department', and 'Meeting Type' required fields—these provide essential context for resource allocation. 'Special Requirements' should stay optional for flexibility, while 'Budget Code' depends on whether you need financial tracking for every booking.

This example pairs the List Field List tool with AI analysis to help optimize your booking forms. The MCP reveals your schedule's custom field configuration, which is crucial for understanding what data you're collecting. Requires the schedule ID, which you can get from List Schedules. This read-only query won't modify your form structure.

When SuperSaaS MCP makes sense for client intake automation

A 3-person consulting firm books discovery calls and onboarding sessions through SuperSaaS. They want ChatGPT to create new client records and assign them to the right schedule when intake forms arrive via email. This MCP is the right call if you're already using SuperSaaS as your booking system and need to automate user creation or schedule assignment based on external triggers. The Create User and List Schedules tools handle the core workflow. The trade-off: if you're managing more than basic user fields or complex booking rules, you'll hit the API's limits quickly—SuperSaaS isn't built for heavy automation. This works when your intake volume is under 50 users per week and your scheduling logic is straightforward. If you're triaging hundreds of bookings or need conditional slot logic, look at a dedicated CRM integration instead.

Using SuperSaaS MCP for promotion code troubleshooting

A 5-person SaaS support team fields questions about promotional codes that unlock discounted booking slots. They want ChatGPT to pull up active promotions and verify codes without switching to the SuperSaaS admin panel. The List Promotions tool is purpose-built for this: it returns all active codes or checks a specific one. This MCP wins when your support reps are already in a shared AI workspace and the promotion catalog is under 100 codes—beyond that, search gets clunky because the tool doesn't filter by date or status. The real value is speed: a rep can verify a code in 10 seconds instead of logging into a separate dashboard. If your promotion strategy is simple (seasonal codes, referral discounts), this handles 80% of support queries. If you're running complex tiered promotions or need audit trails, you'll still need the full SuperSaaS interface.

When SuperSaaS MCP falls short for member data management

A boutique fitness studio uses SuperSaaS to book classes and wants ChatGPT to update member profiles when payment status changes in Stripe. The Get User and Delete User tools exist, but there's no Update User tool in this MCP—you can create or delete, but not modify existing records. This is a dealbreaker for most membership workflows. If your use case is purely additive (onboarding new members, pulling rosters for attendance checks), the MCP works. But if you need to flag inactive members, update contact info, or sync billing changes, you'll have to delete and recreate users, which breaks booking history. The threshold: if member updates happen more than once a month per user, this MCP isn't the right tool. You're better off using SuperSaaS webhooks or a Zapier-style integration that supports full CRUD operations.