SignUpGenius MCP Server
Crea inscripciones, gestiona horarios y envía mensajes a los participantes en SignUpGenius.
Servidor MCP alojado
npx add-mcp 'https://cotlet.dev/mcp/v1/signupgenius'Se instala en Claude Code, Codex, Cursor y más
Documentación
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
SignUpGenius API and MCP server: Let your AI agent fill your SignUpGenius slots.
SignUpGenius has an official API for paid plans, but no MCP server of its own, and its API cannot create a sign-up, add a slot, move a participant or send a message (checked 24 Oct 2026). Of its 12 documented endpoints, 11 read and one adds a group member. Cotlet runs 15 SignUpGenius tools hosted, over MCP for agents and REST for scripts.
Read SignUpGenius sign-ups, slots and participants through MCP or REST. Connect your organizer account to an agent, reporting workflow or script.
- Free 7-day trial, no card
- Unofficial, not affiliated with SignUpGenius
- Page: https://cotlet.dev/integrations/signupgenius-api-mcp-server
What can you automate in SignUpGenius?
- Build a sign-up from one message
- Rebuild last year's sheet on new dates
- List empty slots in the next two weeks
- Email people who have not signed up
- Move someone to another shift
- Add new families to a group
Does SignUpGenius have an MCP server or an API?
- API calls per day: none on Free, 500 on Silver, 2,000 on Gold, 5,000 on Platinum.
- Zapier has three triggers (new slot filled, new event, new group member) and group member actions. Nothing creates a sign-up or emails anyone.
- A free MCP server on GitHub signs in with your password. It covers the participant side: claim a slot, RSVP, read reports.
| What you need | Official API | Zapier | Cotlet |
|---|---|---|---|
| List sign-ups and who took which slot | Yes, Silver and up | New slot filled trigger | Yes, any plan |
| Create a sign-up and add slots | No | No | Yes, as a draft |
| Move or remove a participant | No | No | Yes, after your OK |
| Email people who have not signed up | No | No | Yes, after your OK |
| Add someone to a group | Yes | Yes | Yes |
| The route SignUpGenius provides | Yes, official | Yes, official app | Uses the web app |
Checked 24 Oct 2026. Sources: SignUpGenius API portal, SignUpGenius API docs (v2.0, key-based), SignUpGenius pricing (API row), Zapier: SignUpGenius integrations, chrischall/signupgenius-mcp on GitHub
How does Cotlet connect to SignUpGenius?
- Sign in to SignUpGenius. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your SignUpGenius password, and no email, sign-up link or slot change reaches a volunteer until you approve it.
Connect SignUpGenius to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Turn on SignUpGenius for agents. Make a Cotlet account, log in to your SignUpGenius organizer account in its Cloud Browser, then press Enable for agents.
- Give your agent the address. Add https://cotlet.dev/mcp/v1 where your agent lists MCP servers or connectors.
- Confirm who is connecting. Chat apps send you through a Cotlet sign-in. Code editors, n8n and scripts use an API key from the console.
The shared address https://cotlet.dev/mcp/v1 carries SignUpGenius along with every other app you enabled. Enabled SignUpGenius after you connected? Refresh the connector and the new tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-signupgenius \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-signupgenius": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-signupgenius]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: signupgenius_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: signupgenius_write
How to use the SignUpGenius REST API
Create your Cotlet API key
Sign in to SignUpGenius in its Cotlet Cloud Browser and enable the app for agents. Use your SignUpGenius organizer login.
Create a Cotlet API key with access to SignUpGenius and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Make your first SignUpGenius API request
cURL: list_signups:
curl "https://cotlet.dev/api/v1/signupgenius/signups?limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read sign-ups and follow the cursor
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "signupgenius",
"tool": "list_signups",
"result": {
"signups": [
{
"signup_id": "50463821",
"title": "Spring bake sale",
"status": "active",
"group": "PTA",
"filled": 9,
"wanted": 12,
"next_date": "2027-05-09"
}
],
"next_cursor": null
}
}
Read result.signups and pass result.next_cursor unchanged as cursor until null. Pages default to 25 records, with a maximum of 100.
Active sign-ups are the default; request the drafts status to include drafts. Keep filters and limit fixed while paging.
Use get_signup with open_only=true for open slots. Participant reads have date filters but no cursor; retain slot quantities instead of treating every row as one person.
SignUpGenius workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read sign-ups and open slots into an open-shift report, comparing filled and wanted quantities. |
| Make | HTTP > Make a request | Read participants and slot details into an event roster with times, quantities and custom answers. |
| Python or Node.js | REST API | Compare group members with participants to prepare a volunteer follow-up list without messaging anyone. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads SignUpGenius; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
SignUpGenius API endpoints and MCP tools
Sign-ups and slots
New sign-ups and copies start as drafts that nobody sees. Every slot needs a fixed number wanted; SignUpGenius no longer takes "unlimited".
- List sign-ups (
list_signups, read): Sign-ups you created, with title, group, dates and how many slots are filled. - Get sign-up (
get_signup, read): One sign-up with its description, link and every slot: title, date, time, location, wanted and filled. - Create sign-up (
create_signup, write): New sign-up saved as a draft. Nothing is visible or sent until you publish it. - Add slots (
add_slots, write): Add slots (roles or tasks) to a sign-up, on one or more dates and times. - Update slot (
update_slot, write): Change a slot's title, quantity, location or help comment. Quantity cannot go below the people already signed up. - Duplicate sign-up (
duplicate_signup, write): Copy a sign-up with a new title. The copy is an unpublished draft. - Publish sign-up (
publish_signup, write, asks first): Make a draft sign-up live and return its public link. Does not send invites.
Participants
Only on sign-ups you created. A full slot refuses a new name, and a slot cannot shrink below the people already in it.
- List participants (
list_participants, read): Who signed up for which slot, with name, email, quantity and answers to custom questions. - Add participant (
add_participant, write, asks first): Sign someone up for a slot as the organizer, from a group or as a new person. - Move participant (
move_participant, write, asks first): Move a participant from their slot to another open slot on the same sign-up. - Remove participant (
remove_participant, write, asks first): Delete a participant from a slot.
Groups and messages
Emails count toward your plan's monthly cap: 1,000 on Free, 2,500 on Silver. SignUpGenius may hold a message for review before it goes out.
- List groups (
list_groups, read): Your groups (the people you invite) with member counts. - List group members (
list_group_members, read): Members of a group with name and email. - Add group member (
add_group_member, write): Add a person to one of your groups so you can invite them later. Sends nothing. - Send message (
send_message, write, asks first): Email the people on a sign-up: everyone, those who signed up, or those who have not.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/signupgenius-api-mcp-server#tools
Who can see my SignUpGenius session, and how do I revoke it?
- What we store. Your logged-in SignUpGenius profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. The 15 SignUpGenius tools. Never the session cookie.
- What the session sees. Your sign-ups, groups, participant names, emails and answers.
- What no tool touches. Payments, payouts, your plan, password and deleting sign-ups.
- Google, Apple or Microsoft login. Works too. You finish the provider's sign-in yourself.
- How to cut access. Press Disable for agents, or reset the Cloud Browser to log it out.
Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.
Is it against SignUpGenius's terms? Account safety
You agree that you will not under any circumstances: ... make any automated use of the Site or Services, or take any action that we deem to impose or to potentially impose an unreasonable or disproportionately large load on our servers or network infrastructure
The same terms let SignUpGenius suspend an account "without prior notice ... for any reason whatsoever". The clause is broad: it reaches Cotlet, the GitHub MCP server and any script alike, and only the official API is plainly allowed, for reads. We found no public case of a SignUpGenius account closed for automation (checked 24 Oct 2026). The author of the GitHub server calls it "your own account, your own risk"; that holds for us too.
How we keep your account looking like you:
- Your own organizer account, logged in by you
- One Cloud Browser with a steady IP and cookies, not a fresh login per call
- Calls at a person's pace, one sign-up at a time
- Emails, publishing and participant changes wait for your OK
- If SignUpGenius objects, we pause the SignUpGenius tools for everyone within 24 h
Email only your own groups and people who joined a sign-up. SignUpGenius staff review some messages, and a burst to a large list is the likeliest thing to get held.
What happens when SignUpGenius changes?
- 12 h between tests of the SignUpGenius reads and drafts
- 24 h between tests of emails and changes a volunteer would see
- $0 for a call to a SignUpGenius tool paused for repair
When SignUpGenius moves a tab on the sign-up builder or renames a form field, we repair the tool on our side and your prompts keep working. status.cotlet.dev watches the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Reads the message. Roles, dates and head counts; a missing time means a question.
- Matches the group. Two close group names stop the run instead of a guess.
- Saves a draft. Slots go onto an unpublished sign-up nobody can see.
- Waits for your OK. Publishing and the invite email show up in your console first.
| Action | Undo |
|---|---|
| Create or copy a sign-up | Delete the draft in SignUpGenius |
| Add or edit a slot | Edit it again; nobody is told |
| Publish a sign-up | Edit it in SignUpGenius; the link was public in between |
| Move a participant | Move them back; with notify on, they got an email |
| Remove a participant | Add them again, if the spot is still free |
| Send a message | No, the email is out once it leaves review |
5 of 15 tools ask first: publish_signup, add_participant, move_participant, remove_participant and send_message, the ones a volunteer can see or get an email from. Drafts, slots and group adds reach nobody, so they run at once. Switch the wait off per tool for a Monday reminder run.
Publishing invites no one. The group hears about a sign-up only through send_message or a link you share.
MCP call:
{
"name": "add_slots",
"arguments": {
"signup_id": "50463821",
"title": "Bake sale shift",
"quantity": 4,
"dates": [
"2027-05-09T09:00:00-04:00",
"2027-05-09T11:00:00-04:00",
"2027-05-09T13:00:00-04:00"
],
"location": "School lobby",
"help_comment": "Bring a float of small bills."
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/signupgenius/signups/50463821/slots \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"title":"Bake sale shift","quantity":4,"dates":["2027-05-09T09:00:00-04:00","2027-05-09T11:00:00-04:00","2027-05-09T13:00:00-04:00"],"location":"School lobby","help_comment":"Bring a float of small bills."}'
Tool output:
{
"signup_id": "50463821",
"status": "draft",
"slots_added": 3,
"slots": [
{
"slot_id": "3381902441",
"start": "2027-05-09T09:00:00-04:00",
"title": "Bake sale shift",
"wanted": 4,
"filled": 0
},
{
"slot_id": "3381902442",
"start": "2027-05-09T11:00:00-04:00",
"title": "Bake sale shift",
"wanted": 4,
"filled": 0
},
{
"slot_id": "3381902443",
"start": "2027-05-09T13:00:00-04:00",
"title": "Bake sale shift",
"wanted": 4,
"filled": 0
}
]
}
A script or cron job calls the same tools over REST at /api/v1/signupgenius, with the same key and price. Text messages need a paid SignUpGenius plan, so send_message sends email only; a call that fails costs nothing. The tools table lists the REST path of each tool.
How much does the SignUpGenius MCP server cost?
About $13 a month for a PTA coordinator running 3 new sign-ups a month, 2,190 credits. SignUpGenius bills its own plan as before, and Free works.
| Job | Calls | Credits |
|---|---|---|
| New sign-up from a message | 5 × 3 | 150 |
| Copy last year's sign-up and publish | 3 × 1 | 30 |
| Open-slots email, weekly | 6 × 4 | 240 |
| Move someone to another shift | 3 × 6 | 180 |
| Add new families to the group | 9 × 1 | 90 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,190 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No SignUpGenius Silver plan or API key needed
The month is our example: 3 sign-ups built from a message, one copied from last year, a weekly open-slots email, 6 shift swaps, 8 new families. SignUpGenius publishes no typical account size, only totals such as 40 million sign-ups created. Silver, the cheapest plan with API reads, is $11.99 a month on its own. Dollars at the $29 pack rate.
SignUpGenius MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| chrischall/signupgenius-mcp | 19 tools (15 read, 4 write): sign-up lists, reports with a Pro key, public slot reads, RSVP, claim or release a slot, add a group member. MIT, last commit 19 Oct 2026. | Your password in a .env file, no SSO or 2FA. Cannot build, copy or publish a sign-up, edit slots or email the group. |
| Zapier, also as Zapier MCP | Triggers on a filled slot, a new event or a new group member; adds, finds and deletes group members. | Nothing for sign-ups, slots or messages. |
| SignUpGenius API | 11 read endpoints and one group-member write, 500 to 5,000 calls a day by plan. | Code you write and host, on Silver or above. |
| Participant bots on GitHub | Selenium scripts that grab a slot the moment it opens. | The volunteer side, not the organizer's. |
For a nightly export of who signed up, the official API on a Silver plan is the plain choice, and the route SignUpGenius backs. For a parent who wants an agent to grab a slot, the GitHub server does that. For building sign-ups, swapping people between shifts and nudging the group, nothing else reaches them today; Cotlet does that work in your organizer account.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet, a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the SignUpGenius tools go to contact@cotlet.dev.
SignUpGenius API and MCP: questions
Can I use the SignUpGenius API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Create a free account at https://cotlet.dev, open SignUpGenius under Integrations in the console and log in to SignUpGenius in its Cloud Browser. The trial starts when you sign up, no card asked.
How do I connect SignUpGenius to ChatGPT or Claude?
Sign up at cotlet.dev, log in to SignUpGenius once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your SignUpGenius account through Cotlet, in their phone apps too.
What can ChatGPT do in SignUpGenius?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in SignUpGenius: create sign-ups with an AI agent; weekly report of open slots; remind people to fill open slots. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need a Premium plan?
No. Cotlet works in your own organizer account and does not use the Premium API key, which SignUpGenius limits to paid plans (Silver gets a handful of calls a day, Gold and Platinum up to 5,000). Features your plan lacks stay unavailable, as in the web app.
Does SignUpGenius have webhooks?
No. The API sends no events. Zapier polls for a filled slot, a new event or a new group member. For an agent, a schedule works better: a weekly list_signups and get_signup pass finds the gaps.
Can the agent sign up for someone else's sign-up as a volunteer?
No. The tools work on sign-ups you created as the organizer. add_participant puts a person on your own sheet, after your OK.
Does it send text messages?
No, email only. SignUpGenius texts need a paid plan and reach only members who opted in.
Is the MCP server different from the REST API?
Only the door differs. Both carry the same 15 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with SignUpGenius?
No. Cotlet is independent and not affiliated with SignUpGenius, Inc. or Lumaverse Technologies.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.