Country Club, inside Claude
Our connectors bring Country Club into Claude through the Model Context Protocol (MCP). Ask Claude about your events, guests, opportunities, and pipeline in plain language — it works directly with your Country Club data, securely and on your behalf.
What is a connector?
A connector is a secure bridge between Claude and Country Club. Once connected, Claude can read your data and take actions you approve — like pulling an attendee list, drafting outreach to a target account, or reviewing an opportunity — without you ever leaving the conversation. You sign in once with your existing Country Club account; Claude never sees your password.
Choose a connector
Country Club for Hosts
18 toolsFor hosts
Give Claude a working view of the events you run — your guest lists, engagement, and the connections forming around each table.
https://mcp.country.club/hosts/mcpEvents
Review and manage the events you host — inspect details and update event copy.
Attendees
Browse and export attendee lists, open individual profiles, review attendee matches, and remove guests.
Engagement
See who has activated, track last activity and the engagement funnel, and export activation data.
Interests
Surface mutual and one-sided interests between attendees and export them for follow-up.
How to connect
In Claude, open Settings and go to the Connectors section.
Choose to add a custom connector.
Paste the connector URL for the workspace you want — Hosts or Business.
Click Connect, then sign in with your Country Club account when prompted.
Approve access. The connector's tools are now available inside your chats.
Using a desktop client such as Claude Desktop, Claude Code, or Cursor? Add the same connector URL and paste your Country Club access token as a Bearer token when prompted.
Country Club for Hosts — tool reference
Every tool this connector exposes, grouped by area. Each tool is marked by how it touches your data, and lists the inputs it accepts.
Inputs marked ? are optional. query is a set of optional filter / pagination params; body is a JSON payload for the resource.
Account
hosts_meReadGet the current authenticated user (profile, employment, settings) for the host/organizer.
Input: —
Events
hosts_events_listReadList events where the authenticated user is an organizer.
Input: —
hosts_events_getReadGet full details of a single organizer event by id.
Input: event_id
hosts_events_updateDestructiveReplace an event (PUT). Body must satisfy OrganizerEventUpdateRequest.
Input: event_id, body
hosts_events_patchDestructivePartial update of an event (PATCH). Body fields are optional.
Input: event_id, body
Attendees
hosts_attendees_listReadList attendees of an event. Optional query: page, page_size, search, ordering, state.
Input: event_id, query?
hosts_attendees_matchesReadList matches for a single attendee within an event.
Input: event_id, attendee_id, query?
hosts_attendees_profileReadGet an attendee's full profile by profile_id within an event.
Input: event_id, profile_id
hosts_attendees_exportReadExport attendees as a CSV blob.
Input: event_id, query?
hosts_attendees_removeDestructiveRemove an attendee from an event.
Input: event_id, attendee_id
Engagement
hosts_activated_listReadList activated (logged-in) attendees of an event.
Input: event_id, query?
hosts_activated_last_activityReadLast interested/dismissed actions for one activated attendee.
Input: event_id, attendee_id
hosts_activated_exportReadExport activated attendees as a CSV blob.
Input: event_id, query?
hosts_engagement_funnelReadEngagement funnel metrics for an event (logged_in %, set_priorities %, etc.).
Input: event_id
Interests
hosts_mutual_interests_listReadList mutual interests (matches where both sides expressed interest) for an event.
Input: event_id, query?
hosts_mutual_interests_exportReadExport mutual interests as a CSV blob.
Input: event_id
hosts_one_sided_interests_listReadList one-sided interests (interest expressed but not yet reciprocated) for an event.
Input: event_id, query?
hosts_one_sided_interests_exportReadExport one-sided interests as a CSV blob.
Input: event_id, query?
Security & privacy
Sign in with OAuth
Authentication uses OAuth 2.1 with your existing Country Club account. Claude never receives or stores your password.
You stay in control
Claude only sees the data your account can access, and asks before running actions that change or remove anything.
Revoke anytime
Disconnect the connector from Claude at any time to immediately end its access to your Country Club data.
Need help?
If you need assistance connecting or using the connectors, please contact our support team at country.club/contact.