signupgenius-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNUPGENIUS_NAME | No | Optional log label. | |
| SIGNUPGENIUS_EMAIL | No | Your email address for session mode login. | |
| SIGNUPGENIUS_BASE_URL | No | Override the JSON API base URL. | |
| SIGNUPGENIUS_PASSWORD | No | Your password for session mode login. | |
| SIGNUPGENIUS_USER_KEY | No | Your Pro API key for key mode. | |
| SIGNUPGENIUS_LOGIN_URL | No | Override the login form host. | |
| SIGNUPGENIUS_LEGACY_BASE_URL | No | Override the host for legacy calls. | |
| SIGNUPGENIUS_DISABLE_FETCHPROXY | No | Set 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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_membersA | 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. |
| 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). Walks the PreProcessSignup → getSignupInfo → processSignUpFormHandler flow under the hood. Writes data — confirm with the user before invoking. 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. Two-step by design: call WITHOUT |
| signupgenius_release_slotA | Withdraw (give up) a slot the user previously signed up for. Call WITHOUT |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
The tool set has clear overlap: signupgenius_list_created_active, signupgenius_list_created_expired, and signupgenius_list_created_all all list sign-ups created by the user, with the expired variant explicitly documented as an alias of active in session mode. signupgenius_legacy_get_my_signups also returns a similar listing, adding further confusion. While other tools (rsvp vs claim_slot, reports vs list_slots) are well-separated, these four listing tools create real ambiguity for an agent.
All tools follow a consistent prefix (signupgenius_) and snake_case verb_noun pattern (e.g., list_groups, get_profile, claim_slot). The naming is predictable and descriptive. Minor deviations like 'healthcheck' (noun as verb) and the long 'list_created_all' suffix are acceptable, but the overall pattern is strong.
20 tools is on the higher end of the scale (16-25 feels heavy). The server covers a broad domain—profiles, groups, sign-up listings, reports, slots, and participation actions—so the count is not egregious, but some tools are redundant (list_created_* variants) and could be consolidated. It's borderline appropriate.
The tool surface covers core workflows: authentication verification, group management (list, members, add), sign-up listing (created/invited/signed up), reporting, slot availability, and participation (RSVP, claim, release). However, notable gaps exist: no tool to remove a group member, no creation/update/delete of sign-ups, and reports are limited to key-holders only. Agents can work around most gaps but may hit dead ends for group removal or sign-up management.