Create a free wedding website with 600+ templates, a zero-fee cash registry, smart RSVP, guest list tools, and a matching mobile app. Join millions of couples planning with Joy.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.withjoy.com
34tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.withjoy.com/mcp
Skill page: https://www.mcpbundles.com/skills/withjoy-mcp-5f90b0925c
Explore capabilities (34)
read 11
write 14
Showing 25 of 34
Showing 25 of 34 tools from the public preview. Connect the server to inspect the full live tool list.
Apply3
Get3
Read3
Add2
Remove2
Set2
Update2
Other capabilities8
Find your weddings & events
read
find_event
Lists every wedding — and any other special occasion (birthday, anniversary, etc.) — the signed-in Joy account can manage (as owner or admin), each with its hosts, title, date, location, and website link. When the user refers to one of their events, do NOT immediately pick the closest match and act on it — an exact-looking name match is NOT permission to proceed. First scan the WHOLE list for EVERY plausible candidate — by host/couple names, title, or website handle — and treat close name varian
Description may be truncated on the public preview.
Find your weddings & events — Lists every wedding — and any other special occasion (birthday, anniversary, etc.) — the signed-in Joy account can manage (as owner or admin), each with its hosts, title, date, location, and website link. When the user refers to one of their events, do NOT immediately pick the closest match and act on it — an exact-looking name match is NOT permission to proceed. First scan the WHOLE list for EVERY plausible candidate — by host/couple names, title, or website handle — and treat close name varian
Create or modify a wedding or event — Create a new Joy event, or modify an existing one — a wedding or another occasion (birthday, anniversary, baby shower, engagement party, reunion…). Omit eventWebsite to CREATE; pass the event's website link to MODIFY. When creating, try to capture as complete a picture as the user readily offers — host name(s), date, general location, venue, a title — but conversationally. If the user offers only a name or two, ask once — warmly and briefly — whether they have a date, location, or venue in mind
Look up the schedule — Fetch the couple’s schedule — the ceremony, reception, and surrounding events with their times, locations, dress code, and WHO CAN SEE each one. Identify it by its website link (or the handle at the end of it). This is the admin view: read with the owner’s Joy sign-in, so it returns a site they own or co-host, and it shows every item — including ones hidden from some or all guests — with each item’s audience. To change an item (including who can see it) use update_schedule_item.
Look up the guest list — Fetch the guest list, identified by its website link — guest names, households, email, labels, phone, and mailing address. Guests belong to households: when you present the list, GROUP guests by household (using each guest’s household) rather than as one flat run. An unnamed placeholder guest is shown as "{head}’s guest" (e.g. "Marcel Bichon’s guest") — a household can hold several — and you can give one a name with apply_guest_list. Unlike the public schedule, this is private data: the server r
See the RSVPs — Summarize the RSVPs. By default returns AGGREGATE only — how many guests are attending, declined, or haven't replied, who still needs a nudge, and the answer breakdown for each RSVP question (meal choices, hotel, etc.). Individual guests’ answers (with their email, the follow-up identity key) are returned ONLY when you scope the request: pass `question` (optionally with `answer`) for who answered a given question a given way — e.g. who chose the fish, or who hasn't replied to it — pass `guest` f
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Create a free wedding website with 600+ templates, a zero-fee cash registry, smart RSVP, guest list tools, and a matching mobile app. Join millions of couples planning with Joy.
How do I connect Joy to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Joy provide?
Operate this server?
Request removal if you do not want Joy listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Joy?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
Change the guest list — Change the GUEST LIST in one call — a batch across any of: ADD guests, UPDATE a guest’s details (fix a name or email, or NAME an unnamed placeholder guest), TAG guests (tables/labels), RELABEL a whole group (retag everyone from one label to another), and REMOVE guests. Every field is OPTIONAL — include only what you’re changing; several changes apply together. One ordering rule: update/tag/remove act on the guests ALREADY on the list, not on ones you ADD in the same call — so to add a guest AND
Record a guest's RSVP — Record a guest's RSVP — attending or not attending. This writes the RSVP the host sees on their dashboard, as if the guest replied, so use it when a guest tells the host directly. Identify the guest by name or email; if more than one guest shares that name, use their email instead. Note: the RSVP is yes/no — there is no "maybe", and a reply cannot be cleared once set.
Record a guest's answer to an RSVP question — Record one guest's answer to a specific RSVP question — a meal choice, a hotel/transport question, a free-text note, etc. Get the exact question wording and its choices from get_rsvp_summary. Identify the guest by name or email; if more than one guest shares that name, use their email instead. Writes the answer the host sees on their RSVP dashboard, as if the guest replied. For attendance (attending / not attending) use set_guest_rsvp instead. An answer overwrites any previous one and cannot be
Add an item to the schedule — Add an event to the schedule — a welcome dinner, the ceremony, an after-party, etc. Give it a name and start time; end time, location, description, and dress code are optional. Times are the local time — its timezone is used automatically. Writes to the schedule the host and their guests see.
Remove an item from the schedule — Remove an event from the schedule, identified by name. Deleting a schedule item is destructive and not reversible in one step. This is a TWO-STEP tool: by default (confirm omitted) it does NOT delete — it returns a preview of exactly which item would be removed. Only after the host has approved that specific item, call again with confirm: true to actually delete it.
Update an item on the schedule — Change an existing event on the schedule, identified by name. Provide only the fields to change — name, start/end time, location, description, dress code, or WHO CAN SEE it (everyone / nobody / specific guest groups or people); anything you omit stays as it is. Times are the local time.
See the RSVP form — Show the RSVP questionnaire — every question (including ones turned off), its type, its options, and whether it is required or asked of plus-ones. Use this to see the form before adding or changing questions (so you turn on a built-in question rather than adding a duplicate). Reads only.
Add an RSVP question — Add a question to the RSVP form — a multiple-choice question (with options) or a free-text box. To turn on one of Joy's built-in questions (dietary restrictions, hotel help, etc.), use update_rsvp_question to enable it instead of adding a duplicate — check read_rsvp_form first. Attendance (attending / not) is always present; do not add it.
Change an RSVP question — Change a question on the RSVP form, identified by its current wording — reword it, turn it on or off, make it required or optional, ask plus-ones, add/remove options, or change WHO CAN SEE it (everyone / nobody / specific guest groups or people). Anything you do not set stays as it is. Adding or removing an option changes the LIVE form for every guest — for a meal question, that is what the caterer prepares — so treat option changes as a deliberate decision, not a way to accommodate one guest's
Remove an RSVP question — Remove a question from the RSVP form, by name. Removing a question is destructive — it also drops the answers guests already gave it. This is a TWO-STEP tool: by default (confirm omitted) it does NOT remove anything — it returns a preview of the exact question that would go. Only after the host has approved that specific question, call again with confirm: true. Joy's built-in questions can't be deleted — this turns them off instead. The attendance question can't be removed.
Look up the website design — Look up the website DESIGN by its link — the current theme, font, layout, and colors (plus the page list). This is the couple's current design (what they see and what design edits change), read with the owner’s Joy sign-in, so it only returns one they own. For page CONTENT (text, Q&A, photos, who can see a page) use read_website_content; for site SETTINGS — publishing, the web address or domain, the guest password — use read_website_settings. Call this first to see the current design before edit
Search the website design catalog — FIND candidate themes or fonts for a described vibe — a model-facing search over Joy's large theme/font catalogs (hundreds each), returning candidate NAMES as text. Nothing is shown to the couple. This is step 1 of showing a theme/font gallery: search here for the couple's vibe, pick the 3–6 that fit, then call browse_website_design with `shortlist` set to those names to show them. Matches on style tags and categories, not just names. Read-only.
Show a website design gallery — SHOW the couple a VISUAL GALLERY of the design options you're proposing — themes, fonts, layouts, welcome-page header styles, or color palettes. This is a presentation tool: it renders exactly the set you pass, so the panel matches your advice in chat. For a design request, START with design_guide (it drives this). THEMES and FONTS: pass `shortlist` with the exact names to show (find them first via search_design_catalog — a bare theme/font browse shows nothing). LAYOUTS (3) and HEADER styles are
Apply website design changes — Change the website DESIGN — any of: theme, layout, colors, font, per-role typography (e.g. bigger headings), and the welcome-page header. Every field is OPTIONAL; include only what you’re changing, and you can change several at once (e.g. a theme PLUS a custom button color PLUS bigger headings) — they’re applied together as one coherent look. Use exact theme/font names from browse_website_design. Applies to the couple’s website immediately. For page CONTENT (text, Q&A, photos, wedding party, tra
Look up the website settings — Look up the website’s SETTINGS by its link — whether it’s published or hidden from guests, the web address (handle) and any custom domain, whether a guest password is set and what it protects (the value itself lives in the host’s Joy settings, not here), the guest website language, and each page’s visibility (public / password-protected / guest-list only / hidden). Use this for anything about publishing, privacy, passwords, the web address or domain, the guest language, or showing/hiding pages.
Apply website settings changes — Change the website SETTINGS — any of: the web address (handle), a custom domain, whether the site is published (public to guests) or hidden, whether RSVP shows on the site, what the guest password protects (whether guests must enter it to see the event date or venue), and the guest website language (the language the site renders in for guests). The guest password VALUE itself is set in Joy’s own settings, not here. Every field is OPTIONAL; include only what you’re changing, and you can change se
Preview the website — Render the couple’s current website and show it to them so they can SEE their design edits. After a WHOLE-LOOK design change — or whenever the host asks to see it — call this to show the result (a directed or single-axis edit does not need a preview unless they ask); at most ONCE per response (never twice in the same turn). Optionally target a section with 'page'. Shows the current design whether or not the site is public yet — so this is how to show an UNPUBLISHED site: the public withjoy.com/<
Set a photo on the event's website — Set the main photo on a page of the event's website — the welcome/home page by default, or another page such as story, schedule, or travel. Uses a photo already in the event's library: give its NUMBER (`photo`). Every page ships a sample photo, so the couple is choosing whether to KEEP it or replace it — don't ask them to recall a number. Instead open the picker in the same turn: view_media_library with purpose:"select", showCurrentPagePhoto:"<page>", and maxPhotos:1 — it shows the current page
Manage the event website's photo library — View and organise the event website's photo library — the shared pool of uploaded photos and the albums built from them. Use it to see what photos and albums exist, upload a new photo from a PUBLIC image URL into the pool, permanently remove a photo from the pool, and manage albums: create one, add or remove photos, make it visible to guests or hide it, set how it displays (grid or slideshow), and rename it. Photos upload once into the pool and can be reused across albums and pages. Refer to a p
Show the event website's photo library — Show the couple a VISUAL gallery of the event website's photo library — the pool of uploaded photos as thumbnails, plus their albums (with cover, count, visibility, and display). Use this when they want to SEE their photos or albums. Set `purpose:"select"` to turn it into a PICKER so the couple taps the photos they want (e.g. for a welcome-page header) and posts the numbers back to you — so you never ask them to recall photo numbers. To make changes (upload, organise albums, set privacy) — or to
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 34 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Joy require?
Joy may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.