MCP App Store
by KeenEthics
Gomry icon

Gomry MCP Server for ChatGPT

By Gomry, Inc.

Overview

Gomry is an event platform for organizers. Connect your Gomry account to run your events from ChatGPT: see what's coming up, create and edit events, change ticket prices and limits, check who registered, look up contacts, invite and message attendees, and compare sales and page views across events. Use it when you want an answer about your events or a quick change without opening the dashboard. It works on your own Gomry data and respects your team role, and ChatGPT asks you before running anything that changes your data or emails people.

How to connect

  1. ChatGPT: Open the Gomry listing in the ChatGPT app directory and choose Connect. ChatGPT listing Gomry exposes 111 tools here.

Tools

add_contacts_to_list

ChatGPT
Add one or more contacts to a list.

add_to_calendar

ChatGPT
Add an event, experience or external event to a calendar so it appears on that public page. type says which kind of entry the id refers to — the three do not share an id space, so a wrong type is a not-found rather than a silent mismatch. Optionally feature it to pin it to the top.

archive_experience_ticket_class

ChatGPT
Archive an EXPERIENCE ticket class so it stops accepting new bookings. Existing bookings keep working and the tier name is preserved on receipts. Blocked while active bookings still target the tier on FUTURE sessions — the tool returns that count so the organizer can cancel them first. Hard-delete is deliberately not available (booking history needs the class doc).

cancel_scheduled_experience_message

ChatGPT
PERMANENTLY DESTROYS A QUEUED SEND. Calls off a scheduled experience blast so it never goes out. There is no un-cancel. Confirm with the user before calling. Only works while the status is "scheduled", and only for the organizer who created it.

cancel_scheduled_message

ChatGPT
PERMANENTLY DESTROYS A QUEUED SEND. Calls off a blast that is still scheduled so the emails never go out, and removes it from the event's message list. There is no un-cancel: the message and its schedule are gone, and restoring it means composing and scheduling a new one. Confirm with the user before calling. Only works while the status is "scheduled" — a message that has already been sent cannot be recalled — and only the organizer who created it can cancel it.

compare_periods

ChatGPT
Compare a CURRENT date range against a baseline range across all the organization's events — the tool for "how does this period compare to the same period last year", year-over-year, or any two windows. Returns a summary for each window (net & gross revenue, refunds, tickets sold, events held, unique attendees, new attendees) plus per-metric deltas and % change. By default the baseline is the SAME-LENGTH window exactly years_back years before the current one (default 1) — the server computes it, so never hand-compute last year's dates. Pass baseline_from/baseline_to only for an arbitrary comparison window. Amounts are per native currency (never converted); deltas are computed per currency. Defaults the current window to the last 6 months.

create_attendee

ChatGPT
EMAILS THE ATTENDEE when send_email is true (a ticket CONFIRMATION email, "Your ticket: …", which is the wrong email for an invitation) — it defaults to false, so nothing is sent unless you ask for it. Use this tool ONLY to create confirmed/already-attending tickets ("attendees") for a contact. To INVITE someone, send an invitation, add to the guest list, or handle an RSVP, use send_invite instead — NOT this tool. Delegates to the canonical service so capacity guards, invited-ticket upgrades, contact upsert, and shared paymentID all behave exactly as the dashboard.

create_contact

ChatGPT
Create a new contact in the organization. At least one of email or phone_number is required. If a contact with this email already exists, returns a 409-equivalent error with the existing record.

create_contact_list

ChatGPT
Create a new contact list (segment). Rejects a name that already exists rather than creating a duplicate, because two lists sharing a name make name-based resolution ambiguous for every later call.

create_event

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state. The event is reachable at its public URL and its default "General Admission" ticket class is on sale the moment this returns, and unless is_private is true the event is also queued for an automatic review that can list it in Gomry's public discovery feed. Other side effects (calendar fanout, Mixpanel tracking) match the dashboard creation flow exactly. Requires name, start, and location. end is OPTIONAL — omit it and the event ends 2 hours after the start, exactly as the create page does (it has no end-date input); only send it when the caller gave an explicit end time. Returns the persisted event.

create_experience

ChatGPT
GOES LIVE IMMEDIATELY at its public URL — there is no draft state — but it has NO BOOKABLE SESSIONS until you call create_recurrence, so a visitor arriving before then finds an empty calendar rather than a purchase. Creates a recurring EXPERIENCE (a class, tour, or repeating session series) — the experience counterpart of create_event. Requires name, duration_minutes, default_capacity, location, price and currency. A default "General admission" ticket class is created at that price.

create_experience_ticket_class

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the tier is bookable on the public experience page the moment this returns, and creating the FIRST class also switches that page for every visitor, from a single price to a tier picker. Creates a ticket class (pricing tier) on an EXPERIENCE — e.g. "Early Bird", "VIP", "Member". Required: name, price, capacity. The tier always uses the experience's currency. Use for "add a VIP tier at $50 with 10 seats to my yoga class". This is also how you set a per-tier approval requirement on an experience (require_approval), which is not reachable via update_experience.

