← Plugin catalog
Business & Operations

Swoogo

Swoogo v1.0.1

Manage your events with Swoogo

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Event briefings
  • Registration assistance
  • Agenda management

Cost & access

The plugin does not process payments or purchases. Billing tools only read existing line items and transactions; they do not charge or refund attendees.

Declared limitations

  • Payment processing is unsupported. Explain the limitation without calling any mutating tool or claiming a charge succeeded.
  • Collecting passwords in chat or the embedded registration UI is unsupported, even when an event question is optional. Do not solicit, generate, echo, or submit a password through an MCP tool. Explain that password setup belongs on the event's external registration website and offer a verified event link when available. Password metadata for an external website builder is not permission to collect its value in chat.
  • Email campaign authoring is unsupported. Explain the limitation without invoking transactional email tools as a substitute or claiming a campaign was sent.

Onboarding example

List my Swoogo events.

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.

View package source →

Description

From the marketplace listing

Connect your Swoogo account to find events, prepare event briefings, assist with registrations, manage sessions and speakers, and report on registration trends and session attendance. Built for event teams working with their existing Swoogo data. Includes guided workflows for account setup, event briefings, registration assistance, agenda management, and attendance reporting. Access follows the connected account's permissions. Updates and registrations change live Swoogo records when requested. The plugin does not process payments or refunds. Large reports may be partial when the server returns a data limit; workflows surface those limits.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 17, 2026. Last seen Nov 17, 2026.

Keywords

Files & skills

File archives

Plugin package15 files · 20.6 KBBrowse files →
Skill instructions
agenda-management2.82 KB

View saved version →

---
name: agenda-management
description: Review or update a Swoogo event agenda, create or edit sessions, and add or update speakers. Use for schedule changes, room or speaker conflict checks, and agenda maintenance; not for attendee session enrollment or creating an event website.
---

# Manage sessions and speakers

Read [the shared workflow rules](../../references/workflow-rules.md).

1. Resolve the event, then read `swoogo_get_events` for event dates and timezone. Read affected sessions with `swoogo_get_sessions`; use `expand: speakers` when assignments matter. Complete the relevant date's pagination before declaring no schedule conflicts.
2. Resolve existing speakers through `swoogo_get_speakers` and, where needed, `swoogo_get_contacts`. Inspect current details before editing. A speaker profile is backed by an account contact, so changing profile fields can affect that contact elsewhere.
3. Turn the request into specific field changes. Session dates use `YYYY-MM-DD`; times require `HH:MM:SS`, in the event's timezone. Resolve ambiguous dates/timezones and material conflicts before writing. Use actual returned room/speaker identities; a guessed match is insufficient.
4. Check overlap for the same room or speaker using intervals where start is before the other end and end is after the other start; adjacent sessions are not an overlap. Missing dates, times, or assignments make the check incomplete. Do not claim the server enforces all conflicts or assume parallel sessions in different rooms conflict.
5. Use `swoogo_create_session` with `event_id` and `name` for a requested new session. Use `swoogo_update_session` with `session_id` for edits, sending only changed fields. Check for an existing matching session before creating or retrying a create. Use `swoogo_fields_get` with `object: session` for custom field choices.
6. For a requested new speaker, use `swoogo_speakers_create` with `event_id` and either a resolved `contact_id` or supplied email/name. Include `session_ids` only for requested assignments. Supplying profile fields can overwrite an existing contact; omit unrelated fields. A `session_error` may mean the speaker was created but an assignment failed: report that partial success and do not repeat the create.
7. Use `swoogo_update_speaker` for requested profile changes to an existing speaker. Follow live schemas for any assignment change; do not invent an assignment endpoint or duplicate a speaker to work around a missing operation.
8. Read back affected sessions/speakers. Show saved dates, times with timezone, room, and assignments; report failed operations separately. Do not send emails unless requested.

For review-only requests, return an agenda and specific findings without writes. For edits, summarize the actual before/after values and unresolved conflicts. Do not claim that a room is available outside the data inspected.

Referenced files: 1 — file references are metadata, not package contents.

attendance-reporting2.47 KB

View saved version →

---
name: attendance-reporting
description: Analyze Swoogo session check-ins, attendance rates, and no-show patterns for an event. Use for attendance comparisons and post-event reporting; not for recording check-ins, changing attendance, or assuming registration counts equal attendance.
---

# Report session attendance

Read [the shared workflow rules](../../references/workflow-rules.md).

