Signupgenius Mcp

io.github.chrischallPublished by GitHub account chrischallv2.2.0Updated Nov 5, 2026

SignUpGenius for Claude — sign-ups, slots, groups, and RSVPs. Free accounts or Pro API key.

Overview

AI-generated overview

SignUpGenius MCP server that lets an assistant read sign-ups, slots and groups, and RSVP, claim or release slots on the user's behalf.

What you can do
  • Read profile, groups and group member details
  • List created, invited and personally signed-up sign-ups
  • Read public sign-up metadata and slot listings without any credentials
  • Pull Pro slot reports (all, filled, available) in key mode
  • RSVP to a sign-up, claim a slot, release a slot, or add a group member, each behind a confirmation step
When to use it
Useful when you want an assistant to check which slots are still open on a sign-up, summarize who has signed up, or handle RSVPs and slot claims for your own SignUpGenius account without opening the site.
Requirements
Runs locally as an npm package over stdio. Reading public sign-ups and slots needs no credentials. Signed-in actions need either SIGNUPGENIUS_USER_KEY (Pro) or SIGNUPGENIUS_EMAIL with SIGNUPGENIUS_PASSWORD; direct email/password accounts only, no SSO or 2FA. Alternatively the ContextMint Bridge browser extension supplies cookies from a signed-in tab. Reports require the Pro key.
Before you install
Session mode logs in with the account password, so treat the config as a secret file. Write tools (RSVP, claim slot, release slot, add group member) change data the organizer sees and are confirmed via a prompt or a preview plus confirmToken. The README notes SignUpGenius terms generally prohibit scripted access, so use it for your own account at personal scale. The fetchproxy fallback reads sign-in cookies from a browser extension.

Installation

In SourceWeft

  1. Open Signupgenius Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

signupgenius-mcp

[CI] [npm] [license]

MCP server for SignUpGenius. 15 read tools and 4 write across profile, groups, sign-ups, reports, public sign-up metadata, slot listings, RSVPs, and slot claim/release.

Reading a sign-up needs no credentials at all: signupgenius_get_public_signup (title, description, organizer, required questions) and signupgenius_list_slots (dates, times, locations, capacity, who has signed up and how many spots each entry takes) work on any public sheet, including ones you did not create. The two slot writes — signupgenius_claim_slot and signupgenius_release_slot — need a signed-in session and, like signupgenius_rsvp and signupgenius_add_group_member, never write on the first call: a client that supports MCP elicitation gets a confirmation prompt (unless MCP_CONFIRM_ELICITATION=off); otherwise the first call returns a preview and a single-use confirmToken bound to that exact write, and only a repeat call with the same arguments plus the token submits. MCP_CONFIRM_MODE (ask-user default, auto, refuse) tunes this. Set MCP_CONFIRM_ELICITATION=off for a client that says it supports elicitation but never shows the prompt (the write hangs — opencode 2.0.x); every client then gets the preview-and-token flow. Any other value stays on, with a warning on stderr.

signupgenius_claim_slot and signupgenius_rsvp sign up as the signed-in account by default: leave firstname, lastname and email out and they are read from your profile (the same call signupgenius_get_profile makes). Pass them only to sign up someone else, such as a family member. That is allowed, but the preview then carries identityDiffersFromAccount: true and an identityNote naming both identities, because the entry is still tied to your account. Every preview shows the identity under identity, with source set to account, supplied or mixed. The confirm token is bound to the resolved identity, so a preview approved for one person can't submit as another.

Three auth modes (tried in this priority order — first match wins):

  1. Pro key mode. Uses the documented Pro API key. Required only for the slot REPORT tools (filled/available/all-participants). Pro subscription needed.
  2. Session mode. Logs in with your normal email/password to call the same web API the signupgenius.com dashboard uses. Free accounts work. No SSO/2FA.
  3. fetchproxy fallback (no env vars needed). When no env vars are set, the server reads accessToken / cfid / cftoken cookies once at startup from your already-signed-in signupgenius.com tab via the ContextMint Bridge browser extension (built on fetchproxy). After that one read, all SignUpGenius API calls go directly from Node — the extension is not in the request hot path. Install the extension once (see fetchproxy fallback below), sign into SignUpGenius, and the MCP just works.

Set SIGNUPGENIUS_DISABLE_FETCHPROXY=1 to opt out of the fallback (turns missing credentials into a hard error — useful in headless CI).

Tools

DomainToolsMode
Profilesignupgenius_get_profileboth
Groupssignupgenius_list_groups, signupgenius_list_group_members, signupgenius_get_group_member, signupgenius_add_group_member (write)both
Sign-upssignupgenius_list_created_active, _expired, _all, signupgenius_list_invited, signupgenius_list_signedupforboth
Sign-ups (extras)signupgenius_legacy_get_my_signupssession only
Reportssignupgenius_report_all, signupgenius_report_filled, signupgenius_report_availablekey only