create_merch_offering

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the add-on is on sale to buyers at that host's checkout the moment this returns. Put a catalog add-on on sale at one event or experience (hostId = event id OR experience service id). Give it a per-host price, and stock: stocks for precise per-option counts, or stock for one count across every option, or omit both for unlimited. Get the productId from list_merch_products first. One offering per product per host — offering the same product twice is rejected.

create_merch_product

ChatGPT
NOT ON SALE ANYWHERE — this only adds a reusable add-on product template to the organizer's private catalog; no buyer can see or purchase it until create_merch_offering puts it on sale at a specific event or experience. Pass options (e.g. ["S","M","L"]) for an add-on with variants like a t-shirt; omit it for a simple add-on like parking (stored with one implicit "General" option).

create_promo_code

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the code is redeemable at checkout the moment this returns, and creating the event's FIRST code also turns on the promo-code field in that event's checkout for every buyer. Use valid_from to hold it until a later date. Provide exactly one of discount_amount (fixed, in the event currency) or percent_off (1-100) — passing both or neither is an error. Leave applied_to_tickets empty to discount every ticket class, or list ticket-class ids to restrict it; call list_ticket_classes first to get those ids. Codes are uppercased on save and must be unique within the event.

create_recurrence

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the sessions this schedule generates are bookable on the experience's public page as soon as they materialise. Creates a recurring schedule from a REPEATING RULE the caller stated as a rule ("every Friday at 18:00", "weekdays at 9am", "last Friday of every month"). One call per rule — never one per date. A list of specific dates ("the 3rd, 10th and 17th") is NOT a recurrence: add each one with create_session instead, and do not create a schedule alongside them. Weekly cadence REQUIRES days_of_week. Sessions are materialised lazily, so they appear as the window rolls forward rather than all at once.

create_role

ChatGPT
Create a custom role for the organization with a specific set of privileges. Distinct from the 5 built-in system roles (admin, editor, operations_manager, events_manager, check-in_only), which always exist and cannot be created/edited/deleted.

create_session

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the session is bookable on the experience's public page the moment this returns. Adds ONE session on ONE specific date, independent of any recurring schedule — a one-off class, a make-up session, a special date. When the caller names a LIST of dates, call this once per date and create NO recurrence: individual dates are not a repeating rule, and a schedule added alongside them would generate extra sessions nobody asked for. Reach for create_recurrence only for a stated rule ("every Tuesday"). Works on an experience with no schedule at all; provider_id and timezone default to the experience's existing schedule when it has one, so omit them unless the caller named a different provider or timezone.

create_session_message_automation

ChatGPT
Set up an email that goes out automatically before EVERY session of an experience, e.g. "15 minutes before each class" (offsetMinutes 15). Each session gets it once, sent to the people booked at that moment, so late bookings are included; sessions with no bookings are skipped. Starts active. Confirm the timing and copy with the user before calling.

create_space

ChatGPT
Create a new space in the organization: a sub-division with its own calendar, team and permissions (a city, a brand, a team). Pass name; identifier is derived from it when omitted. Nothing public is created: the space is empty until events are moved into it with move_event. Refused when the name or identifier is already used by an active space (the response lists the existing ones), and "GENERAL" is reserved for the General space every organization has. Not idempotent: retrying a successful call is refused as a duplicate.

create_ticket_class

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the tier appears on the public event page and is purchasable in checkout the moment this returns. Pass hide_on_event_page: true to create it without showing it to buyers, or a future sales_start to hold sales until then. Delegates to the same service the dashboard uses. Pass cost=0 for a free ticket. For pay-what-you-want donations, set flexible_pricing_enabled=true, cost=0, minimum_price=0; suggested_price is optional.

delete_blast_message

ChatGPT
PERMANENTLY DELETES A BLAST MESSAGE, delivered or scheduled. A delivered one disappears from the event page's Messages section and the dashboard history, such as a test message posted by mistake; emails already delivered cannot be recalled. A scheduled message is called off so its emails never go out. There is no undo: restoring it means composing a new one. Confirm with the user before calling. Only the organizer who wrote the message can delete it.

delete_bundle

ChatGPT
Remove a bundle. It comes off sale and disappears from the list and the public page. This is a soft delete: people who already bought keep their sessions, and their bookings, refunds and history still resolve — existing holders are NOT refunded. If the bundle has sales and the organizer only wants to stop new ones, prefer update_bundle with status "archived". Confirm with the organizer first when quantity_sold is above zero.

delete_contact_list

ChatGPT
Archive a contact list and detach it from every contact on it. The CONTACTS are not deleted — only their membership of this list. Soft delete, matching the dashboard.

delete_empty_experience_sessions