1. Resolve the event and requested sessions. Read event dates/timezone and sessions with `swoogo_get_events` and `swoogo_get_sessions`, using `session_id` for detail or `event_id` for a paginated list.
2. Call `swoogo_session_attendance_stats` with `event_id` and optional `session_id`. It automatically reads at most 1000 attendance records. Report any `_warning`; a session filter may still hit the cap.
3. Map session IDs to names. Report total attendance records, checked-in records, and returned rates. The tool's `registered` value counts attendance records, and its rate is checked-in records divided by those records. It is not a denominator of all event registrations, session capacity, or unique attendees.
4. For a complete result beyond the cap, paginate `swoogo_get_session_attendance` with the event and optional session filter until complete, requesting only fields needed for the calculation. Recompute rates from complete records and show the denominator. If full data is unavailable, retain a clear partial label rather than extrapolating.
5. For session fill or registration-to-attendance comparisons, separately fetch session registration counts using `swoogo_get_sessions` with `expand: registrantCount`. For event registration totals use `swoogo_registrations_get`. Label each measure and do not mix their denominators. Deduplicate by returned registrant IDs only if the user requests unique attendees and the full relevant dataset is available.
6. A missing check-in is not evidence of a real no-show for a future or ongoing session. Use event timezone and session end times to distinguish pending check-ins from post-session unchecked records. Do not infer missing duration, checkout time, or reasons for absence.

Deliver a session comparison with checked-in counts, denominators, rates, and completeness. State the reporting time and event timezone. Offer operational observations supported by the data, without changing check-ins or emailing attendees. If the user separately requests attendance writes, use the appropriate live tools within that authorization rather than treating the report as permission.

Referenced files: 1 — file references are metadata, not package contents.

event-briefing2.4 KB

View saved version →

---
name: event-briefing
description: Prepare a Swoogo event overview, readiness audit, or registration trend briefing from live event data. Use for event status, agenda gaps, registration counts, or planning summaries; not for applying changes or attendee-level exports.
---

# Prepare an event briefing

Read [the shared workflow rules](../../references/workflow-rules.md).

1. Resolve the event and any requested reporting dates. If no event is specified, use available conversation context or list accessible events so the user can select one.
2. Call `swoogo_get_event_bundle` with `event_id` for the initial event, sessions, speakers, sponsors, registration types, packages, and questions. The bundle fetches initial pages and may omit records or return component errors. It is a starting snapshot, not proof of completeness. Use the corresponding list tools and their pagination for a complete audit.
3. For registration totals or trends, call `swoogo_registrations_get` using `event_id` and, when useful, `group_by: day`, `week`, `month`, or `reg_type`. Use `date_from` and `date_to` in `YYYY-MM-DD` format. Do not pass an email for an aggregate briefing. The schema does not support grouping by source.
4. Map registration type IDs to names from the bundle or `swoogo_registration-types_get`. The aggregate total comes from pagination metadata, but grouped counts cover at most 5000 records. Surface `_warning`; narrow date windows if complete grouped counts are needed. Weekly buckets begin Sunday.
5. Check only requested readiness areas: event dates/timezone, incomplete session details, speaker assignments, capacity versus registration counts, and form requirements. Use `swoogo_get_sessions` with `expand: registrantCount` for session registrations; those counts differ from attendance. Fetch detail before calling a field absent. Capacity zero means unlimited for sessions.
6. For form audits, inspect `swoogo_get_registration_form`; report observed required fields, choices, and validation constraints. Do not infer conversion rates or claim a form change would produce a measured lift without supporting data.

Deliver a concise briefing with event identity and dates, key counts and reporting scope, agenda/readiness findings, and prioritized suggested next actions. Identify missing, failed, and partial data separately from zero. Keep this workflow read-only; hand requested edits to the appropriate registration or agenda workflow.

Referenced files: 1 — file references are metadata, not package contents.

get-started1.64 KB

View saved version →

---
name: get-started
description: Connect or troubleshoot the Swoogo plugin and verify access to the user's events. Use for initial setup, missing Swoogo tools, or authentication errors; not for unrelated Codex configuration.
---

# Get started with Swoogo

1. Read [the shared workflow rules](../../references/workflow-rules.md).
2. Use the host's plugin connection flow for the bundled `swoogo` MCP server at `https://mcp.swoogo.com`. Have the user finish Swoogo sign-in and OAuth consent in the host or browser. Never request passwords, API secrets, or tokens in chat.
3. Discover the connected tools. Use the exposed tool names and schemas; the host may add a namespace to the `swoogo_` names. If connection is still pending, report that state instead of claiming access or creating another plugin.
4. Once connected, call `swoogo_get_events` with `per_page: 5` for a small read-only check. An empty successful result verifies the connection but does not prove the account contains no events beyond the user's permissions.
5. Show the returned event names, IDs, dates, and status, labeling the list as a sample when more pages exist. Offer the appropriate workflow: an event briefing, registration assistance, agenda management, or attendance reporting.

