Joy MCP Server

Guest list, RSVPs and registry for your Joy wedding.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/joy'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Joy API and MCP server: Let your AI agent chase your Joy RSVPs.

Joy has no public API, no webhooks and no MCP server (checked 24 Oct 2026); withjoy.com/api and /developers answer 404. Cotlet runs 15 Joy tools hosted, over MCP for agents and REST for scripts.

Bring Joy guests, RSVPs and wedding schedules into your planning workflow. Use an AI agent through MCP or call REST from a script or automation tool.

MCP setup REST API guide

What can you automate in Joy?

  • Sync the guest list from your sheet
  • Remind guests who have not RSVPed
  • Count meals for the caterer
  • Move an event and tell the guests
  • Add gifts to the registry
  • Send thank-you notes for gifts

Does Joy have an MCP server or an API?

  • Zapier and n8n have no Joy app. The guest list leaves Joy only as a CSV you export by hand, and the CSV import only adds rows.
  • Joy itself is free. Texts and scheduled sends need Messaging Plus, a one-time purchase per event whose price Joy shows only at checkout.
  • Two open-source exporters on GitHub copy the guest list into a sheet. Neither adds a guest, sends a reminder or reads the gift tracker.
What you needJoy dashboardGitHub exporterCotlet
Guests with every RSVP answerCSV, by handYes, to a sheetYes
Add and update guests from a sheetImport adds onlyNoYes, matched by email
Remind only the pending partiesBy hand, each timeNoYes, after your OK
Thank-you notes for giftsOne gift at a timeNoYes, in batches
Runs with your computer offNoOn your own serverYes, hosted

Checked 24 Oct 2026. Sources: Joy Help: importing and exporting your guest list, Joy Help: sending email and reminder messages, Joy pricing, Joy Help: Messaging Plus, Joy Terms of Use and EULA

How does Cotlet connect to Joy?

  1. Sign in to Joy. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Joy password, and no reminder, update or thank-you reaches a guest until you approve it.

Connect Joy 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.

  1. Turn Joy on for agents. Create a Cotlet account, sign in to Joy in its Cloud Browser and press Enable for agents.
  2. Give your agent the address. Add https://cotlet.dev/mcp/v1 to the MCP server or connector list of your agent.
  3. Let it in. Chat apps open a Cotlet sign-in; editors, n8n and scripts send an API key made in the console.

Joy shares https://cotlet.dev/mcp/v1 with every other app you enable. Turned Joy on after you connected? Refresh the connector and the Joy tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-joy \
  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-joy": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-joy]
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: joy_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: joy_write

How to use the Joy REST API

Create your Cotlet API key

Create a Cotlet API key with access to Joy and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Sign in to Joy in its Cotlet Cloud Browser and enable the app for agents. Use an event owner or collaborator login.

Make your first Joy API request

REST:

curl https://cotlet.dev/api/v1/joy/events \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read event IDs before guest records

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": "joy",
  "tool": "list_events",
  "result": {
    "events": [
      {
        "event_id": "evt_8KQ2mZ",
        "name": "Maria and Tom",
        "date": "2027-06-12",
        "role": "owner",
        "website": "https://withjoy.com/maria-and-tom"
      }
    ]
  }
}

Read result.events and use an event_id in guest, schedule and gift operations. Event listing has no pagination input.

Guest lists default to 100 records per page, with a maximum of 500. Pass their returned next_cursor as cursor until null, keeping event and filters unchanged.

Compare RSVP answers, meal choices and quantities as well as guest IDs when refreshing planning reports.

Joy workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestRead event guests and RSVP summaries into a wedding meal-count report, retaining party quantities.
MakeHTTP > Make a requestRead the event schedule into a briefing for your coordinator and wedding party.
Python or Node.jsREST APICompare received gifts and registry gifts to prepare a thank-you review queue without sending notes.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Joy; 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.

Joy API endpoints and MCP tools

Guest list and RSVPs

