Skip to main content
Glama
chrischall

signupgenius-mcp

by chrischall

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SIGNUPGENIUS_NAMENoOptional log label.
SIGNUPGENIUS_EMAILNoYour email address for session mode login.
SIGNUPGENIUS_BASE_URLNoOverride the JSON API base URL.
SIGNUPGENIUS_PASSWORDNoYour password for session mode login.
SIGNUPGENIUS_USER_KEYNoYour Pro API key for key mode.
SIGNUPGENIUS_LOGIN_URLNoOverride the login form host.
SIGNUPGENIUS_LEGACY_BASE_URLNoOverride the host for legacy calls.
SIGNUPGENIUS_DISABLE_FETCHPROXYNoSet to '1' to disable fetchproxy fallback (missing credentials become a hard error).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
signupgenius_get_profileA

Get the SignUpGenius profile of the authenticated user (name, email, member ID, subscription level). Useful as a first call to confirm credentials. Key mode hits /v2/k/user/profile; session mode hits /v3/member/profile.

signupgenius_healthcheckA

Resolves the credential the way real tools do, then makes one authenticated request to api.signupgenius.com. Reports which source supplied the credential, whether api.signupgenius.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a api.signupgenius.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.

signupgenius_list_groupsA

List groups created by the authenticated user. Returns groupid, title, and member count for each group.

signupgenius_list_group_membersB

List members of a SignUpGenius group (basic info: name, email, memberid).

signupgenius_get_group_memberA

Get detailed info for a group member (address, phone, email) when the member has provided it via a sign-up.

signupgenius_add_group_memberA

Add a member to a SignUpGenius group by email address. First/last name are optional. Writes data — confirm with the user before invoking.

signupgenius_list_created_activeA

List sign-ups created by the authenticated user. In session mode this returns the full list (active + expired) — filter on enddate client-side if you need only active.

signupgenius_list_created_expiredB

Alias of signupgenius_list_created_active in session mode (v3 returns active + expired together). Filter on enddate client-side.

signupgenius_list_created_allA

List ALL sign-ups created by the authenticated user (active and expired).

signupgenius_list_invitedA

List sign-ups the user has been invited to.

signupgenius_list_signedupforA

List sign-ups the user has personally signed up for.

signupgenius_legacy_get_my_signupsA

Session mode only. Returns the same sign-up listing the SignUpGenius wizard sees (via /SUGboxAPI.cfm?go=t.getMySignups). Use when you want fuller data than signupgenius_list_created_* provides.

signupgenius_report_allA

Full report for a sign-up: every slot plus the participant who claimed it (with custom-question answers when present). Requires SIGNUPGENIUS_USER_KEY (Pro subscription) — session mode is not supported for reports — AND only covers sheets the key-holder created. For slot dates, times and availability on ANY sign-up (including sheets the user did not create) prefer signupgenius_list_slots, which needs no auth.

signupgenius_report_filledA

Report for a sign-up restricted to slots that have already been filled. Requires SIGNUPGENIUS_USER_KEY (Pro subscription) — session mode is not supported for reports — AND only covers sheets the key-holder created. For slot dates, times and availability on ANY sign-up (including sheets the user did not create) prefer signupgenius_list_slots, which needs no auth.

signupgenius_report_availableA

Report for a sign-up restricted to slots that are still open/empty. Requires SIGNUPGENIUS_USER_KEY (Pro subscription) — session mode is not supported for reports — AND only covers sheets the key-holder created. For slot dates, times and availability on ANY sign-up (including sheets the user did not create) prefer signupgenius_list_slots, which needs no auth.

signupgenius_get_public_signupA

Look up a SignUpGenius sign-up by its public URL or slug (e.g. https://www.signupgenius.com/go/<urlid>-<signupid>-<vanity>). Returns the real sheet metadata: title, description, organization, category, creator + contact email, timezone, created/modified dates, whether it is an RSVP or slot-based sheet, and which custom fields a participant must supply to sign up. Requires NO SignUpGenius auth and works for sheets the user did not create. Use signupgenius_list_slots for the actual dates/times and availability — this tool returns metadata only.

signupgenius_list_slotsA

List every SLOT on a SignUpGenius sign-up — date, day of week, start/end time, title, location, capacity, how many spots are filled vs still available, and who has already signed up (with the quantity each entry consumes). Accepts a sign-up URL, slug, or numeric id. Requires NO auth and works for sheets the user did NOT create, which is exactly the case the Pro signupgenius_report_* tools cannot serve (they are key-only AND owner-scoped). This is the right tool for "what is still open?".

signupgenius_rsvpA

RSVP to a SignUpGenius sign-up (the Yes/No/Maybe-style sheets, including invitations from family/friends). WRITES DATA the organizer sees, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call sends nothing and returns the preview (sheet, response, head counts, identity) and a confirmToken, and only a repeat call with the same arguments plus that token submits — show the preview to the user and get their approval first (MCP_CONFIRM_MODE). Refuses when the signed-in member already has a response on the sheet (it can only ADD a response, so a second one would double-count) — change an existing answer in the SignUpGenius web UI. Slot-based sign-ups (e.g. "claim the 3pm slot") are NOT handled here — use signupgenius_claim_slot for those.

signupgenius_claim_slotA

Claim (sign up for) a slot on a slot-based SignUpGenius sheet. WRITES DATA the organizer sees, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call writes nothing and returns the preview (sheet, slot, identity) and a confirmToken, and only a repeat call with the same arguments plus that token submits — show the preview to the user and get their approval first (MCP_CONFIRM_MODE). For Yes/No/Maybe headcount sheets use signupgenius_rsvp instead.

signupgenius_release_slotA

Withdraw (give up) a slot the user previously signed up for. WRITES DATA — this removes a real sign-up, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call removes nothing and returns the preview (sheet, slot, whose entry) and a confirmToken, and only a repeat call with the same arguments plus that token withdraws — show the preview to the user and get their approval first (MCP_CONFIRM_MODE).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 20 tools

Disambiguation3/5

The set has clear separation between slot listing, reports, and participant actions, but the list_created_* family (active/expired/all/legacy_get_my_signups) overlaps heavily, with list_created_expired described as an alias of active in session mode. Descriptions mitigate some confusion, but an agent could easily pick the wrong listing tool.

Naming Consistency4/5

Almost all tools follow a consistent signupgenius_<verb>_<noun> pattern, with list_, get_, report_, add_, claim_, and release_ prefixes making behavior predictable. Minor deviations like legacy_get_my_signups and healthcheck break the strict pattern but remain recognizable.

Tool Count3/5

20 tools is at the heavy end, and several are redundant: list_created_expired, list_created_all, and legacy_get_my_signups overlap with list_created_active, and the three report_* tools partly duplicate slot data covered by list_slots. The core set is useful, but the surface could be trimmed.

Completeness3/5

The server covers public metadata, slot availability, reports, group management, and participant write actions like RSVP, claim, and release. Obvious gaps remain: no create/update/delete sign-up operations and no remove-group-member or delete-group tools, so organizer workflows have dead ends.

Maintenance

ActivityActive
ResponsivenessResponsive