zola-mcp
An MCP server that connects Claude to your Zola wedding-planning account, exposing 77 tools across 12 areas for reading and updating your own wedding data.
Vendors — list booked vendors, search by name/category, book, update, or unbook a vendor
Budget — view budget summary/items and update actual costs or notes
Guests — list households (compact or full), add guest groups with plus-ones/addresses/invitations, update addresses, remove households (server-gated)
Seating — list seating charts, view tables/seats/occupants, list unseated guests, assign seats
Inquiries — list vendor inquiries, read full conversations, mark as read
Events & RSVPs — list events, track RSVPs, update events (gated), bulk or single invite/uninvite guests, view gift tracker, view registry purchase state
Registry & gifts — browse Zola products, add/update/remove registry items, reconcile registry against gift tracker
Wedding website pages & settings — list/reorder pages, show/hide pages, update page metadata and top-level wedding settings (gated)
Website content — manage FAQs, home story sections, things-to-do POIs, and travel items
Theme — view current theme and customizations, browse themes, switch theme, update colors/fonts
Invitations & save-the-dates — list/get/validate card projects, browse catalog and suites, favorite suites, create projects, swap variations, set addressing guests, preview templates and QR codes, place QR codes
Discovery & health — health check, planning dashboard, marketplace storefront search/details, favorite vendors
Read-only tools run automatically; writes either prompt the client or are server-gated with a preview + confirm token.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zola-mcp Who hasn't RSVP'd yet?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zola MCP
A Model Context Protocol server that connects Claude to Zola, giving you natural-language access to your wedding vendors, budget, guest list, seating chart, events, registry, inquiries, and more.
AI-developed project. This codebase was entirely built and is actively maintained by Claude Code. No human has audited the implementation. Review all code and tool permissions before use.
What you can do
Ask Claude things like:
"How's wedding planning going?"
"Find a photographer in Charlotte, NC"
"Update the venue cost to $25,000"
"Who hasn't RSVP'd yet?"
"Seat Pat at Table 1"
"Any new vendor messages?"
"Add my cousin Mike to the guest list"
"Show me the gift tracker"
Related MCP server: honeybook-mcp
Requirements
Node.js 22 or later
A Zola account
For the no-env-var path: the ContextMint Bridge Chrome extension (Safari is not available yet — use Chrome for now)
Acknowledgement of Terms
By using this MCP server, you acknowledge and agree to the following:
1. This server accesses your own Zola account. Auth happens via your own credentials. It does not — and cannot — access anyone else's wedding website, registry, or guest list.
2. Zola's Terms of Use govern your use of this server, just as they govern your direct use of zola.com. The clauses most relevant here:
[You may not use] any hardware or software intended to surreptitiously intercept or otherwise obtain any information… including but not limited to the use of any "scraping" or other data mining techniques, robots or similar data gathering and extraction tools.
And, critically, on agent-acting-as-you: "You are responsible for maintaining the confidentiality of your account and password… You accept full responsibility for all activities that occur under your account and password, even if such actions are undertaken by your Authorized Agent or other third party."
You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server. Zola's ToU is explicit: this MCP acting as your Authorized Agent counts as you.
3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Zola, Inc. It is a personal automation tool for one couple to manage their own wedding website, registry, vendor research, and guest list. Do not use it to bulk-extract Zola's vendor directory, scrape registries, or compete with Zola.
4. Stability is not guaranteed. This server may call internal Zola endpoints that change without notice. It may break.
5. You accept full responsibility for any consequences of using this server in connection with your Zola account — rate limiting, account warnings, suspension, or any enforcement action. Per Zola's ToU, anything this MCP does under your account is your action — review guest list edits, registry changes, and inquiries before confirming. If Zola objects to your use, stop using this server.
This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede Zola's actual ToU.
Installation
Option A — MCPB (recommended)
Download the latest .mcpb bundle from Releases and install:
claude mcp add-from-mcpb zola-mcp-x.y.z.mcpbYou'll be prompted for your ZOLA_REFRESH_TOKEN (see Getting your refresh token below).
Option B — npm
npx -y zola-mcpAdd to your Claude config (.mcp.json or Claude Desktop config):
{
"mcpServers": {
"zola": {
"command": "npx",
"args": ["-y", "zola-mcp"],
"env": {
"ZOLA_REFRESH_TOKEN": "your-refresh-token-jwt"
}
}
}
}Option C — from source
git clone https://github.com/chrischall/zola-mcp.git
cd zola-mcp
npm install
npm run buildAdd to Claude Desktop config:
Mac:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"zola": {
"command": "node",
"args": ["/absolute/path/to/zola-mcp/dist/bundle.js"],
"env": {
"ZOLA_REFRESH_TOKEN": "your-refresh-token-jwt"
}
}
}
}Getting your refresh token
You have two options. Both produce the same usr cookie value — a ~1-year JWT that doubles as the refresh token.
Option A — ContextMint Bridge (recommended)
Install ContextMint Bridge — Chrome: download the chrome zip from the latest release, unzip it, and load it unpacked at
chrome://extensions(Developer mode on). Safari is not available yet (it will ship inside the ContextMint app, which has no public download), so use Chrome for now.ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (fetchproxy#extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the
.sha256file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).Sign in at zola.com/account/login in that browser.
Leave
ZOLA_REFRESH_TOKENunset in your Claude config.
On the first tool call, the MCP asks the extension for the HttpOnly usr cookie via chrome.cookies.get, then operates direct-to-API from Node — the bridge is never in the hot path.
That cookie is the ~1-year refresh token, so it is cached at $MCP_DATA_DIR/.zola-mcp/refresh-token.json (falling back to $HOME, mode 0600). Later starts read it from there and need no browser at all, which is what makes the server usable on a remote host where none exists. If the API ever rejects the cached token — you signed out, or it aged past its year — it is discarded automatically and the extension is asked again. To re-auth, just sign back in to zola.com. Set ZOLA_TOKEN_CACHE=false to keep nothing on disk and ask the browser every time.
You can opt out of this fallback with ZOLA_DISABLE_FETCHPROXY=1 (e.g. in headless / CI environments where no extension is available).
Option B — manual (DevTools)
Sign in at zola.com/account/login in any browser.
Open DevTools → Application → Cookies →
https://www.zola.com.Copy the value of the
usrcookie.Paste it into
.envasZOLA_REFRESH_TOKEN=<value>(or into your Claude configenvblock).
Restart Claude Desktop
Quit completely (Cmd+Q on Mac) and relaunch.
Verify
Ask Claude: "How's wedding planning going?" — it should show your wedding dashboard.
Credentials
Env var | Required | Notes |
| Conditional | Refresh token JWT (~1 year lifetime). When unset, the MCP falls back to the ContextMint Bridge browser extension to read the |
| No | Set to |
| No | Set to |
| No | Absolute path for the cache file. Defaults to |
| No | Auto-resolved from API on first use |
| No | Auto-resolved from API on first use |
| No | Default |
| No | Default |
| No | Default |
| No | Signing key for confirm tokens (default: random per process). Set it only if tokens must survive a server restart. |
Available tools
77 tools across 12 areas. The Permission column says what stands between a call and a change:
Auto — read-only; runs without asking.
Host prompt — a write. Clients that prompt before non-read-only tools (Claude Code, Claude Desktop) ask you first; the server itself does not, so on a client with no prompt (claude.ai) it runs on the first call.
Server gate — a write that cannot be undone or that changes what guests see, so the server confirms it itself on every client.
The server-gated writes are remove_guest, update_event, update_wedding_settings, remove_faq, remove_home_section, remove_poi, remove_travel_item, remove_registry_item, set_event_guests and remove_event_invitation (set_event_guests only when it uninvites anyone). Each first shows a preview naming the household, event, item or page content and exactly what changes (for a slug change, the old and new website URL; a registry item on a private or passcode-gated registry, or outside the default collection, is shown by id because only the public page names it), then proceeds only once you approve — see MCP_CONFIRM_MODE above.
Vendors
Tool | What it does | Permission |
| List all booked vendors | Auto |
| Search vendors by name/category | Auto |
| Book a new vendor | Host prompt |
| Update vendor details | Host prompt |
| Unbook a vendor | Host prompt |
Budget
Tool | What it does | Permission |
| Budget summary with all items | Auto |
| Update cost or note | Host prompt |
Guests
Tool | What it does | Permission |
| List all guest groups with stats — names, tier and RSVP state by default; | Auto |
| Add a guest group | Host prompt |
| Update mailing address | Host prompt |
| Remove a guest group (with its RSVPs and seats) | Server gate |
Seating
Tool | What it does | Permission |
| List seating charts | Auto |
| Chart with tables/seats/occupants | Auto |
| Guests not yet seated | Auto |
| Assign guest to a seat | Host prompt |
Inquiries
Tool | What it does | Permission |
| All vendor inquiries with status | Auto |
| Full conversation messages | Auto |
| Mark as read | Host prompt |
Events & RSVPs
Tool | What it does | Permission |
| All events with RSVP counts | Auto |
| RSVP tracking per event | Auto |
| Gifts received, thank-you status | Auto |
| Registry items with per-item purchase state ( | Auto |
| Update event details | Server gate |
| Set which guest groups are invited to an event (bulk) | Server gate |
| Invite a single guest or guest group to an event (additive — does not affect other events) | Host prompt |
| Remove an event invitation for a single guest or guest group | Server gate |
Registry & Gifts
Tool | What it does | Permission |
| Browse Zola products in a category, scoped to your registry | Auto |
| Add a product (by SKU) to the registry | Host prompt |
| Update an existing registry item — all fields must be supplied (it's a full replace) | Host prompt |
| Remove an item from the registry that guests shop from | Server gate |
| Joins the registry against the gift tracker: | Auto |
Wedding website — pages & settings
Tool | What it does | Permission |
| List all wedding-website pages with their IDs, types, display order, visibility, and theme info | Auto |
| Show or hide a page on the wedding website (e.g., hide the RSVP page until invites go out) | Host prompt |
| Reorder pages in the website navigation | Host prompt |
| Update page-level metadata (title, intro copy, nav title, visibility, layout customization) | Host prompt |
| Get top-level wedding settings: title, URL slug, partner names, date, city, hashtag, guest count, search visibility | Auto |
| Update top-level wedding settings | Server gate |
Wedding website — content (FAQs, home, things to do, travel)
Tool | What it does | Permission |
| List all FAQs on the wedding website | Auto |
| Add a new FAQ (question + answer) to the website FAQ page | Host prompt |
| Update an existing FAQ — all three fields (question, answer, display_order) must be supplied | Host prompt |
| Remove an FAQ from the public website | Server gate |
| List the story sections on the website home page | Auto |
| Add a story section to the home page (title + subtitle + description block) | Host prompt |
| Update a home page story section — all fields must be supplied | Host prompt |
| Remove a story section from the public home page | Server gate |
| List points-of-interest on the "Things to Do" page | Auto |
| Add a point-of-interest to the Things-to-Do page (restaurant, attraction, etc.) | Host prompt |
| Update a point-of-interest | Host prompt |
| Remove a point-of-interest from the public Things-to-Do page | Server gate |
| List hotels, flights, and transportation on the website Travel page | Auto |
| Add a travel item (hotel, flight, train, car, bus) to the Travel page | Host prompt |
| Update a travel item | Host prompt |
| Remove a travel item from the public Travel page | Server gate |
Wedding website — theme
Tool | What it does | Permission |
| Get the currently-selected website theme: key, name, swatch color, layout type | Auto |
| Get current website colors, font settings, and available font/color options | Auto |
| Browse the catalog of available wedding-website themes | Auto |
| Switch the wedding website to a different theme template | Host prompt |
| Update website colors and fonts | Host prompt |
Invitations & save-the-dates
Tool | What it does | Permission |
| List your invitation / save-the-date / shower-invite "card" projects (paper or digital) | Auto |
| Get full details for one invitation project including all customizations (invitation, envelope, RSVP card, details card), paper/color options, and per-customization pages | Auto |
| Validate an invitation project — reports any text-fit, image, or guest-addressing errors per customization | Auto |
| List the guest groups assigned to an invitation project, including per-group font-size overrides for printed addressing | Auto |
| Get details for an invitation design "suite" (the family of matching invitation + RSVP + details cards), including paper types, sizes, and price range | Auto |
| Search the invitation design catalog | Auto |
| List invitation design suites you have favorited (hearted) | Auto |
| Get the RSVP page settings on the wedding website (title, intro copy, visibility, customization) | Auto |
| Create a new invitation project from a design suite and a lead variation (specific size/paper) | Host prompt |
| Swap one or more customizations on a project to different variations (paper type, color or size) | Host prompt |
| Enable / disable guest groups for an invitation project and optionally override font sizes for printed names and addresses | Host prompt |
| Render an invitation template preview with text substituted in | Auto |
| Generate a QR-code PNG for an invitation | Auto |
| Place (or update) a QR code on a specific page of an invitation project | Host prompt |
Discovery & health
Tool | What it does | Permission |
| Verify the credential and Zola reachability; says which hop failed | Auto |
| Planning dashboard overview | Auto |
| Search marketplace by category/location | Auto |
| Full vendor storefront details | Auto |
| Favorited vendors | Auto |
Upgrading
next release
preview_qrcode now hands the image back through the shared delivery ladder. A normal QR preview is unchanged: one image content block, PNG. What changed are the edge cases:
An image type is always a bare media type (
image/png, neverimage/png;charset=UTF-8), which a host's image renderer would reject.A non-image type that Zola might return comes back as an embedded
resourceblock locally (it was mislabelled as animageblock), and as a download link on a hosted install.An image over 10 MiB is never inlined. On a hosted install it comes back as one text block of JSON,
{ via: "link", fileName, mimeType, sizeBytes, url, expiresAt, note }, whereurlis a signed link that expires atexpiresAt. With no blob store the tool fails with atoo_largeerror.
Troubleshooting
"Zola auth: set ZOLA_REFRESH_TOKEN, or install the ContextMint Bridge extension…" — either set ZOLA_REFRESH_TOKEN in your config or install the ContextMint Bridge extension and sign into zola.com.
"Zola session refresh failed" — your refresh token has expired (~1 year) or been revoked. Either capture a new usr cookie (DevTools) or sign back into zola.com with the ContextMint Bridge extension installed.
403 from mobile API — the x-zola-session-id header may be missing. Update to the latest version.
Tools not appearing in Claude — go to Claude Desktop → Settings → Developer to see connected servers. Make sure you fully quit and relaunched after editing the config.
Security
The refresh token lives only in your local
.envor config file (when set) or in the user's browser cookie store (fetchproxy path)It is passed as an environment variable and never logged
The server authenticates with Zola's mobile API using the same flow as the iOS app
Account and registry IDs are auto-resolved from the API (no manual configuration needed)
Development
npm test # run the test suite (vitest)
npm run build # compile TypeScript → dist/Project structure
src/
client.ts Zola mobile API client (auth, token refresh, context)
index.ts MCP server entry point
tools/
index.ts TOOL_REGISTRARS — every tool module the server registers
vendors.ts list, search, add, update, remove vendors
budget.ts get budget, update budget items
guests.ts list, add, update, remove guests
seating.ts seating charts, seat assignment
inquiries.ts vendor inquiry conversations
events.ts events, RSVPs, gift tracker, registry
event-invitations.ts which guests are invited to which events
registry-items.ts registry item add / update / remove
reconcile-registry.ts registry vs gift-tracker reconciliation
website.ts website pages and wedding settings
website-content.ts FAQs, home sections, things to do, travel
website-theme.ts website theme and customizations
invitations.ts invitation / save-the-date card projects
discover.ts dashboard, storefront search, favorites
healthcheck.ts zola_healthcheck
tests/ one *.test.ts per module, plus manifest/docs/annotation sync testsAuth flow
All tools use the Zola mobile API (mobile-api.zola.com) with Bearer JWT auth:
POST /v3/sessions/refreshwith refresh token JWT → returns 30-min session tokenAll API calls use
Authorization: Bearer <session_token>+x-zola-session-idheaderOn 401, auto-refreshes and retries once
Session tokens are cached for their lifetime (30 min)
Building the MCPB bundle
The .mcpb bundle is built automatically by the Release workflow when a version tag is pushed. To build locally:
npm run build
npx @anthropic-ai/mcpb packThis produces zola-mcp.mcpb using the configuration in manifest.json. The bundle includes the compiled dist/bundle.js and user config prompts for ZOLA_REFRESH_TOKEN.
Releasing
Releases are automated via GitHub Actions:
Run the Cut & Bump workflow (manual trigger) — tags the current version and bumps patch
The tag push triggers the Release workflow which:
Runs CI (build + test)
Packages
.skilland.mcpbbundlesPublishes to npm
Creates a GitHub Release with the bundles
License
MIT
Available Tools
77 toolsadd_faqC
Add a new FAQ (question + answer) to the website FAQ page
Inputs: answer (required), question (required), display_order.
add_guestA
Add a new guest group (household) to the guest list, optionally with a partner/plus-one, mailing address and event invitations, so one call creates a fully set-up household. Affiliation is relative to the Zola account owner: PRIMARY_* is the account owner's side, PARTNER_* is the other partner's side (the web UI labels PARTNER_* with the partner's name, e.g. "'s Family Friend"). Check list_guests for duplicates first. Guests are invited only to the events in event_ids — none when omitted. Adds to the list only: no invitation, save-the-date or email is sent.
Inputs: last_name (required), first_name (required), city, tier, +11 more.
add_home_sectionC
Add a story section to the home page (title + subtitle + description block)
Inputs: title (required), subtitle (required), description (required), hidden, +1 more.
add_poiC
Add a point-of-interest to the Things-to-Do page (restaurant, attraction, etc.)
Inputs: title (required), url, city, address1, +10 more.
add_registry_itemA
Add a product (by SKU) to the registry. If collection_id is omitted, the default collection is looked up automatically.
Inputs: sku_id (required), quantity, most_wanted, collection_id, +1 more.
add_travel_itemC
Add a travel item (hotel, flight, train, car, bus) to the Travel page
Inputs: name (required), type (required), url, city, +15 more.
add_vendorC
Book a new vendor
Inputs: city (required), name (required), vendor_type (required), state_province (required), +5 more.
assign_seatADestructive
Assign a guest to a specific seat in a seating chart. A guest can be moved to another seat later, but there is no tool to unseat them again.
Inputs: seat_uuid (required), guest_uuid (required), table_uuid (required), seating_chart_uuid (required).
create_card_projectADestructive
Create a new invitation project from a design suite and a lead variation (specific size/paper). There is no tool to delete a project once created.
Inputs: suite_uuid (required), lead_variation_uuid (required), quantity.
get_budgetARead-only
Get the wedding budget summary including total budgeted, actual cost, paid, and all budget items
Inputs: view.
get_card_projectARead-only
Get full details for one invitation project including all customizations (invitation, envelope, RSVP card, details card), paper/color options, and per-customization pages.
Inputs: project_uuid (required).
get_card_project_guestsARead-only
List the guest groups assigned to an invitation project, including per-group font-size overrides for printed addressing.
Inputs: project_uuid (required).
get_card_suiteARead-only
Get details for an invitation design "suite" (the family of matching invitation + RSVP + details cards), including paper types, sizes, and price range.
Inputs: suite_uuid (required).
get_current_themeARead-only
Get the currently-selected website theme: key, name, swatch color, layout type
Inputs: no named parameters.
get_gift_trackerARead-only
View gift tracking: total gifts received, values, thank-you note status
Inputs: no named parameters.
get_inquiry_conversationBRead-only
Get full conversation for a vendor inquiry including messages and inquiry details
Inputs: uuid (required).
get_registryBRead-only
View the couple's registry items with derived purchase state per item (requested_qty, purchased_qty, marked_fulfilled, availability, inconsistent). Paged via limit/offset.
Inputs: limit, offset.
get_rsvp_pageBRead-only
Get the RSVP page settings on the wedding website (title, intro copy, visibility, customization).
Inputs: no named parameters.
get_seating_chartARead-only
Get full seating chart with all tables, seats, and current occupants
Inputs: uuid (required).
get_storefrontARead-only
Get full details for a vendor storefront (pricing, reviews, photos, about, FAQs)
Inputs: uuid (required).
get_website_customizationsARead-only
Get current website colors, font settings, and available font/color options
Inputs: no named parameters.
get_wedding_dashboardBRead-only
Get the wedding planning dashboard overview (invites, paper, planning progress)
Inputs: no named parameters.
get_wedding_settingsARead-only
Get top-level wedding settings: title, URL slug, partner names, date, city, hashtag, guest count, search visibility
Inputs: no named parameters.
invite_guest_to_eventAIdempotent
Invite a single guest or guest group to an event (additive — does not affect other events). Pass exactly one of guest_group_id (invites all guests in the group) or guest_id (invites just that guest). Idempotent.
Inputs: event_id (required), guest_id, guest_group_id.
list_card_projectsARead-only
List your invitation / save-the-date / shower-invite "card" projects (paper or digital). Returns project UUID, name, customizations, suite, and quantity.
Inputs: limit, include_completed.
list_eventsARead-only
List all wedding events (ceremony, reception, rehearsal dinner, etc.) with RSVP counts
Inputs: view.
list_faqsBRead-only
List all FAQs on the wedding website
Inputs: no named parameters.
list_favorite_card_suitesARead-only
List invitation design suites you have favorited (hearted).
Inputs: no named parameters.
list_favoritesBRead-only
List all favorited/saved vendors
Inputs: no named parameters.
list_guestsARead-only
List all guest groups (households) with stats (total, invited, missing addresses). The default view carries names, ids, tier, invited/RSVP state and per-event invitations but no contact details; pass view:"full" for addresses, emails and phone numbers.
Inputs: view.
list_home_sectionsARead-only
List the story sections on the website home page
Inputs: no named parameters.
list_inquiriesBRead-only
List all vendor inquiries with status, vendor name, and unread flag
Inputs: view.
list_pagesARead-only
List all wedding-website pages with their IDs, types, display order, visibility, and theme info
Inputs: no named parameters.
list_poisARead-only
List points-of-interest on the "Things to Do" page
Inputs: no named parameters.
list_seating_chartsARead-only
List all seating charts with their UUID and event name
Inputs: no named parameters.
list_travel_itemsARead-only
List hotels, flights, and transportation on the website Travel page
Inputs: no named parameters.
list_unseated_guestsBRead-only
List all guests who have not yet been assigned a seat
Inputs: no named parameters.
list_vendorsARead-only
List all booked vendors with details
Inputs: no named parameters.
mark_inquiry_readADestructive
Mark a vendor inquiry conversation as read. There is no tool to mark it unread again.
Inputs: uuid (required).
preview_card_templateARead-only
Render an invitation template preview with text substituted in. Use to see how a design would look with your couple's names and wedding date. Returns the template structure including page layouts.
Inputs: variation_uuids (required), last_name, first_name, wedding_date, +2 more.
preview_qrcodeARead-only
Generate a QR-code PNG for an invitation. Returns the image so it can be inspected (or, if it is ever over 10 MiB on a hosted install, a signed, expiring download link). Use set_card_project_qrcode to actually place it on a card.
Inputs: url (required), enabled, url_type, dimension.
reconcile_registryARead-only
Reconcile the registry against the gift tracker. Returns DUPLICATE_RISK (flagged fulfilled but purchased count is 0 — still buyable), UNATTRIBUTED (purchased with no order behind it, so giver and value are lost), ORPHAN_ORDER (an order with no matching registry item) and a MATCHED count. Read-only.
Inputs: no named parameters.
remove_event_invitationADestructiveIdempotent
Remove an event invitation for a single guest or guest group. Pass exactly one of guest_group_id (removes for all guests in the group) or guest_id (removes for just that guest). Removing an invitation discards the guest’s recorded RSVP for this event (response, meal choice); re-inviting does not restore it. Other events’ invitations are preserved. Idempotent. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: event_id (required), guest_id, confirmToken, guest_group_id.
remove_faqADestructive
Remove an FAQ from the public website. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: faq_entity_id (required), confirmToken.
remove_guestADestructive
Remove a guest group (household) from the guest list. This permanently deletes the household with every RSVP, event invitation and seat assignment its guests had; there is no trash. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: guest_group_id (required), confirmToken.
remove_home_sectionADestructive
Remove a story section from the public home page. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: homepage_entity_id (required), confirmToken.
remove_poiADestructive
Remove a point-of-interest from the public Things-to-Do page. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: poi_entity_id (required), confirmToken.
remove_registry_itemADestructive
Remove an item from the registry that guests shop from. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: collection_item_id (required), confirmToken.
remove_travel_itemADestructive
Remove a travel item from the public Travel page. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: travel_entity_id (required), confirmToken.
remove_vendorCDestructive
Unbook a vendor
Inputs: uuid (required).
reorder_pagesA
Reorder pages in the website navigation. Pass the complete ordered list of page IDs.
Inputs: page_ids (required).
search_card_catalogBRead-only
Search the invitation design catalog. Faceted search returning suites matching the requested card type.
Inputs: limit, card_type.
search_registry_productsARead-only
Browse Zola products in a category, scoped to your registry. Category IDs are Zola constants (e.g. 544 = Kitchen) — exposed via GET /v3/categories in the iOS app.
Inputs: category_id (required), limit, offset.
search_storefrontsCRead-only
Search Zola vendor marketplace by category and location (1=Venues, 2=Photographers, 3=Florists, 7=Planners, 9=Bands/DJs)
Inputs: city (required), state_province (required), taxonomy_node_id (required), limit, +1 more.
search_themesBRead-only
Browse the catalog of available wedding-website themes
Inputs: limit, offset, theme_layout_types.
search_vendorsARead-only
Search for vendors by name (typeahead) within a vendor category
Inputs: query (required), taxonomy_key.
set_card_project_guestsA
Enable / disable guest groups for an invitation project and optionally override font sizes for printed names and addresses. Pass the full list of guest groups you want recorded.
Inputs: guest_groups (required), project_uuid (required).
set_card_project_qrcodeA
Place (or update) a QR code on a specific page of an invitation project. The page UUID comes from get_card_project (look under the customization's pages array).
Inputs: url (required), page_uuid (required), project_uuid (required), color, +3 more.
set_event_guestsADestructiveIdempotent
Set which guest groups are invited to an event (bulk). For each group, invited:true ensures every guest in the group is invited to the event; invited:false removes the invitation — and with it any RSVP the guest recorded for this event (response, meal choice), which cannot be restored. Other events’ invitations are preserved. Idempotent. Use this to assign guests to events in bulk (e.g. by tier/affiliation/location). A call that uninvites anyone asks the user to confirm first (a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds — see MCP_CONFIRM_MODE). A call that only invites runs immediately.
Inputs: event_id (required), guest_groups (required), confirmToken.
swap_card_project_variationA
Swap one or more customizations on a project to different variations (e.g. switch paper type, color, or size). Pass a map of customization UUID → new variation UUID.
Inputs: project_uuid (required), customizations (required).
track_rsvpsBRead-only
Get RSVP tracking summary per event (attending, declined, not responded)
Inputs: no named parameters.
update_budget_itemCDestructiveIdempotent
Update a budget item's actual cost and/or note by UUID
Inputs: uuid (required), note, actual_cost_cents.
update_current_themeCDestructiveIdempotent
Switch the wedding website to a different theme template
Inputs: theme_key (required), theme_layout_type.
update_eventADestructiveIdempotent
Update a wedding event (name, time, venue, location, dress code, RSVP settings). Guests see these details on the website. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: event_id (required), city, name, note, +10 more.
update_faqADestructiveIdempotent
Update an existing FAQ — all three fields (question, answer, display_order) must be supplied
Inputs: answer (required), question (required), display_order (required), faq_entity_id (required).
update_guest_addressCDestructiveIdempotent
Update a guest group's mailing address
Inputs: guest_group_id (required), city, address1, address2, +3 more.
update_home_sectionCDestructiveIdempotent
Update a home page story section — all fields must be supplied
Inputs: title (required), hidden (required), subtitle (required), description (required), +2 more.
update_pageCDestructiveIdempotent
Update page-level metadata (title, intro copy, nav title, visibility, layout customization)
Inputs: page_id (required), title, hidden, nav_title, +4 more.
update_poiBDestructiveIdempotent
Update a point-of-interest. Provide only the fields you want to change.
Inputs: poi_entity_id (required), url, city, title, +11 more.
update_registry_itemBDestructiveIdempotent
Update an existing registry item — all fields must be supplied (it's a full replace)
Inputs: quantity (required), group_gift (required), most_wanted (required), collection_id (required), +3 more.
update_travel_itemBDestructiveIdempotent
Update a travel item. Provide only the fields you want to change.
Inputs: travel_entity_id (required), url, city, code, +16 more.
update_vendorCDestructiveIdempotent
Update a booked vendor's details
Inputs: uuid (required), city, name, email, +4 more.
update_website_customizationADestructiveIdempotent
Update website colors and fonts. Provide only what changes. Colors are 6-char hex without #. Note: when header_font_family_id changes, the wrapper auto-fetches current state and re-sends all active colors to defend against a Zola partial-update wipe bug. body_font_family_id is restricted to [68, 198]. header_color and nav_font_color exist on Zola's web-api endpoint but are NOT writable via the mobile-api this MCP uses — change them in the Zola web UI for now.
Inputs: accent_color, header_color, nav_font_color, body_font_color, +4 more.
update_wedding_settingsADestructiveIdempotent
Update top-level wedding settings. Provide only the fields you want to change; the rest are preserved. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: city, slug, title, hashtag, +10 more.
validate_card_projectARead-only
Validate an invitation project — reports any text-fit, image, or guest-addressing errors per customization. Use before placing an order.
Inputs: project_uuid (required).
zola_healthcheckVerify credentials and upstream reachabilityARead-onlyIdempotent
Resolves the credential the way real tools do, then makes one authenticated request to mobile-api.zola.com. Reports which source supplied the credential, whether mobile-api.zola.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a mobile-api.zola.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 77 tools
Most tools map cleanly to a distinct resource+action (e.g. list_faqs/add_faq/update_faq/remove_faq vs. list_pois/add_poi/...), and the dense descriptions resolve most edge cases. A few clusters risk misselection: invite_guest_to_event vs. set_event_guests vs. remove_event_invitation (single vs. bulk vs. removal), search_vendors vs. search_storefronts (your booked vendors vs. the marketplace), and list_favorites vs. list_favorite_card_suites.
The surface overwhelmingly follows snake_case verb_noun (list_*, get_*, add_*, update_*, remove_*, set_*, search_*), making patterns predictable. Deviations are minor: the server-prefixed zola_healthcheck, the bare-verb track_rsvps and reconcile_registry, and set_page_hidden which inverts the verb_noun ordering.
77 tools is far above the 25-tool ceiling and reflects a very broad domain split into vendors, guests, seating, budget, events, website, registry, cards, and storefronts. While each sub-area is internally well-scoped, an agent must navigate an unwieldy flat list with no obvious grouping or namespacing.
Coverage is unusually broad: full CRUD for website pages, FAQs, home sections, POIs, travel items, and registry items, plus invitation, seating, and guest lifecycle tools. Remaining gaps are real but navigable — no way to create/delete events or add/remove budget line items, no unseat operation after assign_seat, and no delete for card projects.
Maintenance
Related MCP Connectors
Zola MCP server for ChatGPT, Claude and any AI agent: list guests, add guest, track RSVPs, list registry gifts and mark thank-you sent in your own Zola account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Zola yourself; Cotlet does not store your password and you need no Zola API key. About the official Zola API: Zola has no public API, developer docs or webhooks for couples (checked 11 Oct 2026). Guest list, RSVP and gift data leave Zola only as files you download by hand from a desktop browser. Setup and FAQ: https://cotlet.dev/integrations/zola-api-mcp-server
Joy MCP server for ChatGPT, Claude and any AI agent: list guests, add guest, get RSVP status, update event details and list registry gifts in your own Joy account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Joy yourself; Cotlet does not store your password and you need no Joy API key. About the official Joy 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. Setup and FAQ: https://cotlet.dev/integrations/joy-api-mcp-server
Perfect Venue MCP server for ChatGPT, Claude and any AI agent: list events, create lead, update event details, send proposal and list payments in your own Perfect Venue account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Perfect Venue yourself; Cotlet does not store your password and you need no Perfect Venue API key. About the official Perfect Venue API: Perfect Venue has one public API, the Leads API: a write-only endpoint that creates a lead from your own contact form, and only on the Enterprise plan (checked 11 Oct 2026). Events, payments, messages and proposals cannot be read or changed by API. Setup and FAQ: https://cotlet.dev/integrations/perfect-venue-api-mcp-server
Zotero MCP server for Claude and ChatGPT: search, citations, safe writes, PDF passages and pages.
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that integrates Google Calendar with Claude Desktop, enabling users to manage calendar events (view, create, update, delete) through natural language.5167 npm59MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to the HoneyBook client portal, giving you natural-language access to contracts and invoices sent by your wedding vendors.22699 npm1MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that gives Claude (or any MCP-compatible LLM) direct access to a self-hosted WordPress site over its REST API.73MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.11286 npm1MIT