Up to 500 guests a page. Tags decide who sees private events and RSVP questions. No tool deletes a guest, since that drops their email history.

  • List events (list_events, read): Joy events you own or collaborate on, with name, date and website URL.
  • List guests (list_guests, read): Guest list with party, plus-ones, tags, contact details and RSVP answers per question.
  • Get guest (get_guest, read): One guest profile: contact details, party, tags, all RSVP answers and email tracking history.
  • Get RSVP summary (get_rsvp_summary, read): Attending, declined and pending counts, with a breakdown of answers to each RSVP question.
  • Add guest (add_guest, write): Add a guest to the guest list, optionally into a party with blank plus-ones. Sends nothing.
  • Update guest (update_guest, write): Change contact details, party or plus-ones, or set or remove an RSVP answer for a guest.
  • Assign guest tags (assign_guest_tags, write): Add or remove guest tags on several guests at once. Tags control private events and RSVP questions.

Schedule page

A change shows on your public wedding website at once, so it asks first.

  • List schedule (list_schedule, read): Events on your Schedule page with time, time zone, venue, dress code and privacy.
  • Update schedule event (update_schedule_event, write, asks first): Change an event on your Schedule page. Guests see it on your website right away.

Registry and gift tracker

Gifts bought straight on an outside store show only after the guest confirms the purchase on Joy.

  • List registry gifts (list_registry_gifts, read): Registry items and cash funds with price, quantity, Our Most Wanted flag and purchased or reserved status.
  • List received gifts (list_received_gifts, read): The gift tracker: who bought each gift, order info, cash fund contributions and whether you sent a thank-you.
  • Add registry gift (add_registry_gift, write): Add a gift from any store by product URL. Joy fills in the title and price when it can.
  • Send thank-you note (send_thank_you_note, write, asks first): Digital thank-you email to the guest who gave a gift, sent from the gift tracker.

Guest messages

Email is free. Text and later send times need Messaging Plus, and Joy texts only US and Canadian numbers.

  • Send RSVP reminder (send_rsvp_reminder, write, asks first): RSVP reminder with a link to your RSVP page, by default to every guest who has not responded.
  • Send email message (send_email_message, write, asks first): Email update to selected guests or tags, with a button linking to your event website.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/joy-api-mcp-server#tools

Who can see my Joy session, and how do I revoke it?

  • What we store. Your signed-in Joy browser profile, AES-256-GCM, in Finland. Never the password.
  • What your agent gets. The 15 Joy tools, nothing else. No cookie, no login.
  • What the session sees. Every event your account owns or edits: guests, addresses, answers, gifts.
  • What no tool touches. Cash fund payouts, store orders, hotel bookings, purchases, deleting guests.
  • If Joy signs you out. You get an email with a sign-in link. We never sign in for you.
  • How to cut access. Disable Joy for agents, reset the browser or delete the API key.

Graded A+ by Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). No SOC 2 report or outside pentest yet.

Is it against Joy's terms? Account safety

You agree not to do, or authorize or permit any third party to do, any of the following: ... use any data mining, robots or similar data gathering or extraction methods

Joy Terms of Use and EULA, License Limitations, 18 Mar 2026

The same terms ask you not to log in "through unauthorized third-party applications or clients" and let Joy close an account without notice. You sign in on withjoy.com yourself and Cotlet never sees the password, but Joy could still count an agent as a robot. The GitHub exporters break the same rule. We found no public case of a Joy account closed for automation (checked 24 Oct 2026).

How we keep your account looking like you:

  • Your own Joy account, signed in by you
  • One Cloud Browser with its own IP and cookies, not a new device each call
  • Reminders, emails, thank-yous and schedule changes wait for your OK
  • No tool deletes a guest, gift or event
  • If Joy objects, we pause the Joy tools for everyone within 24 h

Joy may block messages and close an account for spam. Message only your own guests, and Messaging Plus caps texts at 3,000 per event.

What happens when Joy changes?

  • 12 h between tests of the Joy guest, RSVP and registry tools
  • 24 h between tests of messages a guest would get
  • $0 for a call to a Joy tool paused for a fix

Joy builds its guest list export in the browser, so a redesign of the Guest List page breaks home-made exporters. With Cotlet the repair is ours. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Counts the pending. Attending, declined and no reply, before any send.
  2. Groups them by party. One reminder per household, guests without email set aside.
  3. Waits for your OK. Subject and text show up in your Cotlet console.
  4. Reports back. Who got it, who was skipped, who to call.
ActionUndo
Send a reminder, email or thank-youNo, the email is out
Change a schedule eventChange it back; guests may have seen it
Update a guest or tagsYes, one more call
Add a guestRemove them in Joy by hand
Add a registry giftRemove it in Joy by hand

4 of 15 tools ask first: the three that email guests and the one that changes your public schedule. Guest edits, tags and registry adds reach no one, so they run at once. Turn the wait off per tool for a weekly run.

An RSVP answer set by update_guest counts as if the guest gave it. The sheet sync leaves answers alone.

MCP call:

{
  "name": "send_rsvp_reminder",
  "arguments": {
    "event_id": "evt_8KQ2mZ",
    "delivery": "email",
    "subject": "Two weeks left to RSVP"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/joy/events/evt_8KQ2mZ/rsvp-reminders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"delivery":"email","subject":"Two weeks left to RSVP"}'

Tool output:

{
  "event_id": "evt_8KQ2mZ",
  "status": "sent",
  "delivery": "email",
  "recipients": 35,
  "skipped_missing_email": 2,
  "rsvp_url": "https://withjoy.com/maria-and-tom/rsvp"
}

A script or cron job calls the same tools over REST at /api/v1/joy, with the same key and price. A text send on an event without Messaging Plus fails, and a failed call costs nothing. The tools table lists the REST path of each tool.

How much does the Joy MCP server cost?

About $12 a month for a 117-guest wedding in the month before the RSVP deadline, 2,130 credits. Joy itself stays free.

JobCallsCredits
Count RSVPs and remind pending guests, weekly3 × 4120
Sync the guest sheet into Joy, weekly7 × 4280
Meal counts for the caterer5 × 2100
Add gifts to the registry5 × 2100
Move a schedule event and email guests3 × 130
Cloud Browser, 30 days1,500
Total2,130
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • A reminder to 21 parties is one call, not 21

117 guests is the US average in The Knot 2026 Real Weddings Study; the calls per job are our example. The browser is most of the bill, so switch it off after the thank-yous. Dollars at the $29 pack rate.

Joy MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
jcwearn/withjoy-exporterDocker cron that signs in with headless Chromium, clicks Export All Guests and fills a Google Sheet daily.Read only, your Joy password in an env file, no license, 0 stars.
AriaFallah/withjoy-guestlist-exporterConsole script that scrolls the guest table and saves every column to CSV.Run by hand in your open tab, read only, last commit 7 Feb 2025.
Text My WeddingTexts households from a Joy CSV, with RSVP links and reminders; $19 to $237 per wedding.A file import: the two lists do not sync.
Joy Messaging PlusJoy's own texts, reminders and scheduled sends, one purchase per event.Price shown only at checkout; no repeating reminder, no agent access.

No one publishes a Joy MCP server on GitHub. An exporter is enough if a nightly copy of the guest list is all you want. Texting tools work from a file you upload again after each change. Cotlet lets an agent read and write in Joy itself, so the list, reminders and thank-yous stay in one place.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Behind Cotlet is Take Group sp. z o.o., a software company in Poland, EU (VAT PL6342984273), in business since 2019. Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) founded it. Questions about the Joy tools go to contact@cotlet.dev.

Joy API and MCP: questions

Can I use the Joy 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?

Sign up free at https://cotlet.dev, pick Joy under Integrations in the console and sign in to Joy in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect Joy to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Joy 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 Joy account through Cotlet, in their phone apps too.

What can ChatGPT do in Joy?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Joy: check who has not RSVPed; sync the guest list from a spreadsheet; remind guests who have not RSVPed. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need Messaging Plus?

Only for text messages and scheduled sends. Email reminders and email messages sent now work without it, as in the Joy dashboard (Joy Help, checked 11 Oct 2026).

Do collaborators on my event work too?

Cotlet acts as the Joy account you sign in with, so it can do what that account can do in the dashboard. Joy shows events you own or collaborate on.

Does Joy have webhooks?

No. Joy sends no event when a guest RSVPs or buys a gift. Run your agent on a schedule instead, for example get_rsvp_summary every Monday until the deadline.

Will it see gifts bought on Amazon?

Only those Joy tracks. A gift bought straight on a public Amazon or Crate & Barrel registry shows in the gift tracker only after the guest confirms the purchase on Joy, so list_received_gifts cannot see it before that.

What happens after the wedding?

The tools keep working while your Joy event exists, which helps with thank-yous. Messaging Plus ends 90 days after the event. When you are done, disable Joy for agents or reset the browser, and the daily browser credits stop.

Is the MCP server different from the REST API?

Only the way in 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 Joy?

No. Cotlet is independent and not affiliated with Joy Life, Inc.


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.