vibodj-prod

Showing 25 of 184 from the live probe.

• Login

  Single blocking sign-in via browser. Emits the approval URL via MCP progress + logging notifications, then waits up to 120s for approval. NOTE: because this call blocks, Claude CANNOT auto-open the URL in a browser — the user must click it from the progress notification themselves. PREFER `start_login` + `complete_login` for any interactive session, since that flow lets Claude run `open <url>` automatically. Use this single-call form only when the MCP host renders progress URLs as clickable link

• Start Login

  DEFAULT for any 'login' / 'sign in' request. Two-step browser sign-in: returns a URL immediately so Claude can auto-open it via `open <url>` (macOS) / `xdg-open <url>` (Linux) / `start <url>` (Windows), then call `complete_login` with the returned state. Password never enters Claude. Always prefer this over `login` (which blocks and can't auto-open) and over `login_with_password`.

• Complete Login

  Wait for the user to finish browser approval started by start_login. Pass BOTH the state and completionCode returned by start_login. Resolves when the browser POSTs tokens, or fails on timeout (120s).

• Cancel Login

  Cancel a pending browser-based login started by start_login.

• Login With Password

  FALLBACK ONLY — do NOT call when the user says 'login' or 'sign in'. Use the `login` tool (browser flow) for interactive sessions; password never enters Claude there. Use this tool ONLY when (a) the user explicitly types their email and password into the chat, or (b) running in a headless CI environment without a browser.

• Logout

  Sign out and clear the current session.

• Auth Status

  Check whether the MCP server is currently authenticated and which environment it targets.

• Get Current User

  Get the currently authenticated user's profile (name, email, role, settings)

• List Upcoming Events

  List upcoming (active) events for the current user. Use this by default when the user asks for 'my events' or 'recent events'. Only use list_past_events if the user explicitly asks for past/history events.

• List Past Events

  List past/history events for the current user. Only use this when the user explicitly asks for past, completed, or history events.

• Get Event

  Get detailed information about a specific event by its ID.

• Get Event Sections

  Get all timeline sections for an event (name, time, song count, progress).

• Get Section Songs

  Get songs in a specific event section.

• Create Event

  Create a new event. Returns the created event with its ID. Call get_event_types to get valid typeId values, and get_event_statuses for valid statusId values.

• Update Event

  Update an existing event's details (title, date, location, times, note, status, settings). Use statusId to activate or change event status — call get_event_statuses first to get valid values.

• Delete Event

  Soft-delete an event (moves it to history). The event can be restored with restore_event, or permanently removed with delete_event_forever.

• Delete Event Forever

  Permanently delete an event. The event must be soft-deleted first (in history). This cannot be undone.

• Get Notifications Count

  Get the number of unread notifications. Optionally filter by event.

• Get Notifications

  Get recent notifications. Optionally filter by event.

• Mark Notifications Read

  Mark notifications as read. Pass specific notification IDs, or omit to mark all as read.

• Get Event Custom Notifications

  Get all custom notifications for an event.

• Get Template Custom Notifications

  Get all custom notifications for a template.

• Create Event Custom Notification

  Create a new custom notification for an event. Addresses: 'hosts', 'guests', 'djs'. Sending time is relative to an event date. Title 3–30 chars, body max 100 chars. IMPORTANT: Do NOT use smart fields ($firstName$, $eventDate$, etc.) in the title — use plain text only. Smart fields are allowed ONLY in the body (input field), where they count as 0 chars.

• Create Template Custom Notification

  Create a new custom notification for a template. Addresses: 'hosts', 'guests', 'djs'. Title 3–30 chars, body max 100 chars. IMPORTANT: Do NOT use smart fields ($firstName$, $eventDate$, etc.) in the title — use plain text only. Smart fields are allowed ONLY in the body (input field), where they count as 0 chars.

• Update Event Custom Notification

  Update an existing custom notification for an event. Title 3–30 chars, body max 100 chars (smart fields like $firstName$, $eventDate$ etc. count as 0 chars).