Notes on session-mode sign-up listings: the v3 endpoints signups/created, signups/invited, and signups/signedupfor return the full list in one paginated call (no separate active/expired URLs). The three signupgenius_list_created_* tools all map to the same endpoint in session mode; filter by enddate client-side. The bonus signupgenius_legacy_get_my_signups calls the same backend the SignUpGenius wizard itself uses and sometimes returns fuller data.

Reports outside key mode fail fast with a KeyModeRequiredError naming the tool, the mode required and the mode in effect, telling the user to set SIGNUPGENIUS_USER_KEY — and pointing at signupgenius_list_slots, which answers slot availability for any sheet with no auth at all.

Configuration

Session mode (recommended)

[email protected]SIGNUPGENIUS_PASSWORD=your-passwordSIGNUPGENIUS_NAME=Family               # optional, log label only

The server logs into signupgenius.com on first request, caches the JWT and session cookies, and silently re-logs in on a 401. Treat .env like a password file — it's gitignored here, do not commit.

Direct email/password accounts only. Won't work with Google/Apple/Facebook/Microsoft SSO or 2FA, same caveat as similar sibling MCPs.

Key mode (Pro only)

SIGNUPGENIUS_USER_KEY=your-api-keySIGNUPGENIUS_NAME=PTA Org              # optional

Find the user key in SignUpGenius under Pro Tools → API Management.

fetchproxy fallback (no env vars)

