Skip to main content
Glama

CourtReserve MCP

First MCP server for CourtReserve — the racquet-sports club management platform that runs tennis, pickleball, padel, racquetball, squash, and badminton clubs. Talk to your club's members, reservations, events, and transactions from Claude, Cursor, or any MCP-compatible AI client.

What you can do with it

You:   "Find every active member at our downtown location whose membership
        expires this month and tell me which ones haven't booked a court
        in the last 30 days."
Claude: *calls list_memberships + list_reservations, joins the results, replies*

You:   "Register Sarah for the Tuesday evening pickleball clinic."
Claude: *calls register_for_event, confirms the result*

You:   "Cancel reservation 8888 and refund the booking fee."
Claude: *calls cancel_reservation + create_transaction (credit), reports back*

The MCP covers the same surface CourtReserve uses internally: members, memberships, families, court reservations, events (clinics, lessons, tournaments, round robins, open play), event registrations, transactions, courts, and locations.

Related MCP server: stessa-mcp

Install

pip install -e .

For local development:

pip install -e ".[dev]"

Configure

CourtReserve's API uses HTTP Basic auth with two values issued from the club admin UI:

  1. Log in to app.courtreserve.com as a club admin.

  2. Go to Settings -> Additional Features -> Integrations -> API Access.

  3. Click Create API Key. Enable the API access checkbox first if it's off.

  4. Choose Full Access (read + write) or Restricted Access (pick specific roles).

  5. Copy the Username (format: Org_<numeric>) and Password (long opaque string).

export COURTRESERVE_USERNAME="Org_12345"
export COURTRESERVE_PASSWORD="98765_550e8400-e29b-41d4-a716-446655440000"