ChatGPT
Bulk-delete sessions of an experience that have NO bookings. Pass experience_id; optionally session_ids to limit the sweep, and delete_recurrences: true to also remove every recurrence rule (active and paused) so the experience ends up with zero sessions and zero rules. Sessions with bookings are NEVER deleted — they are skipped and listed in the result; cancel those individually instead. Only experiences owned by this organization can be modified. This is destructive and cannot be undone through the API: confirm with the user before calling. Returns the deleted/skipped ids and the remaining session and recurrence counts.

delete_event

ChatGPT
Delete an event (soft delete: the event is hidden from the dashboard and its public page). Pass event_id. Only the primary host organization can delete; an event co-hosted by this organization is refused. An event that has not ended and has paid orders is refunded in full first, the organization covering the fees: the first call changes nothing and returns confirmation_required with the refunds and a confirmation_token; call again with the same event_id and that token only after the user confirms. Then sales close, the refunds run in the background (refunds_in_progress: true) and the event is deleted when they are done. A short balance answers refused with an add_funds_url (deposits cannot be made through MCP). This is destructive and cannot be undone through the API: confirm with the user before calling. Deleting an already-deleted event succeeds with already_deleted: true.

delete_experience

ChatGPT
Delete an experience (soft delete: the experience is hidden from the dashboard and its public page). Pass experience_id. Only experiences owned by this organization can be deleted. Sessions and bookings are NOT cancelled or refunded and attendees are NOT notified. This is destructive and cannot be undone through the API: confirm with the user before calling. An unknown or already-deleted experience is reported as not found.

delete_merch_offering

ChatGPT
Stop selling an add-on at one event or experience (soft delete of the offering). The catalog template and past orders are untouched — this only takes it off sale at that host.

delete_merch_product

ChatGPT
Remove an add-on template from the catalog (soft delete). Existing offerings and past orders still resolve. To stop selling it at one event without deleting the template, use delete_merch_offering instead.

delete_promo_code

ChatGPT
Deactivate a discount code so it can no longer be redeemed. This is a soft delete: orders that already used the code keep their discount and remain auditable.

delete_session_message_automation

ChatGPT
Delete a "before each session" message so it stops sending. Messages it already sent stay in the history. To stop it temporarily, pause it instead. Confirm with the user before calling.

duplicate_experience

ChatGPT
GOES LIVE IMMEDIATELY — there is no draft state: the copy is bookable at its own public URL the moment this returns, because the copied recurrence re-anchors to start TODAY with no end date and all sold/booking counters reset to zero. Confirm the resulting dates with the organizer rather than assuming them. Copies the definition (name, description, pricing, location, duration, capacity, booking questions, theme), its ticket classes, its recurrence schedule, and its promo codes + group discounts. Sessions, bookings, and invites are NOT copied. The copy stays in the same space as the source. Returns the new experience.

get_application

ChatGPT
Get a single form submission by ID, including all answers. Pass fields to receive only the parts of the submission the question needs.

get_attendee

ChatGPT
Get a single attendee (ticket) by ID, scoped to an event you own. Pass fields to receive only the parts of the record the question needs.

get_bundle

ChatGPT
Get one bundle by id: which experiences its sessions cover, how many have sold, its price, expiry and public URL. Call list_bundles first if you do not have the id.

get_contacts

ChatGPT
Fetch contacts with pagination and sorting. Returns contact details including name, email, phone, lists, tags, and metadata — pass fields to narrow that to only what the question needs, so a count or a segment size returns no personal data at all. organizationId is auto-resolved from your token.

get_conversion_rates_for_events

ChatGPT
Conversion rates for up to 10 events in ONE call — the tool for "which of my events converts best" or "conversion for my top 3 upcoming events". Call list_events first to get the ids. Each event reports the same figures as get_event_conversion_rate. Ids that are not in your organization are returned under meta.rejected and the rest still compute, so one bad id does not fail the call. If page_views_available is false for an event, do NOT report 0 views for it.

get_custom_field

ChatGPT
Get a single custom field definition by ID.

get_device_breakdown

ChatGPT
What event-page visitors browsed with, grouped by devices (default), browsers or os. Useful for "is my page mostly being opened on mobile". Counts page views, not registrations. event_id is required.

get_embed_snippet

ChatGPT
Generate copy-ready HTML an organizer can paste into their OWN website to embed a Gomry EVENT. Use this whenever they ask about embedding, iframes, widgets, adding Gomry to their site, or Wix/Squarespace/Webflow/WordPress. Four modes: "button" (overlay trigger), "eventPage" (full page in an iframe), "compactCheckout" (minimal widget), "calendar" (every upcoming event in the space). Returns the snippet plus the public URL and the dashboard path where the same code lives. event_id is required for every mode EXCEPT "calendar", which embeds a whole space. Return the snippet to the organizer verbatim — it is meant to be pasted, so do not reformat or summarise it. For embedding an experience (a class, workshop or bookable session) use get_experience_embed_snippet instead.