On 401, reconnect using OAuth. On 403, explain the missing permission and use the existing Swoogo administrator/support route. On rate limits, respect retry guidance. Do not change authentication settings, bypass permissions, register anyone, send email, or write a record to test access.

Finish with the connection result and one useful next action. Never report setup as verified before a successful authenticated read.

Referenced files: 1 — file references are metadata, not package contents.

registration-assistance4.6 KB

View saved version →

---
name: registration-assistance
description: Register an attendee for a Swoogo event, update an existing registration, or manage that attendee's session selection. Use for attendee registration requests and registration troubleshooting; not for bulk marketing, payment processing, or aggregate reporting.
---

# Assist with registration

Read [the shared workflow rules](../../references/workflow-rules.md).

1. Resolve the event and attendee. Reuse profile details the user has supplied or authorized. Ask only for missing required non-password answers or ambiguous choices. Never ask for account passwords or other authentication credentials in chat or an embedded form. Never invent attendee details, dietary preferences, consent, or eligibility; use fictional data only for an explicitly requested test.
2. Call `swoogo_get_registration_form` for field definitions, choices, and validation. This tool also supports external website builders and may return password-field metadata. For chat registration, exclude any password field identified by its type, name, or label, including custom field IDs. Never place password values in `additional_fields`, other MCP arguments, generated defaults, or chat. Keep its submission token private. Resolve registration types and prices using `swoogo_registration-types_get` with `include_pricing: true` when needed. Do not assume every event or type is free.
3. Call `swoogo_get_registrants` with `event_id` and the exact email before creating. If a matching registration exists, report it or update it as requested. Clarify multiple matches; never create a second registration just to avoid resolving the first.
4. For a new registration, call `swoogo_create_registrant` with `event_id`, `email`, and supported common fields. Put `reg_type_id`, `job_title`, `phone`, and discovered custom fields in `additional_fields`; map choices to the actual IDs. Set `send_email` true only when the user requested a confirmation email, otherwise false. If the user wants to fill a form themselves and requests a confirmation email, use `swoogo_registration_form` instead of also creating the registration. The current embedded form submits with `send_email: true`; for registration without email, use the programmatic create workflow with `send_email: false`. The hidden submit tool belongs to the UI.
5. For an existing registration, read it and call `swoogo_registrants_save` with `registrant_id` and only requested changes. This update tool accepts `reg_type_id` and `job_title` at the top level. A cancellation must be explicitly requested; do not substitute it for deletion or a refund.
6. Resolve requested sessions with `swoogo_get_sessions`. Check event membership, times, availability, and the attendee's current selections. For a normal session addition, first call `swoogo_add_registrant_to_session` with `validate_only: true` and without `waitlist`. On successful validation, commit the requested addition with `validate_only: false`. Do not override capacity unless specifically authorized.
7. A waitlist is a different outcome from enrollment. Use `waitlist: true` only when requested or after the user chooses it. Never combine waitlist with a validation-only check: the server ignores other options when waitlist is true and writes immediately. For removals/moves, use the update tool's `remove_session_ids`/`add_session_ids` after resolving the requested IDs; inspect partial results and read back selections before retrying.

If there is a charge or payment requirement, explain it and use a verified Swoogo event/registration link for the user's next step; never collect payment-card details or claim payment succeeded. Report the actual registration ID/status and confirmed session or waitlist outcomes. If a create times out, search by event and email before retrying. A confirmation email request is not proof of delivery.

An optional password question must not prevent registration: omit it and submit the other supported answers. A password d

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Release notes

Version 1.0.1 prepares resubmission after the registration password-field review. Registration skills explicitly exclude password collection in chat and MCP tool inputs, allow registration without an optional password, and direct required password setup to the external event website. Review cases now demonstrate the password-free in-chat form and refusal to add an embedded password input. External website builders may use password-field metadata, with values submitted directly from the attendee's browser to the registration API. Requires the separately deployed MCP changes from Swoogo PR #149. Swoogo branding, five skills, worldwide availability, and no-payment behavior are retained. Review fixtures and the demo URL are included. The accompanying MCP source also corrects registration-type grouping when the API returns expanded { id, value } objects; deploy that server fix before rerunning the briefing case.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Swoogo
Keywords
See keywords
Declared availability
No country restrictions declaredDeclared regions; live availability may differ.
Getting started skill
./skills/get-started/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Event briefings
  • Registration assistance
  • Agenda management
  • Attendance reporting

Package observed Nov 17, 2026.

Technical details
First seen
Nov 17, 2026 · 00:00 UTC
Last seen
Nov 17, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6af6336b8b60819192e81fbcfbe45857

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.