Read Hello Club members, events, bookings and transactions; add members and charges. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"hello-club": {
"url": "https://hello-club.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"hello-club": {
"type": "http",
"url": "https://hello-club.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Hello Club API key.
Create it in Hello Club under Integrations → API keys (the card at the bottom of the page; API access needs the Business plan). A key has full access to your club's data, so use a key made just for this connection and switch it off in Hello Club to revoke it. Your key is used only to call the Hello Club API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Hello Club API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Hello Club connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
hello_club_list_members | read | List members List or search the club's members (people and staff) with contact details, roles, memberships (subscriptions), account credit and amount owing. Filter by free text, gender, role, staff, money owing, account credit, current subscription state, ending subscriptions or a membership type. GET /member. |
hello_club_get_member | read | Get member One member by id: profile, contact details, roles, subscriptions, account credit, amount owing, custom fields. Password hashes and payment-provider data are not returned. GET /member/{id}. |
hello_club_list_membership_types | read | List membership types The membership types (plans) the club sells: name, fee, term, age limits, renewal rules and access. GET /membership. |
hello_club_get_membership_type | read | Get membership type One membership type by id. GET /membership/{id}. |
hello_club_list_events | read | List events List or search events and classes (sessions, courses, tournaments) with dates, activity, area, organiser, capacity and attendance rules. Filter by date range, recurring, hidden, public, has attendees, has spaces left, rule type, activity, area or organiser. GET /event. |
hello_club_get_event | read | Get event One event by id: dates, recurrence, activity, area, organiser, capacity, attendance rules, questions. GET /event/{id}. |
hello_club_list_event_attendees | read | List event attendees List who is signed up to events: member or guest, event, sign-up date, paid state, whether they attended. Filter by event, member or guest. GET /eventAttendee. |
hello_club_list_bookings | read | List bookings List resource bookings (courts, rooms, lanes): owner, activity, area, start/end, paid state, recurrence. Filter by date range, member, activity, mode, area, recurring, paid or removed. GET /booking. |
hello_club_list_transactions | read | List transactions List the club's financial transactions (invoices, charges, credits): member, type, amount, tax, due and payment dates, paid state. Filter by member, type, paid, credit or a date range on date / dueDate / paymentDate. GET /transaction. |
hello_club_get_transaction | read | Get transaction One transaction by id: member, type, amount, tax, details, dates, paid state. GET /transaction/{id}. |
hello_club_list_check_ins | read | List check-ins List check-in logs (members arriving at the club): who, when, how (type). Filter by member or type, or only unknown people. GET /checkInLog. |
hello_club_list_access_logs | read | List door access logs List door / access-control logs in a date range: member, door, event, whether it was an override or an unknown person. GET /accessLog. |
hello_club_create_member | write | Create member WRITE: create a new member in the club (first and last name required; email, mobile, phone and gender optional). Creates a real member record in the club's database; it does not assign a membership or send an invoice. Not idempotent: calling twice creates two members, so search with hello_club_list_members first. POST /member. |
hello_club_create_transaction | write | Create transaction WRITE: create a financial transaction for a member (a charge, or a credit when is_credit is true), e.g. an invoice line or a manual adjustment. This changes the member's amount owing / account credit in the club's books and, with notify_by_email, emails the member. Not idempotent: calling twice creates two transactions. Confirm member, amount and type with the user first. POST /transaction. |
hello_club_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
hello_club_request_feature | Request a missing feature Tell usefulapi that the user needs something the Hello Club tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
hello_club_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Hello Club tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
hello_club_cancel_subscription | Cancel the Pro subscription Cancel the caller's Hello Club Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run hello_club_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper club | $9/mo · $90/yr | Unlimited |
Pro covers this Hello Club server only. Subscribe with hello_club_upgrade (it returns a Stripe Checkout link). Cancel any time with hello_club_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running hello_club_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Hello Club. The server calls the Hello Club API with your own Hello Club access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Hello Club API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Hello Club API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Hello Club API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Hello Club.
Yes, if you approve it. 2 of the 14 Hello Club tools can create or change data. The other 12 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Hello Club server only. Run hello_club_usage_status to see how many calls you used.
Ask the AI to run hello_club_upgrade: it returns a Stripe Checkout link. To cancel, run hello_club_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with hello_club_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.