get_event

ChatGPT
Get a single event by ID. Returns 404 if the event belongs to an organization you do not have access to.

get_event_conversion_rate

ChatGPT
ONE event's conversion: total page views, unique page views (deduplicated by IP), registrations, how many visitors opened the page without registering, and both conversion percentages. Use it for "how many saw it but did not buy" or "what percentage of visitors registered". Registrations are counted ALL-TIME regardless of interval, which only bounds the page views — the response says so. CRITICAL: when page_views_available is false the Tinybird query failed; report the registration count and say view/conversion data is unavailable, never that the event got 0 views. For several events at once use get_conversion_rates_for_events. event_id is required.

get_experience

ChatGPT
Get a single experience by ID. Includes pricing, location, scheduling rules, and capacity. For the attached schedules, use list_recurrences.

get_experience_booking

ChatGPT
Get the full detail of ONE experience booking: per-seat names and check-in state, the status history (who changed it, when, and why), the answers the attendee gave on the booking form, the payment breakdown with every refund, the promo code applied, and cancellation detail including any fee charged. Needs both session_id and booking_id — bookings are stored per session, so call list_experience_bookings first to get them.

get_experience_embed_snippet

ChatGPT
Generate copy-ready HTML an organizer can paste into their OWN website to embed a Gomry EXPERIENCE — a recurring offering such as a yoga class, workshop, tour or coaching slot. Use this for "booking widget for my class", "embed my workshop", or iframes for a bookable service. Three modes: "button" (overlay trigger), "experiencePage" (full marketing card in an iframe), "compactCheckout" (minimal booking widget). experience_id is required — call list_experiences first if you do not have it. Return the snippet verbatim; it is meant to be pasted. For an EVENT rather than an experience, use get_embed_snippet.

get_experience_message_content

ChatGPT
Get the full content and status of one experience blast message by its id.

get_form

ChatGPT
Get a single form by ID, including its questions array. Use the id of each question to map to the question_id field on application answers.

get_geographic_breakdown

ChatGPT
Where an event page's visitors are located, grouped by countries (default), cities, regions or continents. Derived from visitor IP on page views, NOT from attendee addresses — a visitor who never registered still counts. event_id is required.

get_lists

ChatGPT
Get all contact lists for your organization. Returns list names, IDs, colors, and privacy settings.

get_message_content

ChatGPT
Read one blast message in full — subject, body as plain text, recipient filters, status, scheduled instant and recipient count.

get_message_history

ChatGPT
List an event's blast messages, most recent first — including ones still SCHEDULED, with the instant each will fire (scheduled_for) and its status ("scheduled", "sent", "draft", "failed"). Use it to show an organizer what is queued, and to get the message id for get_message_content or cancel_scheduled_message.

get_page_views

ChatGPT
Event-page traffic for ONE event: total page views or unique visitors, as a single total (group_by: "count") or a daily series (group_by: "timeseries"). This is WEB traffic from Tinybird — who looked at the page — which is different data from query_metrics and get_sales_trends (tickets and payments). Use both to compare views against sales. event_id is required; there is no ambient event on this surface.

get_recurrence

ChatGPT
Get a single recurrence by ID, scoped to an experience you own.

get_referrer_sources

ChatGPT
Where an event page's traffic came from, grouped by referers (default, the referring domain), referer_urls, utm_sources, utm_mediums, utm_campaigns, utm_terms or utm_contents. This is page-view attribution from Tinybird; it is NOT the same as ticket-level referral codes or promoter attribution. For every dimension at once use get_utm_traffic_report. event_id is required.

get_registration_timeline

ChatGPT
New registrations per day for ONE event over the last days (default 30), bucketed by UTC date. Counts tickets with status valid, checked_in or pending_approval. Days with no registrations are omitted rather than reported as zero. For cross-event trends over a date range use get_sales_trends instead. event_id is required.

get_subscription

ChatGPT
Get one subscription by id: price, billing interval, allowance, covered experiences, how many have sold and its public URL. Call list_subscriptions first if you do not have the id.

get_ticket_class

ChatGPT
Get a single ticket class by ID for an event you own.

get_utm_traffic_report

ChatGPT
ONE event's complete page-view attribution: all seven dimensions (referers, referer_urls, utm_sources, utm_mediums, utm_campaigns, utm_terms, utm_contents) in a single response, each as rows of value + page_views sorted by page views descending. Pass dimensions to narrow it; omit for everything. This is the tool for "give me all the UTM data for this event" or an export of raw traffic attribution — use get_referrer_sources only for a single dimension. Counts VIEWS from Tinybird, NOT registrations or revenue, and is not joined to ticket-level referral codes or promoter attribution. A dimension whose status is "error" could not be measured; do NOT report it as zero. event_id is required.

list_applications

ChatGPT
List form submissions ("applications") for the organization. THIS IS THE PRIMARY TOOL FOR ANALYZING FORM RESPONSES. Each application contains an answers array keyed by question_id (cross-reference with get_form). Filter by form_id to analyze submissions for a single form, or by a date range to count submissions over a period — and pass fields to leave the free-text answers out of the response when the question is a count rather than an analysis. Status defaults to all (Draft, Pending, Accepted, Rejected). Results are sorted by created_at newest-first by default; pass sort to change direction. With a date filter + sort, you can early-stop pagination once results fall outside the range.

list_attendees

ChatGPT
List attendees (tickets) for one of the organizer's EVENTS. Each attendee includes name/email and basic ticket metadata by default — pass fields to narrow that to only what the question needs, so a head count or a check-in rate returns no personal data. For full form submissions (answers), use list_applications with form_id instead. Status defaults to valid+checked_in. This does NOT cover experiences — experiences have bookings rather than tickets, so use list_experience_bookings for those.

list_bundles

ChatGPT
List the prepaid session packs (bundles) in this organization. A bundle sells a block of sessions spendable across one or more experiences, with the credits pooled. Returns active bundles across every space unless you narrow it with space_id or status.

list_calendars

ChatGPT
List the organization's calendars — the public pages that group events, experiences and external events under one URL with their own branding. Returns each calendar's id, name, slug and entry count. Call this first when an organizer names a calendar, so an edit targets the right one.

list_custom_fields

ChatGPT
List the organizer's custom field definitions. Filter by record_type (e.g. 'contact').

list_events

ChatGPT
List the organizer's events. Returns active events by default. Supports pagination and an optional comma-separated status filter (active, inactive). When you belong to multiple organizations, omit organization_id to see events across all of them.

list_experience_bookings

ChatGPT
List the bookings on an experience — who booked, which session, status, quantity and what they paid. Filter with status or session_id to narrow. Returns the most recent first and caps at 100 rows, so a truncated result says so in its meta rather than silently dropping bookings.

list_experience_messages

ChatGPT
List an experience's blast messages, most recent first — including SCHEDULED ones with the instant each fires, and ones sent by a "before each session" automation (automationId set). Use it to get a message id to read or cancel.

list_experience_ticket_classes

ChatGPT
List ticket classes (pricing tiers) for an EXPERIENCE. Returns active and archived classes with price, per-session capacity, approval flag, color, and the optimistic-lock version (required when updating or archiving). If the experience is in single-price mode, use_ticket_classes is false and the list is empty — pricing then comes from the experience itself. For EVENT tiers use list_ticket_classes instead.

list_experiences

ChatGPT
List the organizer's experiences (bookable services with sessions and recurrences). Returns active experiences by default. Filter by status (active, inactive). Rows carry description_preview (the first ~200 plain-text characters), not the full description — call get_experience for the whole body of one experience, and never page through every experience just to read their descriptions.

list_forms

ChatGPT
List the organizer's forms. Forms contain the question schema for application submissions — pair this with list_applications to interpret answers.

list_merch_offerings

ChatGPT
List the add-ons on sale at one event or experience — each offering with its price, currency, the product it comes from, and per-option stock (with the option/variant ids needed for update_merch_stock). hostId may be an event id or an experience service id.

list_merch_products

ChatGPT
List the organization's reusable add-on catalog (product templates): id, name, price, image, and each template's options with their ids. These are the products you offer at a specific event or experience with create_merch_offering.

list_my_organizations

ChatGPT
List the organizations you belong to. Use the id of an organization as the organization_id argument for other tools to scope a call to one specific org. GOMRY STAFF ONLY: when called by internal staff in GomryOS mode, this instead lists organizations ACROSS THE WHOLE PLATFORM (not just your own), each with country, niche, trailing-12-month volume and fees, and first event date — the same figures as the /gomryos Revenue Intelligence dashboard. Every organization_id returned works with the read-only tools even where you are not a member. total_count is the number of matches BEFORE paging, so answer "how many X" from that field rather than counting rows. Filters are ignored for non-staff callers.

list_recurrences

ChatGPT
List all schedules (recurrences) attached to an experience. Each recurrence defines a cadence, end condition, and one or more session templates that generate bookable sessions. Entries with is_one_off: true are not schedules — each carries a single date added by hand via create_session, and its weekly cadence is internal plumbing that runs once and stops. Describe the experience's schedule from the is_one_off: false entries only.

list_session_message_automations

ChatGPT
List an experience's "before each session" messages: each sends automatically N minutes (offsetMinutes) before every session to whoever is booked at that moment.

list_spaces

ChatGPT
List the organization's spaces — the sub-divisions an event belongs to, each with its own calendar, team and permissions. Returns each space's id, identifier and name, plus the General space every organization has (its id is null). Call this before moving an event so the move targets the space the organizer meant.

list_subscriptions