The API key must be enabled on an Advance / Momentum / Enterprise plan (per CourtReserve's docs, the API add-on is paid). The key's role-based permissions control which endpoints the MCP can call.

Claude Desktop / Cursor

Add to your claude_desktop_config.json (or ~/.cursor/mcp.json):

{
  "mcpServers": {
    "courtreserve": {
      "command": "courtreserve-mcp",
      "env": {
        "COURTRESERVE_USERNAME": "Org_12345",
        "COURTRESERVE_PASSWORD": "your-password"
      }
    }
  }
}

Tools (22)

Group

Tool

Purpose

Diagnostic

health_check

Verify credentials + returns locations list

Members

list_members, get_member, create_member, update_member, delete_member

Member CRUD + search

Memberships

list_memberships, get_membership, create_membership, update_membership, cancel_membership

Tier assignment + lifecycle

Families

list_families, get_family, add_family_member

Linked-member accounts

Reservations

list_reservations, get_reservation, create_reservation, cancel_reservation

Court bookings

Events

list_events, get_event, list_event_registrations, register_for_event, cancel_event_registration

Clinics, tournaments, lessons, round robins

Transactions

list_transactions, get_transaction

Payments, credits, refunds

Courts

list_courts, get_court

Court surface + rate info

Locations

list_locations, get_location

Sites/branches

Run courtreserve-mcp --help (or start the server and inspect tools/list from your client) for the full JSON schema.

Engineering standards

This MCP inherits the engineering playbook applied across the sanjibani MCP portfolio:

  • Shared httpx.AsyncClient with connection pooling + transport-level retries.

  • Typed exception hierarchy (CourtReserveAuthError, NotFoundError, RateLimitError, APIError, ConnectionError) with structured fields (http_status, request_id, retry_after).

  • Application-level retry with exponential backoff + full jitter on 429/5xx, honoring Retry-After.

  • isError-compliance (per the Blackwell Systems MCP security audit): tools raise exceptions, FastMCP wraps them with isError=true on the wire. AI agents can distinguish failures from successful responses returning error-shaped strings.

  • JSONL audit logging via src/courtreserve_mcp/audit.py — one record per tool call to stderr (or <PKG>_AUDIT_LOG file). Fail-open: sink failure never breaks the tool. Secret redaction on password/api_key/token/etc.

  • respx for httpx mocking + hypothesis property tests + pytest-asyncio.

  • mypy --strict clean, ruff full rule set clean, py.typed marker (PEP 561).

  • src/ layout, dynamic version from __init__.py, hatchling backend.

Development

pip install -e ".[dev]"

# Lint
ruff check src tests
ruff format --check src tests

# Type
mypy src

# Test
pytest

# All three
ruff check src tests && ruff format --check src tests && mypy src && pytest

License

MIT — see LICENSE.

Author

Sanjibani Choudhury schoudhury1991@gmail.com. Independent community build — not affiliated with CourtReserve or Storable. PRs welcome if CourtReserve renames an endpoint; open an issue if you find a gap in coverage.


This MCP is part of the sanjibani MCP portfolio — 28+ vertical-specific MCPs (insurance, dental, veterinary, legal, home service, church, auto-dealership, title/escrow, pest control, golf, self-storage, laundromat, youth sports, etc.). All MIT-licensed, all ruff + mypy + pytest clean, all isError-compliant.

Need a custom MCP built for a niche SaaS you use? See engagement options.

Available Tools

29 tools
add_family_memberA

Link an existing member into a family account.

Use when: "add Sarah to the Doe family account".

Args: family_id: Target family id. member_id: Member to add to the family. relationship: Optional relationship string ("spouse", "child", etc.).

Inputs: family_id (required), member_id (required), relationship. Returns: result

cancel_event_registrationA

Cancel a member's event registration.

Use when: "pull Sarah out of the Tuesday clinic".

Inputs: event_id (required), registration_id (required). Returns: result

cancel_membershipA

Cancel (terminate) a membership. Preserves the historical record.

Use when: "cancel membership 67890". Preferable to deleting the member outright - keeps the audit trail.

Inputs: membership_id (required). Returns: result

cancel_reservationA

Cancel (delete) a court reservation.

Use when: "cancel reservation 8888". Sends a courtesy email to the primary member if CourtReserve is configured to do so.

Inputs: reservation_id (required). Returns: result

create_memberA

Create a new club member.

Use when: "add Jane Doe to the club", "register a new member".

Args: first_name: Member's first name (required). last_name: Member's last name (required). email: Primary email - used for login (required). phone: Optional phone number. location_id: Home location for multi-location clubs. notes: Internal admin notes.

Inputs: email (required), last_name (required), first_name (required), notes, +2 more. Returns: result

create_membershipA

Assign a membership tier to a member.

Use when: "give Jane a Gold membership starting today".

Args: member_id: Target member id. tier: Membership tier name as configured in CourtReserve (e.g. "Gold", "Family", "Junior"). Exact strings depend on club configuration. start_date: ISO date (YYYY-MM-DD). Defaults to today. end_date: ISO date (YYYY-MM-DD). Open-ended if omitted. location_id: Location (multi-location clubs only).

Inputs: tier (required), member_id (required), end_date, start_date, +1 more. Returns: result

create_reservationA

Create a new court reservation.

Use when: "book court 3 for Sarah at 2pm for 90 minutes with John".

Args: court_id: Target court id. start_time: ISO datetime (YYYY-MM-DDTHH:MM:SS) in club local time. duration_minutes: Reservation length in minutes. primary_member_id: Booking member id. additional_member_ids: Optional list of additional member ids (for doubles, group play, etc.). notes: Optional admin notes.

Inputs: court_id (required), start_time (required), duration_minutes (required), primary_member_id (required), +2 more. Returns: result

delete_memberA

Remove a member from the club. Use with caution - often irreversible.

Use when: "delete member 12345". Consider cancelling the membership instead - cancellation preserves the history while removing billing.

Inputs: member_id (required). Returns: result

get_courtA

Fetch a single court by id - surface type, location, hourly rate.

Use when: "show court 5 - what's the surface and rate?".

Inputs: court_id (required). Returns: result

get_eventA

Fetch a single event by id - description, schedule, capacity, price.

Use when: "show event 4444 - when does it start, what's the cost?".

Inputs: event_id (required). Returns: result

get_familyA

Fetch a single family account by id - includes linked members.

Use when: "show family 555's profile - which members are linked?".

Inputs: family_id (required). Returns: result

get_locationA

Fetch a single location by id - address, hours, contact info.

Use when: "show our downtown location's details".

Inputs: location_id (required). Returns: result

get_memberA

Fetch a single member's full profile by id.

Use when: "show member 12345's profile", "what membership tier does Sarah have?". Returns the full record including family, membership, contact info, and account status.

Inputs: member_id (required). Returns: result

get_membershipA

Fetch a single membership by id - tier, status, dates, billing.

Use when: "show membership 67890's full details".

Inputs: membership_id (required). Returns: result

get_reservationA

Fetch a single reservation by id - full player list, court, time, cost.

Use when: "show reservation 8888 - who booked it?".

Inputs: reservation_id (required). Returns: result

get_transactionA

Fetch a single transaction by id - amount, type, payment method, status.

Use when: "show transaction 9999 - what was it for?".

Inputs: transaction_id (required). Returns: result

health_checkA

Verify credentials work. Returns location list as a smoke test.

Use when: "is my CourtReserve API key valid?" - if this fails, all other tools will too. Check COURTRESERVE_USERNAME / COURTRESERVE_PASSWORD and that the API key is enabled on an Advance/Momentum/Enterprise plan.

Inputs: no named parameters. Returns: result

list_courtsA

List courts at one or all locations.

Use when: "what courts do we have at location 1?", "list all 12 courts".

Inputs: location_id. Returns: result

list_event_registrationsB

List registrations (signups) for an event.

Use when: "who's signed up for the Tuesday clinic?".

Inputs: event_id (required), skip, take. Returns: result

list_eventsB

List events (clinics, lessons, tournaments, round robins, open play).

Use when: "what events are happening next month?", "list all tournaments in Q3".

Inputs: skip, take, end_date, start_date, +1 more. Returns: result

list_familiesC

List family accounts (linked members under a primary contact).

Use when: "list all families", "find family accounts at our west location".

Inputs: skip, take, location_id. Returns: result

list_locationsA

List the club's locations (sites / branches).

Use when: "list all our club locations". Single-location clubs get a 1-item list.

Inputs: no named parameters. Returns: result

list_membersA

List club members with optional paging and search filter.

Use when: "show me all members", "find member Jane Doe", "list active members at our downtown location".

Args: skip: Records to skip (paging offset). Default 0. take: Page size (max records returned). Default 100. q: Search query - matches name/email substring. location_id: Filter to a single location (multi-location clubs only).

Inputs: q, skip, take, location_id. Returns: result

list_membershipsA

List memberships, optionally filtered by member or location.

Use when: "what memberships are active?", "show member 12345's membership history", "list all memberships at location 1".

Inputs: skip, take, member_id, location_id. Returns: result

list_reservationsA

List court reservations, with optional filters by location, court, member, and date range.

Use when: "what reservations are on court 3 this Saturday?", "show all reservations for member 12345 in the next 30 days".

Args: skip: Paging offset. take: Page size (default 100). location_id: Filter to one location. court_id: Filter to one court. member_id: Filter to one member's reservations. start_date: ISO date (YYYY-MM-DD) lower bound. end_date: ISO date (YYYY-MM-DD) upper bound.

Inputs: skip, take, court_id, end_date, +3 more. Returns: result

list_transactionsA

List payment transactions - charges, credits, refunds.

Use when: "show me yesterday's revenue", "what did member 12345 spend this month?".

Args: skip: Paging offset. take: Page size (default 100). location_id: Filter to one location. member_id: Filter to one member. start_date: ISO date lower bound. end_date: ISO date upper bound.

Inputs: skip, take, end_date, member_id, +2 more. Returns: result

register_for_eventA

Register a member for an event.

Use when: "sign Sarah up for the Tuesday clinic".

Args: event_id: Target event id. member_id: Member to register. notes: Optional notes (partner name, skill level, etc.).

Inputs: event_id (required), member_id (required), notes. Returns: result

update_memberA

Update an existing member. Partial updates are supported.

Use when: "change Jane's phone number", "fix typo in member 12345 email". Only fields passed in are updated.

Inputs: member_id (required), email, notes, phone, +2 more. Returns: result

update_membershipB

Update a membership tier, end date, or status.

Use when: "extend membership 67890 to year-end", "change tier to Gold".

Inputs: membership_id (required), tier, status, end_date. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 29 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action (e.g., create_member vs create_membership, cancel_reservation vs cancel_event_registration). There is no ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_family_member, list_courts, cancel_event_registration). No deviations.

    Tool Count4/5

    29 tools cover a broad domain (members, families, memberships, courts, events, reservations, transactions, locations, health). While slightly high, each tool serves a distinct purpose and is justified.

    Completeness5/5

    The tool surface provides comprehensive CRUD and lifecycle coverage for all major resources (members, memberships, reservations, events, etc.). Obvious gaps like updating events are absent but not critical for an MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers