Waitwhile MCP by usefulapi

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 마케팅 및 소셜 미디어

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://waitwhile.usefulapi.io/mcp

claude mcp add --transport http waitwhile https://waitwhile.usefulapi.io/mcp

{
  "mcpServers": {
    "waitwhile": {
      "url": "https://waitwhile.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "waitwhile": {
      "type": "http",
      "url": "https://waitwhile.usefulapi.io/mcp"
    }
  }
}

https://waitwhile.usefulapi.io/mcp

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• waitwhile_list_locations

  List the account's locations (businesses/sites): id, name, short name, address, time zone, opening hours and waitlist/booking settings. Use the ids to filter visits, services and resources. GET /locations.

• waitwhile_get_location

  One location by id or short name (the part of its public Waitwhile URL). GET /locations/{shortNameOrId}.

• waitwhile_list_location_status

  Live status of every location: open/closed, number of people waiting and being served, current estimated wait time, and booking counters. GET /location-status.

• waitwhile_get_location_status

  Live status of one location: open/closed, waiting and serving counts, estimated wait. GET /location-status/{locationId}.

• waitwhile_list_visits

  List visits: waitlist entries (people in line) and bookings (appointments), with customer, state (PENDING, DRAFT, BOOKED, WAITING, SERVING, COMPLETE), tags (e.g. NO-SHOW, CANCELLED, ARRIVED), services, resources, party size, position and timestamps. Filter by location, state, tag

• waitwhile_search_visits

  Search visits by a prefix match on customer name, phone, e-mail or customer id, optionally filtered by location, state, tag and excluded tags. Page-numbered. Contains customer contact details. GET /visits/search.

• waitwhile_get_visit

  One visit (waitlist entry or booking) by id: customer, state, tags, services, resources, party size, position, estimated wait and all timestamps. GET /visits/{visitId}.

• waitwhile_list_booking_slots

  Booking slots of a location for a date range with the free spots per resource and service, so you can see when an appointment can be booked. Dates are local to the location, YYYY-MM-DDThh:mm. GET /visits/availability.

• waitwhile_first_available_slots

  The first available booking slots of a location (optionally for a party size, services and resources) from a date. Use it to propose appointment times. GET /visits/first-available-slots.

• waitwhile_list_customers

  List customers (name, phone, e-mail, tags, last visit per location, created/updated). Cursor-paged, 20 per page by default; filter by location, external id or created/updated date. Contains personal data. GET /customers.

• waitwhile_search_customers

  Search customers by a prefix match on name, phone, e-mail or customer id; optionally narrowed by location, visit state or tag. Page-numbered. Contains personal data. GET /customers/search.

• waitwhile_get_customer

  One customer by id: contact details, tags, per-location state and last visit. Contains personal data. GET /customers/{customerId}.

• waitwhile_list_customer_notes

  The staff notes recorded on a customer (content, author, visit and location, timestamps). GET /customers/{customerId}/notes.

• waitwhile_list_services

  List services (what customers book or queue for): name, duration, price, locations, resources and category structure. GET /services.

• waitwhile_get_service

  One service by id. GET /services/{serviceId}.

• waitwhile_list_resources

  List resources — the people, rooms, tables or equipment that serve customers: name, locations, services, availability flag and category structure. GET /resources.

• waitwhile_get_resource

  One resource by id. GET /resources/{resourceId}.

• waitwhile_resources_availability

  Working hours/availability of a location's resources on a date (e.g. who is working today). GET /resources/availability.

• waitwhile_list_data_fields

  List the custom data fields (intake/booking form questions) with type, options and where they apply. Use the ids to read answers on visits. GET /data-fields.

• waitwhile_get_data_field

  One data field by id. GET /data-fields/{dataFieldId}.

• waitwhile_list_users

  List the staff users of the account: name, e-mail, roles, locations. Password data and tokens are never returned. GET /users.

• waitwhile_list_messages

  List the SMS/e-mail messages Waitwhile sent to and received from customers: channel, recipient, body, delivery state (PENDING, BLOCKED, FAILED, DELIVERED, UNCONFIRMED, RECEIVED) and error. Filter by location, visit, customer, state or date. Contains personal data. This only reads

• waitwhile_get_message

  One message by id. Contains personal data. GET /messages/{messageId}.

• waitwhile_visit_analytics

  Aggregated visit statistics for a period: visits, waitlisted, bookings, served, no-shows, cancellations, wait and serve duration quantiles, and breakdowns by location, resource, service, party size, user, day of week and hour of day. GET /analytics/visits (JSON).

• waitwhile_list_audit_entries

  The account's audit log: who changed what and when (visits, customers, locations, services, resources, users, messages). Filter by type, event, entity, location or date. GET /audit-entries.

• waitwhile_create_visit

  WRITE: create ONE visit at a location. Without a date it adds the customer to the waitlist; with a local date-time (YYYY-MM-DDThh:mm) it creates a booking. Needs a location and at least a name, phone or e-mail. Not idempotent: calling it twice creates two visits. Visit notes are

• waitwhile_update_visit

  WRITE: change ONE visit — its state (e.g. WAITING to SERVING to COMPLETE, or BOOKED), add/remove tags (e.g. ARRIVED, CONFIRMED, NO-SHOW), booking date/duration or party size. Only the fields you pass change. By default the request asks Waitwhile to suppress the customer message;

• waitwhile_cancel_visit

  WRITE: cancel ONE visit (a waitlist entry or booking). Waitwhile sets its state to COMPLETE and adds the CANCELLED tag; the visit is kept, not deleted. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate cancellation notice, an

• waitwhile_add_customer_note

  WRITE: add one staff note to a customer's record (optionally tied to a visit and location). Adds only; nothing is edited or sent to the customer. POST /customers/{customerId}/notes.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 usefulapi.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  21ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 29개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 2952개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 2952개 중 97%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 2952개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{