ChatGPT
List the recurring memberships (subscriptions) in this organization: price per period, billing interval, sessions per period (or unlimited) and the experiences they cover. Returns active subscriptions across every space unless you narrow it with space_id or status. For prepaid session packs use list_bundles.

list_ticket_classes

ChatGPT
List all ticket classes (products) for an event. Also accepts an EXPERIENCE id, in which case it returns that experience's pricing tiers and sets resource_type: "experience" — note those must be edited with the update_experience_ticket_class tool, not update_ticket_class.

move_event

ChatGPT
Move an event to another space, together with its ticket classes and promo codes. Pass event_id and the target space as an identifier, id or unambiguous name ("GENERAL" for the General space); list_spaces returns the valid values. Refused when the event has already sold tickets — attendees hold tickets tied to its current space, so the dashboard blocks that move too. Asking for the space the event is already in succeeds without changing anything (already_in_space: true).

query_metrics

ChatGPT
Flexible group-by analytics over the organization's tickets or payments. Pick a source (tickets or payments), a group_by dimension (event, day, week, month, ticket_class, status), and a metric (count, unique_contacts, sum_spend). Returns one row per group with the aggregated value plus a grand total. Examples: tickets grouped by event counted; payments grouped by month summed (sum_spend, per currency); tickets grouped by ticket_class counting unique_contacts. sum_spend requires source=payments. Defaults to the last 6 months. Spend is reported per native currency (never converted).

remove_contacts_from_list

ChatGPT
Remove one or more contacts from a list.

remove_from_calendar

ChatGPT
Remove an event, experience or external event from a calendar. This only takes it off that calendar page — the event itself, its tickets and its attendees are untouched. type says which kind of entry the id refers to.

remove_member

ChatGPT
Revoke a team member's access to the organization (or one space). Soft-deletes their permission grant — mirrors the dashboard "Remove" action. Does not delete their user account or contact record.

reorder_experience_ticket_classes

ChatGPT
Replace the tier display order on an EXPERIENCE wholesale. The order array must reference exactly the set of ACTIVE class IDs — extras, missing IDs, or archived IDs are rejected. Call list_experience_ticket_classes first to get the live IDs, then pass them all in the desired order.

reorder_ticket_classes

ChatGPT
Set the order an EVENT's ticket classes are listed in on its public page and checkout, first ID shown first (the same order the dashboard sets by drag and drop). Use it to lead with a priority ticket, e.g. a dinner ticket before a cheaper party ticket. Get the IDs from list_ticket_classes. Prices are untouched, and the "Get tickets from …" button keeps showing the lowest price. For experiences use reorder_experience_ticket_classes.

report_feature_request

ChatGPT
SENDS WHAT YOU PASS TO GOMRY'S TEAM: everything in the arguments, including the user_quote you supply verbatim, is stored and posted to an internal Gomry Slack channel. Tell the user you are logging it — never call this without saying so. Use it to log a feature request when the organizer asks for a Gomry capability that no available tool supports (e.g. an unavailable report, an unsupported automation, a missing integration). Call it BEFORE telling them it is not supported yet, then tell them you have logged the request for the Gomry team. Do NOT call it when a tool already covers the ask, when you just need to clarify what they want, or for a simple misunderstanding.

search_contacts

ChatGPT
Search contacts by name, email, or other text fields using full-text search. Returns matching contacts ranked by relevance. Pass fields to receive only the parts of each match the question needs.

send_blast_message

ChatGPT
ALWAYS EMAILS EVERY ATTENDEE of one event who matches recipient_type, now or at scheduled_for: use it for a message about that event, such as a reminder, a schedule change or venue details. There is no per-recipient confirmation and a sent email cannot be recalled, so confirm the audience and the copy with the user before calling. recipient_type picks registration statuses: ["accepted"] for people who hold a valid ticket, "pending" for those awaiting approval, "rejected" for declined ones, ["all"] (the default) for everyone registered. ticket_class_ids narrows it to specific tiers (ids from list_ticket_classes). Pass scheduled_for as an ISO-8601 instant to send later, one call per message; omit it to send now. A scheduled message can be called off with cancel_scheduled_message until it fires. Emails go out from the organization's reply-to address, and unsubscribed contacts are skipped automatically. To reach contacts who are not registered for the event, use send_contact_message instead. A WhatsApp copy goes out automatically to recipients who opted in to WhatsApp, and is NOT counted in queued: the result's whatsapp gives how many were queued, a plain status (why none, if none) and billing (null until WhatsApp billing is enforced): the free messages it uses, the estimated cost from the organization's WhatsApp balance, and copies nothing covers or that billing stopped. Recipients still get the email either way.

send_contact_message

ChatGPT
ALWAYS EMAILS the contacts you name (contact_ids) or every contact on a saved list (list_id), and also reaches them by SMS and push where they have opted in: use it for news or an announcement to the organization's contacts, whether or not they are registered for an event. A sent message cannot be recalled, so confirm the recipients and the copy with the user before calling. It does not send WhatsApp. To message the people registered for one event, use send_blast_message instead; to invite one contact to an event, use send_invite. Unsubscribed contacts are skipped automatically.

send_experience_blast

ChatGPT
EMAILS REAL PEOPLE. Sends a blast to an experience's bookers now, or once at scheduledFor. Pass sessionId to reach just one session ("remind tomorrow's yoga attendees"). Recipients are fixed when the message is queued, so people who book after a scheduled send is created will not get it. For "N minutes before every session", use createSessionMessageAutomation. Confirm the audience and copy with the user before calling. A WhatsApp copy goes out automatically to recipients who opted in to WhatsApp, and is NOT counted in queued: the result's whatsapp gives how many were queued, a plain status (why none, if none) and billing (null until WhatsApp billing is enforced): the free messages it uses, the estimated cost from the organization's WhatsApp balance, and copies nothing covers or that billing stopped. Recipients still get the email either way.

send_invite

ChatGPT
ALWAYS EMAILS THE PERSON: sends the "You're invited to {event}!" email to the contact you name and creates an invited ticket for them (no ticket class, no charge). There is no way to call this without mailing someone, so confirm the recipient with the user first. Use it for any invitation, "add to the guest list", or RSVP request. This is the dashboard "Send invitations" flow: delivery is asynchronous (queued), and recipients who are unsubscribed or already have a ticket are skipped. To create a confirmed ticket with a confirmation email instead, use create_attendee. DELIVERY: the email invite always goes out. A WhatsApp copy is sent automatically (never chosen by the caller) and only to invitees who have a phone number on file, have opted in to WhatsApp, and whose notification preferences include WhatsApp for invites (US/Canada +1 numbers default to SMS instead). The result reports whatsapp_queued and a plain-language whatsapp_status; queued does NOT include the WhatsApp copy. Answer "was a WhatsApp invite sent?" from those fields rather than assuming. The organization pays for WhatsApp (free messages each month, then billed and charged later, like Gomry Ads): whatsapp_billing (null until billing is enforced) gives the free messages used, the estimated cost, the copies that won't go out, and why billing stopped the copy (whatsapp_off, payment_failed).

set_application_status

ChatGPT
EMAILS EVERY APPLICANT YOU LIST when notify_applicant is true — up to 200 acceptance or rejection emails from a single call. notify_applicant is REQUIRED and has no default, so decide it with the user before calling. The tool approves, rejects, or returns form submissions to review, in bulk: pass one or more application IDs from list_applications and the target status. Accepting with notify_applicant true sends the form's acceptance email and adds the applicant to the form's accepted contact lists; rejecting sends the rejection email. Both only mail when the form has that template active. IDs that cannot be moved come back in failed with a reason rather than failing the whole batch.

update_application

ChatGPT
Attach or update integration metadata on a form application. metadata is a free-form key/value object — your own data (e.g. a cohort tag or external funnel stage), merged onto the existing metadata. Pass null as a value to clear a key. The application's internal status is not writable here (it drives acceptance emails and list membership). Returns the updated application with its change history.

update_bundle

ChatGPT
Edit an existing bundle. Pass ONLY what changes. To change what the bundle includes, send experience_ids AND session_count together — they define the selection jointly. To change the size options, send sizes (the FULL list, echoing back each existing size’s id from get_bundle). Changing sessions, prices or sizes affects only FUTURE buyers: anyone who already paid keeps exactly what they bought. Set status to "archived" to stop sales while keeping it readable for existing holders.

update_calendar

ChatGPT
Update a calendar's name, description, slug, branding (cover image, logo, tint colour, font, background pattern), location, social links, or its auto-add/auto-remove settings. Pass only what you want changed. Changing the slug changes the public URL, so confirm it with the organizer first. links replaces the whole object rather than merging.

update_contact

ChatGPT
Update a contact's fields. Partial update — only the fields you pass are written. Use status: 'inactive' to archive (soft-delete) a contact.

update_event

ChatGPT
Update fields on an existing event; moving start by more than 6 hours while the event has paid orders EMAILS EVERY ATTENDEE and lets every buyer cancel for a full refund for up to 48 hours (the organization covers the fees). Snake_case body, partial update — only the fields you pass are written. NOTE: venue REPLACES the existing venue wholesale rather than merging, so send every venue field you want to keep. reviews shows or hides the attendee reviews on the public event page (public) and those borrowed from past dates (past_dates); both stay on while the Distribution Program is enabled. Delegates to the canonical update service (taxonomy sync, cache invalidation, isPast recompute all fire). That date move takes two calls: the first changes nothing and returns confirmation_required with what buyers could claim and a confirmation_token; call again with the same arguments and that token only after the user confirms.

update_experience

ChatGPT
Update fields on an existing experience — the experience equivalent of update_event. Set or replace the cover image (cover_image, an uploaded https URL), swap the full photo gallery (photos, first entry is the cover), rename it, edit the description, activate/deactivate it (status), make it secret / link-only (is_private, the same setting as a private event), open/close bookings (registration_status), change the price, currency, per-session capacity or session length. Partial update — only the fields you pass are written. Changing the currency cascades to every ticket tier.

update_experience_ticket_class

ChatGPT
Edit an existing EXPERIENCE ticket class. Partial update — only the fields you pass are written. Pass the version from list_experience_ticket_classes. Capacity cannot drop below the tier's live sold count (the tool returns the real count if you try). Currency is not editable here: it stays in lockstep with the experience's currency.

update_member_role

ChatGPT
Change an existing team member's role. Overwrites the permission grant's roleID in place (same org/space scope). It cannot move someone between scopes: to do that, remove them with remove_member and re-invite them to the target scope from the Gomry dashboard.

update_merch_offering

ChatGPT
Edit an add-on offering at its host: its price, currency, and/or per-option stocks. Stock rows are upserted — options you do not list keep their current stock. To only change stock, update_merch_stock is simpler.

update_merch_product

ChatGPT
Edit a catalog add-on template: name, price, description, image, currency, or its options (add new ones with addOptions, remove existing ones with removeVariantIds). Pass only what changes. Editing the template updates it everywhere it is offered.

update_merch_stock

ChatGPT
Set the stock of an add-on offering. For an add-on with options, pass stocks with a { variantId, stock } entry per option (get the ids from list_merch_offerings); for a single-option add-on you can pass a plain stock number. Unlisted options keep their stock.

update_organization

ChatGPT
Update the organization's basic profile settings — the same fields as the dashboard's Organization Profile page: display name, description, contact email, logo, website, and social links. Pass ONLY the fields you want to change; every field is optional and omitted fields are left untouched. Pass an empty string to clear a social link or the website. For the logo, pass EITHER logo (the URL of an image already hosted somewhere) OR the image file itself as logo_base64 + content_type, which uploads it to Gomry's storage and attaches it in one step; prefer logo_base64 when the user supplies an actual file rather than a link (JPEG, PNG, WebP, or GIF; max ~3MB decoded). Social links accept either a full URL or a bare handle like "@gomry", which is expanded to that network's URL. This changes the org's public identity wherever it is shown, so confirm the new values with the user before calling. Does NOT change payment settings, webhooks, tax details, billing country, or the org URL/username.

update_promo_code

ChatGPT
Update an existing discount code. Partial update — only the fields you pass are written. The code string itself cannot be changed, because it may already be in circulation. Passing discount_amount or percent_off replaces the discount and clears the other form, since the two are mutually exclusive.

update_recurrence

ChatGPT
Update an EXISTING schedule: cadence, days of week, start time, start date, end condition, or pause it — e.g. "move the Friday class to 19:00", "end the series on Aug 31". NOTE: cadence is REPLACED wholesale — when switching a weekly schedule to monthly, send the complete new cadence, not just the changed field.

update_role

ChatGPT
Update a custom role's name, privileges, or status (active/deleted). System roles cannot be updated or deleted this way — attempting to target one returns an error. Deleting a role fails if any member is currently assigned it; reassign them first.

update_session

ChatGPT
Update ONE session: its capacity, private note, duration, or per-occurrence location. Capacity cannot drop below the number already booked. To change the whole series, use update_recurrence instead.

update_session_message_automation

ChatGPT
Change a "before each session" message: its timing, subject, body or audience, or pause / resume it with status. Pass only the fields to change.

update_sponsorship_settings

ChatGPT
Turn sponsorship on or off for ONE event or ONE experience. Pass exactly one of event_id or experience_id. enabled: false deactivates sponsors entirely (every ad placement plus the cashback program); enabled: true activates them. Or toggle features individually: post_purchase_dialog and ticket_placement (events only), experience_page (experiences only), cashback_enabled (both). This changes what attendees see at checkout and what advertisers can buy, so CONFIRM WITH THE USER before calling. Idempotent: the response lists what actually changed and the resulting state. There is no separate read tool on this surface: current_state in the response IS the current state, and a call that requests settings already in effect changes nothing and returns an empty changes list.

update_subscription

ChatGPT
Edit a subscription. Pass ONLY what changes. Price, interval and allowance changes apply to FUTURE members; existing members keep what they signed up for. experience_ids replaces the whole list. Set status to "archived" to stop new sign-ups.

update_ticket_class

ChatGPT
Update fields on an existing ticket class. Partial update — only the fields you pass are written. Sold quantity is recomputed server-side and is not settable. Supports flexible_pricing_enabled, suggested_price and minimum_price for pay-what-you-want donations; minimum_price=0 clears a previous minimum.

Capabilities

WritesInteractive

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/gomry"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/gomry)