Chorus
Start a book of voice, video and written messages from a group of people for one person, and hand the organiser one link to forward.
Documentation
Gathering is free, and the people recording need no account. An organiser pays once, at the end, if they order. The prices are at /llms.txt, which is the one place they are written.
The link that needs no connector
The assistant writes the link
An assistant with nothing installed can write the person a link. They tap it once and the start screen opens with the details already filled in. One button and the book exists, with no sign-in, and they get the link to forward. They give their email when they want to read the messages or order the book.
What goes in that link
A title, a person or both
https://choruskeepsake.com/start?title=Kerry%20in%20August&q=What%20was%20the%20best%20day%3F&answer=voice,video,written
title is what the book is called, up to 40 characters. for is who the book is for, when it is for one person or a couple: Mum, Nana Rose, Clare and James. Give title, for or both. q is one question everybody is asked, written again for each question, up to ten. answer says how people may answer: voice, video, written. occasion is one of birthday, wedding, baby, child, memory, or left out; plain words are matched, so occasion=her 80th gives the birthday book. closes is the day collecting stops, written as a date. Allow three weeks before the day if a printed copy is wanted. A link with no title and no for, which says how people answer or carries a question, opens on a book that asks what it is called.
https://choruskeepsake.com/mcp
Protocol 2025-06-18, one POST carrying a JSON-RPC message and one JSON reply. There is no authentication, because nobody needs a Chorus account to start a book. start_book with no email makes the book at once and hands back a handle and a keep_link. The organiser opens keep_link and gives their email when they want the book in their account. Every later call carries the handle. A handle carries 128 bits of randomness and is never shown on a page. Given the organiser's email instead, start_book sends them a six digit code and makes the book in their account on the second call, and find_my_book does the same for the books an account already has.
The connector that signs you in
The same tools, with no code
https://choruskeepsake.com/mcp/account
Add this address and the assistant sends you to choruskeepsake.com once. You sign in the way you sign in to Chorus and press Allow, and from then on the assistant works in your account. start_book makes the book straight away, my_books lists the books you already have, and every tool works only on your own books. In ChatGPT, order gives you the page that orders the printed keepsake. You can switch it off any time in Account on Chorus. For the assistant it is OAuth 2.1 with PKCE and dynamic client registration, found at /.well-known/oauth-authorization-server.
Add Chorus to your assistant
One address, added once
Copy https://choruskeepsake.com/mcp/account and add it where your assistant keeps its connectors.
Claude: open Settings, then Connectors, then Add custom connector.
Grok: open grok.com/connectors and add a custom connector.
Le Chat: open Connectors and add a custom MCP connector.
Perplexity: open Settings, then Connectors, and add a custom connector.
Sign in to Chorus when it asks and press Allow. Then say Start a Chorus book for Mum's 70th and give me the link to send the family.
The action
OpenAPI 3.1, the same nineteen tools
https://choruskeepsake.com/api/openapi.json
Import that to build a ChatGPT action. It describes the same nineteen tools on the same address, and both surfaces run the one piece of code.
The nineteen tools
Seven tools read and twelve write. None of them deletes anything.
start_book starts the book and returns the one link to forward, with no sign-in. Given the organiser's email, it sends a six digit code first and starts the book on the second call. Writes.
get_links gives the collecting link, the link that plays every message, and a short message to paste alongside them. Reads.
add_people names the people the book is waiting on, with an email address where there is one. It sends nothing on its own. Writes.
send_it_out emails the invitation once to everyone with an address, and returns a tap that opens WhatsApp, a text or a mail draft with the message and the link already written. Writes.
chase_the_missing reminds the people who have not recorded, and returns a message naming them for the group chat. One reminder a day, three in all, and none after somebody asks to stop. Writes.
book_status says who is in, who is still out, how many days are left, and the day to chase and the day to close. Reads.
close_collecting stops new messages arriving and returns the final counts. It can be undone. Writes.
reopen_collecting lets messages in again, with a new closing date if there is one. Writes.
order hands the organiser a payment page for the option they chose. Writes.
find_my_book emails a six digit code to the address a book belongs to, and on the second call, with the code, hands back every book on that account. Writes.
my_books takes the place of find_my_book on the connector that signs you in, and lists every book in the account with no code. Reads.
change_the_book changes the closing date, the questions people are asked, which can be about anything, the order they come in, whether they may send voice, video or writing, and whether they are offered to chip in towards the printed book. A song, a photo, a date, a choice, a link and a short voice note that prints as its own code are some of the ways people answer. Writes.
get_style reads how each page looks, part by part: the type, the colours, the margins, the photo, the heading, the words, the name, the codes and the page numbers, with the limits the printer sets. Reads.
set_style changes any part of how each page looks, for every page or for one person, and answers with what it set, what a print rule changed and why, and pictures of the pages as they now print. Writes.
preview_pages gives pictures of the pages, drawn by the same code that makes the printer's file. Reads.
arrange_the_book puts the people in the order you ask for, takes a person's pages out or puts them back, and sets the title and the cover. It moves pages and changes no word on them. Writes.
their_own_link gives the separate link for the person the book is about, and refuses on a memorial, a new baby and an as they grow book. Reads.
read_the_messages gives every message and who left it, with the words where the tier includes them. Reads.
order_status says whether it is paid and, on a printed copy, where the printer is with it. Reads.
send_feedback sends the people who make Chorus a short note when a tool fails or cannot do what was asked. It changes nothing on a book and emails nobody. Writes.
What people ask it
Typed to an assistant
Start a Chorus book for Mum's 70th and give me a link I can send the family. The assistant calls start_book, which makes the book at once and hands back the link to send round.
Add my brothers Dave and Ciarán and my aunt Maura, and send them the link. It calls add_people, then send_it_out.
Who still hasn't recorded for Mum's book? Give them a nudge. It calls book_status, then chase_the_missing.
Read me what everyone said. It calls read_the_messages.
Ask everyone for a song, why they picked it, a photo and a voice note, with the song at the top of each page. It calls change_the_book.
Make the QR code smaller and put it on the right. It calls set_style, then shows the pages it sends back.
Close Mum's book and get me the printed copy. It calls close_collecting, then order.
What a tool will never do
A tool never takes a card or names a price
order returns a Stripe page and stops there. Stripe shows the figure, takes the card and, on a printed copy, takes the postal address.
What Chorus is told
A name, an email, and the messages
Starting a book stores the name the book is for, the organiser's email address so the book belongs to them, and whatever the people taking part record. The conversation itself never reaches Chorus, and neither does anything else the assistant holds. A note sent with send_feedback is kept with any email address or phone number taken out. The full account of what is kept and how to have it removed is on the privacy page.
Who made it
Spremt Labs Limited
Chorus is made by Spremt Labs Limited, a company in Ireland. Write to hello@choruskeepsake.com about anything on this page, including a server that is answering slowly or a tool that gave you something you did not expect.
This page was written on 7 September 2026 and updated on 10 November 2026. Chorus is a product of Spremt Labs Limited.