@phenomenalorg/mcp 0.5.178 → 0.5.179

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@phenomenalorg/mcp",
-  "version": "0.5.178",
+  "version": "0.5.179",
   "type": "module",
   "description": "Phenomenal MCP bridge — connects a stdio-only MCP client to the Phenomenal MCP server over Streamable HTTP, with browser sign-in.",
   "license": "MIT",

package/skill/SKILL.md

@@ -8,7 +8,7 @@ description: Use when the user wants to manage an organization in Phenomenal —
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 52 tools · 325 actions · 5 prompts · fingerprint `4cc1a527`._
+_Tool surface: 52 tools · 329 actions · 5 prompts · fingerprint `063f219b`._
 
 You are connected to Phenomenal, the platform for this organization's site, members, events, tickets, email, forms, store and money.
 

package/skill/references/mutations.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 52 tools · 325 actions · 5 prompts · fingerprint `4cc1a527`._
+_Tool surface: 52 tools · 329 actions · 5 prompts · fingerprint `063f219b`._
 
 The curated tools in `references/tools.md` cover the work an officer does most days. Everything else Phenomenal can do is reachable by name:
 
@@ -96,10 +96,12 @@ Areas: account, automations, billing, brand, broadcasts, connections, domains, d
 - `createTicketType` — Add a ticket type (price, capacity) to an event.
 - `createVolunteerRole` — Create a volunteer role on an event — the job itself, like 'Ticket table'.
 - `createVolunteerShift` — Add a shift to a volunteer role: a start, an end, and how many people are needed.
+- `createVolunteerShifts` — Add many shifts or conference times to one volunteer job at once, all or nothing (up to 300).
 - `deleteEvent` **(confirm)** — Delete an event, its ticket types and its volunteer jobs.
 - `deleteTicketType` **(confirm)** — Delete a ticket type from an event.
 - `deleteVolunteerRole` **(confirm)** — Remove a volunteer job and its shifts.
 - `deleteVolunteerShift` **(confirm)** — Remove one shift; the job and its other shifts are untouched.
+- `deleteVolunteerShifts` **(confirm)** — Remove many shifts or conference times of one volunteer job at once, all or nothing.
 - `setEventParticipationGoal` — Set or clear an event’s sign-up goal (in households) and the earlier event its sign-ups are compared with.
 - `setEventPublished` **(confirm)** — Prefer the `set_event_published` tool. Publish or unpublish an event.
 - `setEventRules` — Make this the default: how long a NEW volunteer job’s shift runs (`shiftMinutes`: 15 to 720 minutes in quarter hours from the event’s start, or null for the event’s hours, the starting rule) and how many people it takes (`shiftPeople`: 1 to 500, 2 to start).
@@ -116,6 +118,7 @@ Areas: account, automations, billing, brand, broadcasts, connections, domains, d
 - `addSubmissionNote` — Add a staff note to a form submission you can read.
 - `createForm` — Create a form (sign-ups, RSVPs, volunteer slots) as a draft.
 - `deleteForm` **(confirm)** — Delete a form.
+- `deleteFormSubmission` **(confirm)** — Delete one form answer for good, with its attached files, its staff notes and its one-by-one sharing (a family’s erasure request).
 - `deleteSubmissionNote` **(confirm)** — Delete a staff note on a form submission — your own, or any note if you are an admin.
 - `grantFormAccess` **(confirm)** — Let members read every submission to one form — open attachments and export it too.
 - `grantSubmissionAccess` **(confirm)** — Let members read ONE form submission and its attachments.
@@ -410,6 +413,7 @@ Areas: account, automations, billing, brand, broadcasts, connections, domains, d
 
 ## tickets
 
+- `addNextAppointmentTime` — Book a double for the family who holds a conference seat (a teacher’s suggestion): the time right after theirs, else right before, at most 15 minutes away.
 - `cancelMyBooking` — Cancel a booking you made yourself.
 - `checkInOrder` — Check a whole booking (one party) in at the door in one step: every still-valid ticket on it.
 - `checkInTicket` — Check a ticket in at the door by its code.

package/skill/references/schema.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 52 tools · 325 actions · 5 prompts · fingerprint `4cc1a527`._
+_Tool surface: 52 tools · 329 actions · 5 prompts · fingerprint `063f219b`._
 
 Two tools answer questions no curated tool anticipated.
 

package/skill/references/starting-doc.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 52 tools · 325 actions · 5 prompts · fingerprint `4cc1a527`._
+_Tool surface: 52 tools · 329 actions · 5 prompts · fingerprint `063f219b`._
 
 Phenomenal runs an organization: its public website, its member roster, its events and tickets, its email to members, its forms, its store and its money. It exposes all of that over the Model Context Protocol, so an assistant an officer already uses can do the work with them.
 

package/skill/references/tools.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 52 tools · 325 actions · 5 prompts · fingerprint `4cc1a527`._
+_Tool surface: 52 tools · 329 actions · 5 prompts · fingerprint `063f219b`._
 
 Every tool the Phenomenal MCP server offers, in the order a client lists them. `list_my_orgs` is first because every other tool needs an organization id from it.