Install the ContextMint Bridge browser extension from its releases page (Chrome: download the chrome zip, unzip it and load it unpacked at chrome://extensions with Developer mode on. Safari isn't available yet — it will ship inside the ContextMint app, which has no public download — so use Chrome for now), sign into signupgenius.com, and remove the env block from your MCP config. The MCP reads accessToken / cfid / cftoken cookies once at startup and uses them like a session-mode login. No password copy-paste required.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).

The slot REPORT tools still require Pro key mode — SIGNUPGENIUS_USER_KEY is the only path that hits the documented v2/k Pro API. They are also owner-scoped, so they only answer for sheets the key holder created; for availability and participants on anyone's sheet use signupgenius_list_slots, which needs no auth.

Both at once

Set both Pro key and email/password. Key mode wins. Useful if you have Pro for some accounts and want reports while still using your normal login elsewhere.

Advanced overrides

Env varDefaultPurpose
SIGNUPGENIUS_BASE_URLkey: https://api.signupgenius.com/v2/k
session: https://api.signupgenius.com/v3
Override the JSON API base.
SIGNUPGENIUS_LEGACY_BASE_URLhttps://www.signupgenius.comOverride the host for /SUGboxAPI.cfm?go=… legacy calls.
SIGNUPGENIUS_LOGIN_URLhttps://www.signupgenius.comOverride the login form host.
SIGNUPGENIUS_DISABLE_FETCHPROXYunsetSet to 1 to skip the fetchproxy fallback (missing creds become a hard error).

ToS caveat

SignUpGenius's terms generally prohibit scripted/automated access. Session mode is "your own account, your own risk" — fine for personal automation but not something you should run at scale or on accounts you don't own.

Local dev

npm installnpm run buildnpm test

Point an MCP host at dist/bundle.js with the env vars above, or run npm run dev after creating a .env.

Tests: vitest, 100% line/branch/function coverage. End-to-end tests against the SignUpGenius API are not in CI by design — running them requires real credentials.

Notes

  • The Pro v2/k API authenticates via a user_key query param. The session API uses a JWT Bearer + session cookie. The client picks the right one based on which env vars you set.
  • All response envelopes are normalized to { data, message, success } (lowercase) regardless of which surface served the request — the legacy SUGboxAPI dispatcher's uppercase envelope is rewritten internally.
  • signupgenius_healthcheck reports the credential in use as credential.source, one of api key, email/password session, fetchproxy session, or <mode> (auth not configured) (e.g. session (auth not configured)) when auth setup was deferred. Changed in 2.1.9: an email/password login used to report fetchproxy session, and a deferred config used to report fetchproxy session or api key. Update anything that matches on the old strings.
  • For testing the Pro v2/k surface without an account, SignUpGenius publishes a frozen demo key: V0FzMkxZcmVOZlVnclZMVEl6dGhWQT09.

Developed and maintained by AI (Claude). Use at your own discretion.

Acknowledgement of Terms

By using this MCP server, you acknowledge and agree to the following:

1. This server accesses your own SignUpGenius account. Auth happens via your own credentials. It does not — and cannot — access anyone else's account or signups.

2. SignUpGenius's Terms of Service govern your use of this server, just as they govern your direct use of signupgenius.com. The clauses most relevant here:

Users may not bypass any robot exclusion headers or other measures we take to restrict access to the Services or use any software, technology, or device to scrape, spider, or crawl the Services.

And: "You are responsible for maintaining the confidentiality of your account user name and password… You agree to accept responsibility for any and all activities or actions that occur in connection with your User Credentials."

You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server. Notably, SignUpGenius does offer an official API for paid plans; where possible, prefer the official API over the endpoints this MCP exercises.

3. Personal, organizer/participant use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with SignUpGenius, Inc. It is a personal automation tool for an authenticated user to manage their own signups and groups. Do not use it to scrape other organizers' signups, spam participants, or bulk-add fake group members.

4. Stability is not guaranteed. This server may call internal endpoints that SignUpGenius can change without notice. If a tool here breaks, the canonical fix is to use the official API where available.

5. You accept full responsibility for any consequences of using this server in connection with your SignUpGenius account — rate limiting, account warnings, suspension, or any enforcement action. Per the ToS, everything done under your credentials is attributed to you. If SignUpGenius objects to your use, stop using this server.

This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede SignUpGenius's actual ToS.

Source: README.md at commit c765f22

Tools

20

signupgenius_get_profile

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.

Takes no parameters.

signupgenius_healthcheck

Verify credentials and upstream reachability

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.

Takes no parameters.

signupgenius_list_groups

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

Parameterssort

signupgenius_list_group_members

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

ParameterssortgroupIdrequired

signupgenius_get_group_member

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

ParametersgroupIdrequiredmemberIdrequired

signupgenius_add_group_member

Add a person to one of your SignUpGenius groups by email address (first/last name optional). WRITES DATA: the person may start receiving the group's sign-up invitations, 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 (group, email, name) and a confirmToken, and only a repeat call with the same arguments plus that token adds them — show the preview to the user and get their approval first (MCP_CONFIRM_MODE).

ParametersgroupIdrequiredlastnamefirstnameconfirmTokenemailaddressrequired

signupgenius_list_created_active

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.

Takes no parameters.

signupgenius_list_created_expired

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

Takes no parameters.

signupgenius_list_created_all

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

Takes no parameters.

signupgenius_list_invited

List sign-ups the user has been invited to. view: "brief" answers one line per sign-up (title — date — status).

Parametersview

signupgenius_list_signedupfor

List sign-ups the user has personally signed up for. view: "brief" answers one line per sign-up (title — date — status).

Parametersview

signupgenius_legacy_get_my_signups

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.

Takes no parameters.

signupgenius_report_all

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.

ParameterssignupIdrequired

signupgenius_report_filled

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.

ParameterssignupIdrequired

signupgenius_report_available

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.

ParameterssignupIdrequired

signupgenius_get_public_signup

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.

Parametersurlrequired

signupgenius_list_slots

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?".

ParametersurlrequiredonlyAvailableincludeParticipants

signupgenius_rsvp

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). Responds as the signed-in account by default: omit firstname/lastname/email unless the user is responding for someone else. A supplied identity that differs from the account is allowed but flagged in the preview (identityDiffersFromAccount) — point it out to the user. 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.

ParametersurlrequiredemailadultscommentchildrenlastnameresponserequiredfirstnameconfirmToken

signupgenius_claim_slot

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). Signs up as the signed-in account by default: omit firstname/lastname/email unless the user is signing up someone else (e.g. a family member). A supplied identity that differs from the account is allowed but flagged in the preview (identityDiffersFromAccount) — point it out to the user. For Yes/No/Maybe headcount sheets use signupgenius_rsvp instead.

ParametersurlrequiredemailcommentlastnamequantityfirstnameslotitemidrequiredconfirmTokencustomFields

signupgenius_release_slot

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).

ParametersurlrequiredmemberIdslotitemidrequiredconfirmTokenitemMemberIdrequired

Version history

15
  1. v2.2.0LatestNov 4, 2026
  2. v2.1.11Oct 16, 2026
  3. v2.1.10Oct 10, 2026
  4. v2.1.9Oct 10, 2026
  5. v2.1.8Oct 7, 2026
  6. v2.1.7Oct 5, 2026
  7. v2.1.6Oct 3, 2026
  8. v2.1.5Sep 28, 2026
  9. v2.1.4Sep 25, 2026
  10. v2.1.3Sep 23, 2026
  11. v2.1.2Sep 23, 2026
  12. v2.1.1Sep 21, 2026
  13. v2.1.0Sep 20, 2026
  14. v2.0.0Sep 18, 2026
  15. v1.8.4Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts