# Joy API and MCP server

> Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Guests, RSVPs and the registry are managed in the Joy dashboard, and the guest list leaves Joy only as a CSV file you download by hand.

Free wedding website, guest list, RSVP and universal registry app for couples planning a wedding or other event.

## What is the Joy API?

Cotlet's Joy API exposes 15 endpoints for your own Joy account: list events, list guests, get guest, get RSVP summary, list schedule, list registry gifts, list received gifts, add guest, update guest, assign guest tags, update schedule event, add registry gift, send RSVP reminder, send email message and send thank-you note. The list_events endpoint returns Joy events you own or collaborate on, with name, date and website URL. Each endpoint takes simple JSON inputs like event_id, guest_ids or subject and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities)
- **Endpoints:** 15 (7 read, 8 write)
- **Updated:** 2026-10-11

Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Joy with 15 endpoints (7 read, 8 write): your AI agent signs in as you and does the work.

## Does Joy have an official API?

Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Guests, RSVPs and the registry are managed in the Joy dashboard, and the guest list leaves Joy only as a CSV file you download by hand.

| Task | Joy official | Cotlet |
|---|---|---|
| List guests with RSVP answers and tags | Partly: Only as a CSV export from the Guest List | Yes |
| Get attending, declined and pending counts | No | Yes |
| Add or update guests, parties and plus-ones | Partly: Only as a CSV import that adds to the list | Yes |
| Change an RSVP answer for a guest | No | Yes |
| Edit the schedule of events | No | Yes |
| Add registry gifts and see who bought what | No | Yes |
| Send RSVP reminders and email updates | No | Yes |
| Send thank-you notes for gifts | No | Yes |

Sources: [Joy Help: importing and exporting your guest list](https://withjoy.com/help/en/articles/8309207-importing-and-exporting-your-guest-list), [Joy Help: sending email and reminder messages](https://withjoy.com/help/en/articles/8346349-sending-email-and-reminder-messages), [Joy Help: tracking gifts you received](https://withjoy.com/help/en/articles/8328136-how-do-i-see-what-gifts-i-ve-received), [Joy Help: sending thank-you notes](https://withjoy.com/help/en/articles/8328353-sending-thank-you-notes), [Joy Help: seating chart](https://withjoy.com/help/en/articles/16416147-seating-chart)

## For AI agents

```text
Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Guests, RSVPs and the registry are managed in the Joy dashboard, and the guest list leaves Joy only as a CSV file you download by hand.
Cotlet provides a hosted MCP server and REST API for Joy: 15 tools (7 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=joy; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/joy
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_events, list_guests, get_guest, get_rsvp_summary, list_schedule, list_registry_gifts, list_received_gifts, add_guest, update_guest, assign_guest_tags, update_schedule_event, add_registry_gift, send_rsvp_reminder, send_email_message, send_thank_you_note
Confirm      update_schedule_event, send_rsvp_reminder, send_email_message, send_thank_you_note (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/joy-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=joy (Joy is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Joy once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Joy server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Joy in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Joy's terms; Cotlet is not affiliated with Joy.
```

## What can an AI agent do in Joy?

Cotlet is best for couples and planners who keep their Joy guest list, RSVPs and registry up to date through an AI agent without running or fixing a server.

- **Check who has not RSVPed** (runs: weekly): "How many guests are coming, and who still has not replied to the RSVP?" → `list_events`, `get_rsvp_summary`, `list_guests`
- **[Sync the guest list from a spreadsheet](https://cotlet.dev/integrations/joy-api-mcp-server/add-guests-from-spreadsheet)**: "Compare our "Wedding guests" Google Sheet with the Joy guest list: add the new rows as guests with their party and tags, update changed emails and phone numbers, and list anything you are not sure about." → `list_events`, `list_guests`, `add_guest`, `update_guest`, `assign_guest_tags`
- **[Remind guests who have not RSVPed](https://cotlet.dev/integrations/joy-api-mcp-server/send-rsvp-reminders)** (runs: weekly): "Our RSVP deadline is May 15. Tell me how many guests are coming, then email an RSVP reminder to every party that has not answered and list the ones you cannot reach." → `list_events`, `get_rsvp_summary`, `list_guests`, `send_rsvp_reminder`
- **[Get final meal counts for the caterer](https://cotlet.dev/integrations/joy-api-mcp-server/export-meal-choices)**: "RSVPs are closed. Give the caterer the number of each meal for everyone attending the reception, plus a list of dietary notes by guest name, and flag anyone with no meal answer." → `get_rsvp_summary`, `list_guests`, `get_guest`
- **Announce a schedule change**: "Move the welcome dinner to 7 pm and email the guests about the change." → `list_schedule`, `update_schedule_event`, `send_email_message`
- **[Send thank-you notes for gifts](https://cotlet.dev/integrations/joy-api-mcp-server/send-thank-you-notes)**: "Go through every gift in our Joy registry tracker since the wedding, draft a thank-you for each giver that names what they gave, and send them in batches of ten after I read them." → `list_received_gifts`, `send_thank_you_note`

## Can Joy automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Joy connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to check who has not rsvped, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/joy/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/joy/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/joy/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/joy/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Joy.

### list_events

Joy events you own or collaborate on, with name, date and website URL. Access: read. REST: `POST /api/v1/joy/list_events`.

No parameters.

Returns every Joy event your account can open, as owner or collaborator. Use event_id from each item as the event_id parameter of the other endpoints.

Example response:

```json
{
  "events": [
    {
      "event_id": "evt_8KQ2mZ",
      "name": "Maria and Tom",
      "date": "2027-06-12",
      "role": "owner",
      "website": "https://withjoy.com/maria-and-tom"
    }
  ]
}
```

### list_guests

Guest list with party, plus-ones, tags, contact details and RSVP answers per question. Access: read. REST: `POST /api/v1/joy/list_guests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `rsvp` | enum | no | all, attending, declined or no_response. Default: all. |
| `tag` | string | no | Only guests with this guest tag. |
| `search` | string | no | Match on guest name or email. |
| `limit` | integer | no | 1 to 500. Default: 100. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns guests in guest list order with their party, tags and answers to each RSVP question. Filter by RSVP status, tag or name to narrow it down. Pages hold up to 500 guests; pass next_cursor back as cursor.

Example response:

```json
{
  "guests": [
    {
      "guest_id": "g_4d21",
      "first_name": "Ana",
      "last_name": "Lopez",
      "email": "ana@example.com",
      "party": "Lopez",
      "tags": [
        "friends"
      ],
      "rsvp": "attending",
      "answers": {
        "Meal choice": "Vegetarian"
      }
    },
    {
      "guest_id": "g_4d22",
      "first_name": "Luis",
      "last_name": "Lopez",
      "email": null,
      "party": "Lopez",
      "tags": [
        "friends"
      ],
      "rsvp": "attending",
      "answers": {
        "Meal choice": "Fish"
      }
    }
  ],
  "next_cursor": null
}
```

### get_guest

One guest profile: contact details, party, tags, all RSVP answers and email tracking history. Access: read. REST: `POST /api/v1/joy/get_guest`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_id` | string | yes | Guest ID from list_guests. |

Returns one guest with the full set of RSVP answers and which emails were sent to them. Use it before changing an RSVP or contacting the guest.

Example response:

```json
{
  "guest_id": "g_4d21",
  "first_name": "Ana",
  "last_name": "Lopez",
  "email": "ana@example.com",
  "phone": null,
  "party": "Lopez",
  "plus_ones": 0,
  "tags": [
    "friends"
  ],
  "rsvp": "attending",
  "answers": {
    "Meal choice": "Vegetarian",
    "Dietary notes": "No nuts"
  },
  "emails": [
    {
      "subject": "Two weeks left to RSVP",
      "sent_at": "2027-05-29T10:00:00Z",
      "opened": true
    }
  ]
}
```

### get_rsvp_summary

Attending, declined and pending counts, with a breakdown of answers to each RSVP question. Access: read. REST: `POST /api/v1/joy/get_rsvp_summary`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Returns counts of guests who are attending, declined or have not responded, and for each RSVP question how many guests gave each answer. The counts match the Guest List screen.

Example response:

```json
{
  "event_id": "evt_8KQ2mZ",
  "guests_total": 120,
  "attending": 74,
  "declined": 9,
  "no_response": 37,
  "questions": [
    {
      "question": "Meal choice",
      "answers": {
        "Beef": 31,
        "Fish": 24,
        "Vegetarian": 19
      }
    }
  ]
}
```

### list_schedule

Events on your Schedule page with time, time zone, venue, dress code and privacy. Access: read. REST: `POST /api/v1/joy/list_schedule`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Returns the events on your Schedule page in time order. Privacy says whether everyone or only specific guests see an event. Use schedule_item_id with update_schedule_event.

Example response:

```json
{
  "schedule": [
    {
      "schedule_item_id": "sch_41",
      "name": "Welcome dinner",
      "start": "2027-06-11T18:00:00",
      "time_zone": "Europe/Rome",
      "venue": "Osteria del Ponte",
      "dress_code": "Smart casual",
      "privacy": "everyone"
    }
  ]
}
```

### list_registry_gifts

Registry items and cash funds with price, quantity, Our Most Wanted flag and purchased or reserved status. Access: read. REST: `POST /api/v1/joy/list_registry_gifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Returns everything on your registry: gifts from any store and cash funds. Each item shows how many are still wanted and whether any were purchased or reserved.

Example response:

```json
{
  "gifts": [
    {
      "gift_id": "gft_7731",
      "title": "Stand mixer",
      "store": "example-store.com",
      "price": "329.00",
      "quantity": 1,
      "purchased": 1,
      "most_wanted": true
    },
    {
      "gift_id": "gft_7740",
      "title": "Honeymoon fund",
      "type": "cash_fund",
      "raised": "450.00"
    }
  ]
}
```

### list_received_gifts

The gift tracker: who bought each gift, order info, cash fund contributions and whether you sent a thank-you. Access: read. REST: `POST /api/v1/joy/list_received_gifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `since` | date | no | Only gifts received on or after this date. |

Returns what the Track tab of your Registry shows: the guest who bought each physical gift, the quantity and order info, and what each guest put into a cash fund. Each row says whether a thank-you was sent.

Example response:

```json
{
  "gifts": [
    {
      "gift_id": "gft_7731",
      "item": "Stand mixer",
      "from": "Ana Lopez",
      "quantity": 1,
      "received_at": "2027-05-20",
      "thank_you_sent": false
    },
    {
      "gift_id": "gft_7740",
      "item": "Honeymoon fund",
      "from": "Luis Lopez",
      "amount": "100.00",
      "received_at": "2027-05-22",
      "thank_you_sent": true
    }
  ]
}
```

### add_guest

Add a guest to the guest list, optionally into a party with blank plus-ones. Sends nothing. Access: write. REST: `POST /api/v1/joy/add_guest`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `first_name` | string | yes | First name, no symbols. |
| `last_name` | string | no | Last name, no symbols. |
| `email` | string | no | Needed for digital cards and email messages. |
| `phone` | string | no | Mobile number, for text messages with Messaging Plus. |
| `party` | string | no | Party name. Guests with the same party are grouped and can RSVP for each other. |
| `plus_ones` | integer | no | Number of blank plus-ones. Default: 0. |
| `name_on_envelope` | string | no | How the party is addressed on envelopes, e.g. The Porter Family. |
| `tags` | string[] | no | Guest tags to assign. New tags are created. |

Adds one guest to the guest list. Guests with the same party value are grouped and can RSVP for each other. It sends nothing to the guest and is undone by removing the guest, so it runs without asking.

Example response:

```json
{
  "guest_id": "g_4e08",
  "first_name": "Maria",
  "last_name": "Porter",
  "party": "Porter family",
  "name_on_envelope": "The Porter Family",
  "tags": [
    "family"
  ],
  "rsvp": "no_response"
}
```

### update_guest

Change contact details, party or plus-ones, or set or remove an RSVP answer for a guest. Access: write. REST: `POST /api/v1/joy/update_guest`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_id` | string | yes | Guest ID from list_guests. |
| `fields` | object | yes | Any of first_name, last_name, email, phone, party, plus_ones, name_on_envelope, rsvp_answers ({question: answer or null to remove}). |

Changes the fields you pass and leaves the rest. Setting rsvp_answers records the answer as if the guest gave it; null removes an answer. It sends nothing to the guest and one more call reverts it, so it runs without asking.

Example response:

```json
{
  "guest_id": "g_4d22",
  "email": "luis@example.com",
  "rsvp": "attending",
  "answers": {
    "Meal choice": "Fish"
  }
}
```

### assign_guest_tags

Add or remove guest tags on several guests at once. Tags control private events and RSVP questions. Access: write. REST: `POST /api/v1/joy/assign_guest_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_ids` | string[] | yes | Guest IDs from list_guests. |
| `add` | string[] | no | Tags to assign. New tags are created. |
| `remove` | string[] | no | Tags to take off these guests. |

Adds or removes tags on many guests in one call. New tags are created. Tags can limit who sees a private event or an RSVP question, so check them before the next send. It sends nothing and is undone with one call.

Example response:

```json
{
  "updated": 12,
  "added": [
    "family"
  ],
  "removed": []
}
```

### update_schedule_event

Change an event on your Schedule page. Guests see it on your website right away. Access: write, asks the user first. REST: `POST /api/v1/joy/update_schedule_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `schedule_item_id` | string | yes | Schedule item ID from list_schedule. |
| `fields` | object | yes | Any of name, description, start, end, time_zone, venue, dress_code, privacy (everyone or specific_guests). |

Changes the fields you pass on one Schedule event. The new time or venue shows on your public website at once, so guests can see it before any email goes out. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "schedule_item_id": "sch_41",
  "name": "Welcome dinner",
  "start": "2027-06-11T19:00:00",
  "time_zone": "Europe/Rome",
  "privacy": "everyone",
  "status": "updated"
}
```

### add_registry_gift

Add a gift from any store by product URL. Joy fills in the title and price when it can. Access: write. REST: `POST /api/v1/joy/add_registry_gift`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `product_url` | string | yes | Product page on any retailer site. |
| `title` | string | no | Overrides the title Joy reads from the page. |
| `price` | string | no | MSRP price in your registry currency, e.g. 89.00. |
| `quantity` | integer | no | How many you want. Default: 1. |
| `most_wanted` | boolean | no | Mark as Our Most Wanted. Default: false. |
| `note` | string | no | Note to Family and Friends shown with the gift. |

Adds a gift to your registry from a product page. Joy reads the title and price from the page when it can; set them yourself otherwise. Mark it Our Most Wanted to highlight it. It reaches no one directly and one removal undoes it, so it runs without asking.

Example response:

```json
{
  "gift_id": "gft_7752",
  "title": "Cast iron pan",
  "price": "89.00",
  "quantity": 1,
  "most_wanted": false
}
```

### send_rsvp_reminder

RSVP reminder with a link to your RSVP page, by default to every guest who has not responded. Access: write, asks the user first. REST: `POST /api/v1/joy/send_rsvp_reminder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_ids` | string[] | no | Recipients. Default: guests with no response. |
| `delivery` | enum | no | email, text or both. Text needs Messaging Plus. Default: email. |
| `subject` | string | no | Email subject line. |
| `message` | string | no | Message body. Default: the Joy reminder text. |

Sends the Joy RSVP reminder. Without guest_ids it goes to every guest with no response. Guests with no email are skipped and counted in the response. Email is free; text needs Messaging Plus. By default you confirm each call; you can switch that off for this tool.

Example response:

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

### send_email_message

Email update to selected guests or tags, with a button linking to your event website. Access: write, asks the user first. REST: `POST /api/v1/joy/send_email_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_ids` | string[] | no | Recipients by guest ID. |
| `tags` | string[] | no | Recipients by guest tag. Use guest_ids or tags. |
| `subject` | string | yes | Email subject line. |
| `message` | string | yes | Message body. |
| `send_at` | datetime | no | Schedule for later, ISO 8601. Needs Messaging Plus. Default: now. |

Sends a freeform email to the guests you pick by ID or tag, with a button to your event website. Guests without an email address do not get it. Scheduling for later needs Messaging Plus. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "msg_2290",
  "status": "sent",
  "recipients": 74,
  "skipped_missing_email": 1
}
```

### send_thank_you_note

Digital thank-you email to the guest who gave a gift, sent from the gift tracker. Access: write, asks the user first. REST: `POST /api/v1/joy/send_thank_you_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `gift_id` | string | yes | Gift ID from list_received_gifts. |
| `message` | string | yes | Thank-you text. |
| `subject` | string | no | Email subject line. |

Sends one thank-you to the guest who gave the gift, and marks the gift as thanked in the tracker. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "gift_id": "gft_7731",
  "to": "Ana Lopez",
  "status": "sent",
  "thank_you_sent": true
}
```

## How do I connect Joy to Claude Code, Codex or Cursor?

Connecting Joy takes three steps: request access, sign in to Joy once, then add one MCP server or call the REST API with the same key.

### Connect Joy to your agent.

1. **Create an account** Sign up and add Joy in the console. Your API key is there too.

2. **Sign in to Joy once** Open the connect page from the console and sign in to Joy the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Joy tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
How many guests are coming, and who still has not replied to the RSVP?
```

### Call Joy from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/joy/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

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

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

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

## Why use Cotlet for Joy?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Joy yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Joy changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Joy MCP server on GitHub?

Open-source export scripts exist on GitHub. They are usually maintained by one person, log in to Joy with a headless browser, click Export All Guests and only read the guest list. You run and fix them yourself; Cotlet hosts the same kind of access for you, adds writes, and our team keeps it working.

|  | GitHub export script | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, store your Joy login in a config file | Request access, sign in to Joy once, add one MCP server or API key |
| When Joy changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Joy session | Your password in a file on your machine | Only the session, encrypted in an EU vault, revoked in one click |
| When the session expires | The script fails or logs in again with the stored password | Your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your machine or server, on a cron | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Joy changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Joy API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Joy API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Joy account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Joy yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Joy tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Joy in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Joy's terms:** You use your own Joy account and stay responsible for following Joy's terms. Cotlet is independent and not affiliated with Joy. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Joy. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Joy once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Joy session would leave my computer.**

Cotlet keeps your Joy session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

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

**Can my agent post or send messages in Joy without asking me?**

No. Every call to update_schedule_event, send_rsvp_reminder, send_email_message or send_thank_you_note waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_guest, update_guest, assign_guest_tags, add_registry_gift runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Joy API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/joy/{tool} from the HTTP Request node.