· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →SAIRYŌ v2.0.0
Event Management and Analytics
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Create and configure a SAIRYŌ event.
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
SAIRYŌ MCP-guided Event workflows: event creation and management, ticketing, attendees, check-in, co-hosts, checkout, transaction reporting, revenue reconciliation, analytics, publishing, ticket support and auditing. Events may include in-person or virtual experiences. Uses existing authorized SAIRYŌ MCP tools.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 3 observations
Plugin name changed from “SAIRYŌ” to “SAIRYO”. Is template instance added: “false”. App-69c97dfccdac819182320df39e3d5db4 updated; open the comparison for details. Sairyo updated; open the comparison for details. 22 more changes in the comparison.
View comparison →Plugin name changed from “SAIRYŌ” to “SAIRYO”. Is template instance added: “false”. App-69c97dfccdac819182320df39e3d5db4 updated; open the comparison for details. Sairyo updated; open the comparison for details. 21 more changes in the comparison.
View comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: create-sairyo-event description: Create, configure, visually review, publish, and verify a SAIRYO event through its MCP tools. Use when a user wants to create or copy an event; do not use for attendee-only or reporting-only requests. --- # Create a SAIRYO event Preserve the user's choices and keep the event private until publication is explicitly confirmed. 1. Call `get_event_creation_options` before collecting or writing event settings. Never guess category IDs, currencies, or supported configuration values. 2. If the user asks to reuse a prior event, retrieve that event before gathering inputs. 3. Gather only missing essentials: category, title, description, start, duration, timezone, location or public stream, admission model, currency when applicable, and poster intent. 4. Call `create_event`. It creates a private pending draft; a cover URL is optional. 5. Attach supplied poster, gallery, promotional video, video thumbnail, or tier thumbnails with the file-aware media tools. Do not ask the user to host attached files publicly. 6. Configure admission with `set_event_admission`, streaming with `set_event_streaming_configuration`, and ticket tiers with the tier tools. After every write, use the returned event version for the next write. 7. Apply only optional settings requested or confirmed by the user, including donations, co-hosts, referrals, discounts, checkout questions, and refund policy. 8. Call `get_event_publish_readiness`. Resolve blocking issues; distinguish warnings from blockers. 9. Call `render_event_publish_preview` so the user can visually review the complete stored configuration. 10. Obtain explicit confirmation to publish after showing the preview. Do not treat an earlier request to create an event as publish confirmation. 11. Call `publish_event` with `confirmed: true` only after readiness passes and confirmation is obtained. 12. Call `get_event_detail`, `get_event_ticket_tiers`, and `get_event_media` after publication. Compare the read-back with the user's requested configuration and report any mismatch. Never expose RTMP credentials, stream keys, provider secrets, private payment identifiers, or attendee PII without the required permission. ## SAIRYŌ Event / Content type handling SAIRYŌ calls the main record an Event whether the creator is setting up a scheduled gathering or a video-content experience. Ask which experience they want before requesting time, location, admission and ticket details. Use `get_event_creation_options` to establish supported types and fields. Only configure dates, streams, tiers and admissions if applicable. The promotional-video attachment tool does not, by itself, prove regular or spatial content ingestion/playback support. For a content Event requiring functionality not exposed through these tools, create only a supported draft (with authorization), then hand off remaining upload steps to the website; never publish or claim a spatial asset is processed before confirmation. ## Events also include content (regular and spatial videos) SAIRYŌ uses Events for both scheduled activities and standalone content/video listings. At discovery ask which type the user is creating. For regular or spatial primary video use the appropriate specialized skill as needed, and never conflate `attach_event_media` promotional media with primary video ingestion.
Referenced files: 1 — file references are metadata, not package contents.
--- name: find-sairyo-events-reports description: Help a user search discoverable SAIRYO events, locate events they manage, retrieve event or report references, or choose the correct record for another workflow. Use for lookup and navigation rather than event edits or payment. --- # Find SAIRYO events and reports 1. Identify whether the user is asking for managed/owned events, publicly discoverable events, or authorized report references. Do not assume visibility or access. 2. For keyword search, use `search_sairyo_events_and_reports`; for managed events use `list_managed_events` with user-requested filters. 3. Where a reference ID is returned, use `get_sairyo_event_or_report_reference` for the supported summary. Use `get_event_detail` for a manageable event when its ID is known and permitted. 4. When multiple matching events exist, show name, date and other returned distinguishing attributes; request selection instead of guessing. 5. Provide only tool-returned event URLs and report references; do not construct or invent links or financial values. 6. State when a result is private, not authorized, missing, or outside the search scope; do not treat a missing result as proof that an event was deleted. 7. Route subsequent requests to the appropriate event management, ticketing, attendee, transaction, or reporting workflow without performing an unexpected write. Purchasing tickets requires SAIRYO.live checkout; do not accept card data in chat. ## SAIRYŌ Event / Content type handling Search results for an Event may represent a live/scheduled activity or regular/spatial video content. Do not silently discard content Events from searches. Clarify whether the user wants all Events, scheduled Events only, regular videos, spatial videos, or both; only filter when the MCP query supports it and otherwise explain the limitation.
Referenced files: 1 — file references are metadata, not package contents.
--- name: manage-sairyo-event description: Edit an existing SAIRYO event, manage event media and optional settings, and safely change its visibility or publication state. Use for existing-event management, not new-event creation, attendee operations, or sales reports. --- # Manage a SAIRYO event Use live SAIRYO MCP data; do not infer permissions or stored values from user descriptions. 1. Identify the correct event via `list_managed_events` or `search_sairyo_events_and_reports`; disambiguate similar titles before acting. 2. Read `get_event_detail` and `get_event_management_context` for the current version, capabilities, and settings. Read `get_event_media` when media is involved. 3. Summarize requested edits and distinguish safe edits from destructive or public-facing actions. Ask only for missing choices. 4. Apply scoped changes with `update_event`, `set_event_streaming_configuration`, `set_event_visibility`, `set_event_sales_status`, `set_event_refund_policy`, `set_event_checkout_questions`, `replace_event_cohosts`, `replace_event_referrals`, or `replace_event_discount_codes` only as requested. Replacement tools overwrite entire corresponding sets: retrieve current state, explain the intended replacement, and avoid accidental removal. 5. For poster, gallery, thumbnail or promotional video, use `attach_event_media`, `remove_event_media`, or `get_event_media`. Never assume uploaded media is already attached. Confirm exact target before removal. 6. Use the current event version/optimistic concurrency token supplied by preceding reads or writes, if the tool requires it. On conflict, refresh and ask before overwriting newer user edits. 7. Before publishing, run `get_event_publish_readiness`, present `render_event_publish_preview`, and obtain explicit confirmation. Only then call `publish_event` and read back `get_event_detail`. 8. For cancellation, explain effects and request explicit confirmation before `cancel_event`. Do not delete financial or attendee records by assumption. 9. Verify changed fields via read-back and report any error, partial completion, or unmet prerequisite. Never expose private stream keys, passwords, internal provider secrets, or other attendees' data. ## SAIRYŌ Event / Content type handling An Event may be scheduled/live or a regular/spatial video content experience. Check its stored type and media before recommending edits. Do not treat `attach_event_media` promotional videos as proof of primary spatial-content upload support. For content-only management settings not exposed by the MCP tool, provide website guidance without claiming the modification occurred.
Referenced files: 1 — file references are metadata, not package contents.
--- name: manage-sairyo-ticketing description: Create, adjust, pause, resume, or inspect event ticket tiers, discounts, donations and sales settings. Use when a host asks about ticket availability, tier prices or quantities, promo codes, sales windows, checkout rules or ticketing configuration. --- # Manage SAIRYO ticketing 1. Locate the managed event; verify role and current version using `get_event_management_context`, `get_event_ticket_tiers`, and `get_ticket_tier_sales_status`. 2. If changing admission model or currency, check `get_event_creation_options` and existing sold ticket restrictions before `set_event_admission`. Do not invent supported IDs or currencies. 3. For a single tier, prefer `create_ticket_tier`, `update_ticket_tier`, `archive_ticket_tier`, `duplicate_ticket_tier`, `pause_ticket_tier_sales`, `resume_ticket_tier_sales`, or `reorder_ticket_tiers` as appropriate. 4. `replace_event_ticket_tiers` replaces the complete active tier set. Use only when a full replacement is explicitly intended after showing its effects. Preserve sold-ticket history. 5. Use `replace_event_discount_codes` only after reviewing the complete current set; manage donations via `set_event_ticket_donation_settings` and ticket sales via `set_event_sales_status`. 6. Confirm monetary amounts, currency, capacities, sale windows, visibility and discount impacts before write actions. Do not promise a ticket is purchasable until `get_ticket_tier_sales_status` confirms it. 7. Respect returned event versions between writes, refresh on conflict, and verify result with `get_event_ticket_tiers` and `get_ticket_tier_sales_status`. 8. Report user-facing totals and any caveats (paused, unpublished, sold out, outside sale window). ChatGPT does not process ticket purchases, payment cards, refunds, or checkout. Direct buyers to SAIRYO.live when a purchase is requested.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-attendee-operations description: Review event attendees, check in or undo check-ins, resend tickets, handle QR codes, issue complimentary tickets and export attendee data. Use for attendee lists, guest operations, entrance management and ticket delivery. --- # SAIRYO attendee operations 1. Resolve the exact managed event, check caller permissions, and use `list_event_attendees` (or `get_event_attendees` if appropriate) with necessary search, cursor and filters. Use `render_event_attendees` for interactive operations when supported. 2. For an individual, disambiguate using permitted ticket or attendee identifiers and call `get_attendee_details`, optionally `render_attendee_details`. Do not expose personal data not required for the task. 3. For check-in, use `check_in_attendee` with verified ticket ID or opaque QR token, not a guessed identity. Treat duplicate scans idempotently and convey recorded status. 4. For undo, verify target check-in, gather required reason, confirm intent, then use `undo_attendee_check_in`; inspect resulting state. 5. For resend, verify the permitted recipient and use `resend_attendee_ticket`. Do not redirect to an arbitrary third-party address. 6. For complimentary tickets, confirm event, recipient, tier, inventory and that zero-value issuance is intended before calling `issue_complimentary_ticket`. 7. Use `get_ticket_qr_code` for existing signed QR data; `regenerate_ticket_qr_code` only with explicit confirmation that it revokes a previous token. 8. For attendee export, use `export_event_attendees_csv` only after checking authorization and intended filters. Treat download links as sensitive and short-lived. 9. Clearly state whether an operation succeeded, was blocked, or needs a separate host-dashboard action. Never include ticket QR tokens, private buyer contact data, or exported attendee rows in public summaries.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-audit-support description: Investigate event changes and operational issues using authorized audit and state. --- # Event Audit and Troubleshooting SAIRYŌ Events may represent scheduled events or video content. Use the authorized MCP tools only where their contracts support the action. Identify a specific Event and authorization. Read `get_event_detail`, `get_event_management_context`, and `get_event_audit_log`; correlate with version and timestamps. For purchase issues consult `list_event_transactions`; for attendance `list_event_attendees`; for media `get_event_media` and publish readiness. Differentiate observed records from hypotheses. Do not infer server logs or root cause from an absence in an audit log. Do not mutate state during investigation unless separately asked and confirmed. Where an operation is not exposed through MCP, provide an honest website handoff rather than claiming completion.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-checkout-access description: Configure checkout questions, admission access, pricing, refunds and settings safely. --- # Configure Checkout and Access SAIRYŌ Events may represent scheduled events or video content. Use the authorized MCP tools only where their contracts support the action. Use `get_event_management_context` and `get_event_ticket_tiers` first. Review access, prices, currency, payer, ticket quantity and sale windows. Use `set_event_admission`, `set_event_checkout_questions`, `set_event_ticket_donation_settings`, and `set_event_refund_policy` only when user requests the respective changes. Confirm total intent before replacement/financial operations. Use returned versions and re-read settings. Do not assert video entitlement/one-time-pay/per-view behavior unless supported by an available tool or verified dashboard. Content Events use the same Event object. Where an operation is not exposed through MCP, provide an honest website handoff rather than claiming completion.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-cohosts-promoters description: Guide revenue splits, co-hosts, referrals, promotions and discount codes for authorized Events. --- # Co-host and promoter operations 1. Resolve the authorized Event and read `get_event_management_context`, `get_event_detail`, current co-hosts/referrals/discounts when exposed. 2. Separate promotional co-hosts, financial revenue splits, referral commissions and discount codes; never conflate a promotional code with a payout entitlement. 3. For `replace_event_cohosts`, `replace_event_referrals` and `replace_event_discount_codes`, emphasize that each operation replaces the COMPLETE authoritative list. Reconcile existing entries and show additions, changes and removals. 4. Check percentage totals, participant authorization and current Event version; seek explicit approval before any replacement or financially significant change. 5. Perform only supported authorized actions, then read back the stored configuration and summarize effects. Never invent PDF promoter-report or payout functionality that is not in the MCP inventory.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-event-analytics description: Summarize ticket sales, revenue, check-ins, refund patterns and event performance over a date range, compare managed events, and render grounded visuals. Use for KPIs, sales summaries, forecasting-style questions and operational recommendations, not changing event settings. --- # SAIRYO event analytics and reporting 1. Clarify the date range, timezone, relevant event(s), and whether the user means one event or all accessible managed events. Do not guess missing ranges when materially ambiguous. 2. For one event, use `get_event_sales_summary`; for multiple events or a period, use `get_sales_metrics_for_date_range`. Use `list_managed_events` to establish eligible scope if needed. 3. For grounded insights, use `generate_event_insights` and `render_event_insights` when available. Include the underlying source counts, freshness and caveats. 4. Compare tickets sold, gross revenue, successful refunds, net revenue, tiers and check-ins only when denominators and currencies are comparable. Never sum distinct currencies without a supported FX conversion. 5. Distinguish ticket attendees from ticketing guests, tickets sold from check-ins, and cashflows from gross bookings; do not estimate unavailable results as observed fact. 6. For requested datasets, use `export_event_insight_metrics_csv` and explain source range and scope. 7. For recommendations, ground each suggestion in observed metrics and separate facts from hypotheses. Avoid financial guarantees or fabricated trends. 8. Deliver concise KPI summary, per-event breakdown if requested, anomalies, and actionable follow-ups. Use available visual tools when they materially help; do not pretend a UI render succeeded if it failed. No transaction, ticket, or event modifications occur in this reporting skill. ## SAIRYŌ Event / Content type handling An Event might represent a regular or spatial video content experience. Use actual event type and tool metric definitions before interpreting sales as ticket admissions, views, content accesses or entitlements. The MCP inventory does not establish primary-video view or spatial-playback analytics; do not infer those from ticket sales.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-event-templates-plans description: Reuse a managed Event configuration safely and build a grounded next-step plan. --- # Event Templates and Action Plans SAIRYŌ Events may represent scheduled events or video content. Use the authorized MCP tools only where their contracts support the action. Call `get_my_management_scope` and `get_event_management_context` before reusing settings. Use `create_event_from_template` only with explicit source and confirmed subset of safe fields. It produces a private pending draft; do not imply media, attendee, discount, purchase or confidential data were copied. Use `get_event_action_plan` for versioned suggestions grounded in the event. Review `get_event_publish_readiness` and request explicit approval before publish. Where an operation is not exposed through MCP, provide an honest website handoff rather than claiming completion.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-publishing-readiness description: Validate readiness for either live Events or video-content Events before public release. --- # Publish SAIRYŌ Events and Content safely Use this for publication or visibility changes involving scheduled events, on-demand regular video or spatial video Events. 1. Determine the Event's actual content classification and identify the record via `list_managed_events`, `get_event_detail` or authorized lookup; do not infer content type solely from its title. 2. Read `get_event_management_context`, current tiers, media, and payout state. Check `get_event_publish_readiness`; report blocking issues verbatim. Do not bypass requirements by changing content type. 3. For Apple spatial video, inspect processing/validation results. Backend may require `.aivu` input or `mediaStatus=READY` and `mediaProfile=SPATIAL_RECTILINEAR`; confirm on the actual record, not via inference. 4. Use `render_event_publish_preview` if available. Show visibility, dates, prices, access, media and any limitations. Seek explicit user approval immediately before publication. 5. Publish with `publish_event` only when supported for the selected Event type and user has approved. Verify with `get_event_detail` and explain any remaining content playback limitations. 6. Never claim the content itself has been uploaded, trans-coded or playback-tested just because the Event record was published; use website workflow when APIs do not expose primary media processing.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-revenue-reconciliation description: Reconcile Event and video-content sales, refunds, fees and settlement statuses without double-counting. --- # Reconcile SAIRYŌ revenue 1. Identify whether the Event record represents a scheduled event or video content; request period, event IDs, currency and gross/net/payout measures. 2. Use `get_event_sales_summary`, `get_sales_metrics_for_date_range`, `list_event_transactions`, `get_transaction_details`, `generate_event_insights` and authorized CSV exports when relevant; respect access scopes. 3. Compare paid/successful transactions to gross sales; reconcile refunds, fees and net earnings. Do not equate net revenue with paid-out Stripe balance. 4. For paid videos, verify that the selected content Event is actually included in the Event-level datasets; the current 64-tool MCP catalog does not separately expose video playback, content entitlements or content-specific payout ledger. 5. Distinguish historical data, report freshness, refunds in flight and settlement delay. Do not mix currencies or count the same video-Event transactions in both Event and Video buckets. 6. Where metrics are not exposed, request a SAIRYŌ dashboard CSV and give a reproducible reconciliation rather than guesses. Exports may contain PII; only reveal permitted fields.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-ticket-delivery-qr description: Assist hosts with ticket delivery, QR regeneration, and complimentary tickets. --- # Ticket Delivery and QR Support SAIRYŌ Events may represent scheduled events or video content. Use the authorized MCP tools only where their contracts support the action. Use `list_event_attendees`, `get_attendee_details`, and `get_ticket_qr_code` when authorized. Check purchaser/ticket and QR state first. `resend_attendee_ticket` and `regenerate_ticket_qr_code` have real-world effects; confirm user intent, including regeneration invalidating the old token. `issue_complimentary_ticket` changes inventory; explain effect and confirm. Never expose underlying QR secrets or personal information beyond authorized context. Verify result and explain next action. Where an operation is not exposed through MCP, provide an honest website handoff rather than claiming completion.
Referenced files: 1 — file references are metadata, not package contents.
--- name: sairyo-transaction-operations description: Find and reconcile event transactions, payments, discounts, fees and refunds, show transaction details, or export filtered transactions. Use for host-side purchase records and transaction inquiries, not to execute payments or refunds. --- # SAIRYO transaction review 1. Identify the authorized event and obtain a clear date/currency/payment-status scope. 2. Retrieve paginated transactions with `list_event_transactions`; use `render_event_transactions` for a visual, searchable table where available. 3. For a selected transaction, use `get_transaction_details` and/or `render_transaction_details`; reconcile item subtotal, discounts, taxes, fees, donations, refunds, net, status and currency using returned figures. 4. Do not conflate gross, net, paid, refunded and pending amounts. State data freshness and any unavailable figures. 5. For exporting, request the intended date and status filters, then use `export_event_transactions_csv` and `get_transaction_export_status` as needed until the export is ready. Do not claim a pending export is complete. 6. Use least-privilege disclosure; avoid revealing full buyer details or provider payment identifiers without explicit authorization and need. 7. Do not promise to refund, capture payment, charge cards or fulfill tickets. Those operations are handled on SAIRYO.live and are not covered by these tools.
Referenced files: 1 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugin_asdk_app_69c97dfccdac819182320df39e3d5db4
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.