Connect an AI assistant
Let Claude read your club data directly from ClubPal, so an admin can ask it questions instead of hunting through admin pages.
ClubPal can act as a connector for Claude, so you can ask an AI assistant things like "how many members are due to renew this month" or "what's booked in on Saturday" and get an answer drawn from your own club's data, without leaving the conversation. It works with both Claude.ai and Claude Code.
The connection is read-only and personal to the admin who sets it up: it can look things up, but it can never edit a member, take a payment, cancel a session or send anything on your behalf.
Before you start
- Your club has to turn it on first. AI assistant connections are off until an admin with the System Administrator permission switches on Allow AI Assistant Connections? under AI Assistant in Admin > Settings. Whatever an assistant reads, including members' details, is sent to the company that provides it, so it is the club's decision rather than one admin's, and worth checking against your club's privacy notice.
- You need admin access to your club. Connecting requires the same Access Administration permission that gets you into the admin area at all. See Permissions.
- What it can read follows your own permissions, not a fixed list. If you don't have Manage Payments, for example, it cannot answer questions about payments either, because it is acting as you.
- Nothing is written. Every question it can answer comes from a read-only lookup. There is no tool that changes a member, a booking, a payment or anything else.
Each connection belongs to one admin. If a colleague wants Claude to answer with their own permissions, they connect separately from their own account.
Connect from Claude.ai
- In Claude.ai, go to Settings > Connectors > Add custom connector.
- Paste in the connector address:
https://mcp.clubpal.app/mcp. - Sign in when prompted, following what happens at sign-in below.
Connect from Claude Code
Run:
claude mcp add --transport http clubpal https://mcp.clubpal.app/mcp
The first time you use it, Claude Code opens a browser to complete the same sign-in as Claude.ai.
Both routes use the same sign-in. There is no API key to generate or paste: it is your normal ClubPal login, the same way you'd sign in on the website.
What happens at sign-in
- You are asked to find your club. Start typing its name and pick it from the list. If you would rather, type its web address instead, either
myclub.clubpal.appor your club's own domain. This first step happens on ClubPal's connector, before you reach your club's own site. - You're taken to your club's own site to sign in, exactly as you would to reach the admin area.
- You're shown what's being connected and asked to Allow or Cancel. The screen names the profile whose permissions the connection will use, so check it before you allow.
- Click Allow, and you're sent back to Claude, connected.
If you're signed in under the wrong profile, for example a managed profile with no admin access, switch profile from the account menu at the top of the page, then start the connection again. See Linked profiles.
What it can answer
| Question you might ask | What it looks at | Needs |
|---|---|---|
| What club is this, and what's switched on? | Club name, website, time zone, currency, membership year and which features are enabled | Admin access |
| List or filter members, or look up one in full | Members and their profiles: any field, group or status you can filter on, but never payment details | View Members |
| How many members do we have, and what's our auto-renew rate? | Headline membership numbers, recomputed nightly | View Members |
| What membership types do we offer, and how many are on each? | Membership types (packages), prices and active counts | Manage Membership |
| How many memberships expiring this month will actually renew? | A renewals forecast for a date window, including how many have no working payment method | Manage Membership |
| List or filter memberships, not just the headline numbers | Individual memberships: type, status, expiry, auto-renew and card health | Manage Membership |
| List or filter sessions, bookings or attendance | Sessions, session occurrences, bookings and who attended, by date, session or member | Manage Sessions |
| How many people usually turn up to Monday's session? | Past attendance for a session, with the mean and median turnout | Manage Sessions |
| How much have we taken this month, after fees and refunds? | A payments summary for a date window, grouped by day, week, month or category | Manage Payments |
| List or filter individual receipts or payments | Receipts and payments: date, amount, category, member or method | Manage Payments |
| Who owes us money, and what's overdue? | Payment requests: who was asked for what and when it is due, whether it has been paid, cancelled or chased, failed automatic card charges, and whether an admin or a booking balance raised it | Manage Payments |
| What events have we got coming up, and which still have tickets left? | Events and each of their dates: when and where, who can see them, ticket price and capacity, and tickets sold and remaining for a date | Manage Events |
| Who's coming to the quiz night, and who has bought tickets? | Going, maybe and not going responses, and ticket orders with the names on each ticket, what was paid and whether the order is confirmed or still unpaid | Manage Events |
| Which orders still need sending out, and what did Sam order? | Store orders: who ordered what, the items and variations in each, what was paid, any discount code, checkout comments and admin notes, and whether the order is pending, processing, complete or cancelled | Manage Store |
| What are our best-selling products this season? | Every item sold through the store, by product and variation, with how many and at what price, leaving out cancelled orders the same way the Store's own figures do | Manage Store |
| Who has a valid swim pass, whose passes run out this month, and who has used theirs up? | Passes and who holds them: price, sessions allowed, how long each lasts, when each member's pass expires, sessions used and left, and whether it renews automatically | Manage Passes |
| What's booked in the hall next week, and which hires still owe a balance? | Facility hire bookings: facility, date and time, who booked it, package and price, whether it is confirmed or cancelled, and, once confirmed, what has been paid and what is still owed | Manage Facility Hire |
| When did our last payout arrive, and did any fail? | Payouts into the club's bank account: arrival date, amount, status and the reason for any failure | Manage Payments |
| How many, or how much, grouped by membership type, status, category, session, product, member or date | Counts and totals across any of the above, for example memberships by type, bookings by session, money owed by status or items sold by product | Whichever permission covers what's being counted |
| What can I ask about? | The kinds of records and fields available to this connection | Admin access |
| How do I do X in ClubPal? Can ClubPal do X? | ClubPal's own product documentation | Nothing extra, anyone connected can ask |
Ask it to start with "what club is this" if you want to see straight away which of your permissions it picked up, before asking anything more specific.
Examples
Each of these is a plain question you can type into Claude once connected. Claude decides which lookups to run; you never name them.
Planning a session
How many people should I expect at Tuesday's track session?
Claude finds Tuesday's instance, looks at the last eight times that session ran, and answers with the current booking count, the capacity, and the typical turnout (mean and median attended). Follow up with "is that up or down on last month". Claude can also list who's booked, who's on the waiting list and who attended, by name, and you can follow up on any of them.
Renewals
How many memberships expire in the next 60 days, and how many will actually renew?
You get the number expiring, how many have auto-renew on, and, of those, how many have no working card so the renewal will fail, broken down by membership type with the expected revenue. Claude can now list the members behind each number too, for example everyone whose membership expires in March with auto-renew on and no usable card. If more than 2,000 memberships expire in a single window, it lists the first 2,000 and says so.
Money
What did we take last month, and how does it split between sessions and memberships?
Claude runs a payments summary for the month grouped by category and reports gross, refunds, fees and net for each. Ask "and the month before" for a comparison, or "show me the largest receipts" to drill into individual payments.
Money owed
Who still owes us money, and how much of it is overdue?
Claude lists the outstanding payment requests by name, with the amount and due date, totals what is overdue, and points out any where an automatic card charge has failed. It uses the same rules as Admin > Payments > Outstanding Payments, so its Overdue and Needs Attention answers match the page. Follow up with "just the ones from last week's kit request" or "who has never been sent a reminder".
Payouts
Did we get paid out last week, and did anything fail?
Claude lists the payouts that arrived or were due in that week, with the amount and status of each, and gives the reason for any that failed. Ask "which payments were in that payout" to see the receipts it covered.
Events and tickets
How many tickets have we sold for the summer ball, and who hasn't paid yet?
Claude counts the confirmed tickets for each date and what they took, the same way Ticket Sales does, and lists any orders still waiting for payment. Ask "is there space left on the Saturday" for the tickets remaining on that date, or "who said they're going but hasn't bought a ticket" to compare the two lists. Private events only show up for the admin who created them, just as in ClubPal.
Store
Which orders haven't been sent out yet, and what are our top sellers since August?
Claude lists the orders still Pending or Processing, oldest first if you ask, with who ordered and how many items, and can open any of them to show the items, sizes, checkout comments and admin notes. For top sellers it adds up items sold by product over the dates you give, leaving out cancelled orders as Admin > Store does. Follow up with "what did Sam Jones order this year" or "how much did the summer kit code take off".
Passes
Whose swim passes run out this month, and which of them will renew?
Claude lists the members whose pass expires in the month, with how many sessions each has left, and picks out the ones set to renew automatically. It counts a pass as active the same way Admin > Passes does. Follow up with "who has used all their sessions" or "how many people hold each pass".
Facility hire
What's booked in the main hall next week, and which hires still owe a balance?
Claude lists next week's confirmed bookings for the hall with the times and who booked each one, then the hires with a balance still due, how much and when it is collected. Checkouts that were never paid are left out of both, as they are on Admin > Facility Hire > Bookings. Follow up with "how much has the hall taken this year compared with last" for the value of confirmed hires per facility.
Members
Find Sam Jones and tell me when their membership expires and which groups they're in.
A member search followed by the profile. Payment details are never included, whatever you ask.
Attendance
Which members came to more than five sessions this quarter?
Claude lists everyone who attended more than five times in the quarter, by name, with their attendance count. Follow up by asking for just one session's history, or for who used to come regularly and has stopped.
Renewals at risk
Who is going to fail to renew in March?
Claude lists everyone whose membership expires in March with auto-renew on and no usable card, so you know who to follow up with before they lapse.
Revenue comparison
How does revenue per session category this year compare with last year?
Claude totals revenue by session category for each year and lines the two up so you can see which categories grew and which fell back. Ask "and by month" to see where in the year the difference shows up.
Combining club data with the docs
Draft a reminder email to members whose membership lapses in March, explaining how auto-renew works.
Claude pulls the March renewals, then reads the ClubPal documentation on renewals to describe the process accurately, and drafts the text for you. It does not send anything: you copy the draft into an email yourself.
Asking about ClubPal itself
Can I take a deposit for a pitch booking, and how do I turn it on?
This one needs no club data at all. Claude searches the ClubPal docs and walks you through the facility hire settings.
Where it stops
Cancel Saturday's session and refund everyone.
Claude will tell you it cannot: the connection is read-only. It can tell you how many are booked and what the refunds would come to, and point you to Admin > Sessions to do it. Whatever you ask, Claude reads only the fields ClubPal chooses to share, never card details, and asks for nothing outside that list.
Disconnecting
Go to Admin > Connected Apps to see everything connected under your account, with the profile it uses and when it was last used, and disconnect anything you no longer want to have access.
Disconnecting takes effect straight away: it stops the assistant answering anything new within a minute, everywhere. It does not affect anyone else's connection, only the one you disconnect.
To stop every admin's assistant at once, a System Administrator can switch off Allow AI Assistant Connections? in Admin > Settings. Connections stop answering on their next question, and start working again if the setting is turned back on.
Because the connection acts as you, losing admin access or a permission has the same effect immediately: the assistant can no longer answer the questions that permission covered.
Tips
- A connection stops working on its own 30 days after it was last used, so there is nothing to tidy up if you try it once and move on.
- Sessions, events, facility hire, store orders, passes, payments, receipts and payouts are all answered over a date window you (or Claude, on your behalf) choose. Asking a broad question like "this year" works, but a specific window such as "the last 30 days" gets a faster, more precise answer.
- If an answer looks wrong or missing, check which profile you connected as: the answer only ever reflects that profile's own permissions.
- Membership headline numbers are recomputed overnight, so a member who joined an hour ago will not show in the totals until tomorrow. Searching for them by name works straight away.
See also
- AI assistant feature overview: what clubs use it for, with worked examples
- Permissions: what Access Administration and each other permission actually grants
- Linked profiles: switching between the profiles you manage
- Your account dashboard: where your own account settings live