Zola MCP Server
Zola 婚禮的賓客名單、出席回覆和禮物登記。
託管 MCP 伺服器
npx add-mcp 'https://cotlet.dev/mcp/v1/zola'可安裝到 Claude Code、Codex、Cursor 等客戶端
文件
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Zola API and MCP server: Let your AI agent keep your Zola RSVPs straight.
Zola publishes no API, webhooks or MCP server (checked 24 Oct 2026); zola.com/api and zola.com/developers answer 404. Cotlet hosts 10 Zola tools, over MCP for agents and REST for scripts.
Connect Zola guests, event RSVPs and gifts to your wedding planning workflow. Use an AI agent through MCP or REST requests from automation tools and scripts.
- Free 7-day trial, no card
- Unofficial, not affiliated with Zola
- Page: https://cotlet.dev/integrations/zola-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Zola. Zola is a trademark of its owner. If Zola's own integrations cover what you need, use them first.
What can you automate in Zola?
- Weekly RSVP and meal count for every event
- Enter paper RSVP cards and phone replies
- Add late guests and invite them to events
- Fix mailing addresses before envelopes print
- Track Save the Dates and invitations mailed
- Mark thank-you notes sent in one batch
Does Zola have an MCP server or an API?
- The "Zola" app on Zapier is an unrelated reviews tool, and n8n has none. Guest lists, RSVPs and addresses leave Zola only as downloads from a desktop browser.
- Zola itself is free. Its blog lists the seating chart at $14.99 and premium guest texting at $79.99, both one-time.
- chrischall/zola-mcp on GitHub (MIT) runs on your computer with your Zola login token in a file. It reads RSVPs and the gift tracker but has no tool to record a phone reply or mark a thank-you sent.
| What you need | Zola by hand | zola-mcp (GitHub) | Cotlet |
|---|---|---|---|
| RSVPs and meals across every event | One event at a time | Yes | Yes |
| Record replies from cards and calls | Guest by guest | No tool | Yes, meal checked |
| Mark thank-you notes sent | One gift at a time | No tool | Yes, in batches |
| Where your Zola login lives | Your browser | A token file, about a year | Encrypted Cloud Browser |
| Runs with your computer off | No | On your own server | Yes, hosted |
Checked 24 Oct 2026. Sources: Zola Help: Can I export or print my guest list?, Zola Terms of Use, Zola: best wedding planning apps (prices), chrischall/zola-mcp, Zapier: Zola (reviews platform)
How does Cotlet connect to Zola?
- Sign in to Zola. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Zola password, and none of the Zola tools sends a word to your guests.
Connect Zola 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.
- Sign in to Zola in Cotlet. Make a Cotlet account, open Zola in its Cloud Browser, log in to your couple account and press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP or connector settings of your agent.
- Approve the connection. Chat apps send you to a Cotlet sign-in page; editors, n8n and scripts use an API key from the console.
Zola uses the same https://cotlet.dev/mcp/v1 as every other app on your account. If you enable Zola after connecting, refresh the connector to load the Zola tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-zola \
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-zola": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-zola]
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: zola_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: zola_write
How to use the Zola REST API
Create your Cotlet API key
Create a Cotlet API key with access to Zola and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Sign in to Zola in its Cotlet Cloud Browser and enable the app for agents. Use your own Zola couple account.
Make your first Zola API request
REST:
curl https://cotlet.dev/api/v1/zola/events \
-H "Authorization: Bearer $COTLET_API_KEY"
Read event IDs and request RSVP reports
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": "zola",
"tool": "list_events",
"result": {
"events": [
{
"event_id": "evt_ceremony",
"type": "Ceremony",
"name": "Wedding Ceremony",
"date": "2027-06-12",
"start_time": "15:00"
}
]
}
}
Read result.events and use an event_id with track_rsvps. The event and guest lists have no cursor or page-size inputs.
Guest contact details are excluded unless include_contact=true. Event-specific RSVP results cover the guests invited to that event.
Compare RSVP choices and guest counts on later runs. A guest row alone does not establish attendance at every wedding event.
Zola workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read events and their RSVP reports into an event-by-event attendance and meal summary. |
| Make | HTTP > Make a request | Read guests into a private contact review sheet, including contact fields only when requested. |
| Python or Node.js | REST API | Read gifts into a thank-you review queue without sending notes or changing gift records. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Zola; 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.
Zola API endpoints and MCP tools
Guest list
Addresses, emails and phones come back only when asked for. A plus-one can be set only when the guest is created. No tool deletes a guest.
- List guests (
list_guests, read): Guests with their list (Definitely Invited or Maybe), events invited to and RSVP state. - Add guest (
add_guest, write): Add a guest, optionally with a plus-one, to your guest list. Nothing is sent to the guest. - Invite guest to event (
invite_guest_to_event, write): Mark a guest as invited to an event, so they can RSVP to it on your wedding website.
Events and RSVPs
A reply counts only for an event the guest is invited to, and the meal has to be one of that event's options.
- List events (
list_events, read): Your wedding events with type, name, date and start time. - Track RSVPs (
track_rsvps, read): RSVPs for one event: who is attending, declined or has not replied, with meal choices. - Record RSVP (
record_rsvp, write): Record a reply you got by phone or mail: attending or declined, with meal choice.
Envelopes and mail
The address and the mailed tick on Zola's Address Envelopes page. Nothing is printed or posted.
- Update guest address (
update_guest_address, write): Set the mailing address used for Save the Dates and invitation envelopes. - Mark mail sent (
mark_mail_sent, write): Track that a guest has received a Save the Date or an invitation.
Gifts and thank-you notes
Surprise gifts show after their reveal date, Venmo cash fund gifts after the guest reports them.
- List gifts (
list_gifts, read): Gift tracker: each gift with giver, message, value, giver address, order status and thank-you note status. - Mark thank-you sent (
mark_thank_you_sent, write): Mark the thank-you note for one or more gifts in the gift tracker as sent.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/zola-api-mcp-server#tools
Who can see my Zola session, and how do I revoke it?
- What we store. Your logged-in Zola browser profile, AES-256-GCM, in Finland. No password.
- What your agent gets. The 10 Zola tools and no cookie or login token.
- What the session sees. Your whole Zola account: guests, addresses, RSVPs, registry and gifts.
- What no tool touches. Cash fund transfers, store credit, registry orders, vendor messages, the seating chart.
- If Zola logs you out. We email you a link to log in again. We never log in for you.
- How to cut access. Disable Zola for agents, reset the browser or delete the API key.
In May 2022 attackers took over Zola couples' accounts and went after their cash funds (Money, 23 May 2022), so a signed-in Zola session is worth guarding. Ours scores A+ at Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Matches each card. By surname, and asks when two guests fit.
- Checks the invite. No reply for an event the guest is not on.
- Maps the meal. "The fish" becomes Salmon, or it asks.
- Reads totals back. New counts per event, and what it skipped.
| Action | Undo |
|---|---|
| Record an RSVP | Yes, record it again |
| Mark a thank-you sent | Yes, sent set to false |
| Update an address | Yes, call again with the old one |
| Invite a guest to an event | Remove the invite in Zola by hand |
| Add a guest | Delete the guest in Zola by hand |
None of the 10 tools waits for approval, because none sends anything to a guest or spends money. A recorded RSVP still changes the head count your caterer gets, so read the totals the agent reports. Want to look first? Enable Zola read only, and only the 4 read tools work.
A card with a plus-one Zola does not have is reported, not recorded. Add the plus-one in Zola first.
MCP call:
{
"name": "mark_thank_you_sent",
"arguments": {
"gift_ids": [
"gft_8f21c4",
"gft_8f21d9"
],
"sent": true
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/zola/thank-you-sent/mark \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"gift_ids":["gft_8f21c4","gft_8f21d9"],"sent":true}'
Tool output:
{
"updated": [
{
"gift_id": "gft_8f21c4",
"gift": "Dutch Oven",
"giver": "Alex Example",
"thank_you": "sent"
},
{
"gift_id": "gft_8f21d9",
"gift": "Honeymoon Fund",
"giver": "Sam Example",
"thank_you": "sent"
}
]
}
A script or cron job reaches the same tools over REST at /api/v1/zola, with the same key and price. A reply with a meal the event does not offer fails, and a failed call costs nothing. The tools table lists the REST path of each tool.
How much does the Zola MCP server cost?
About $13 a month for a 145-guest wedding with three events in the month before the RSVP deadline, 2,280 credits. Zola itself is free.
| Job | Calls | Credits |
|---|---|---|
| RSVP and meal report for every event, weekly | 5 × 4 | 200 |
| Enter the week's RSVP cards and calls | 9 × 4 | 360 |
| Mark invitations mailed, fix addresses | 8 × 2 | 160 |
| Add late guests and invite them to events | 6 × 1 | 60 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,280 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Marking 12 thank-yous sent is one call
145 guests is the average in Zola's First Look Report 2026 (over 11,500 couples); the calls per job are our example. The browser is most of the bill, so turn it off between the RSVP deadline and the thank-yous. Dollars at the $29 pack rate.
Zola MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| chrischall/zola-mcp | 77 tools over Zola's internal mobile API: vendors, budget, seating, guests, website pages, invitations. MIT, 3 stars, last commit 19 Oct 2026. | Runs on your computer with Node 22 and a login token good for about a year. No tool to record a reply or mark a thank-you sent. Its README says no human has audited the code. |
| avegancafe/zola-mcp-remote | Wraps zola-mcp as a remote server for chat apps. | Created 24 Oct 2026, no license or docs; you host it. |
| Text My Wedding | Texts households from a Zola export, with RSVP links and reminders; $19 to $237 per wedding. | A file upload: the two guest lists do not sync. |
| Zola premium guest texting | Zola's own group texts and scheduled sends, $79.99 per its blog. | Messages only, US numbers, no agent access. |
zola-mcp covers much more of Zola than our ten tools, so pick it if you want the seating chart or budget and are happy to run Node and guard the token file. Cotlet is the hosted choice for the RSVP and thank-you work: nothing to install, a session we keep encrypted, and repairs that are ours when Zola changes.
Who runs Cotlet
Cotlet is built by Take Group sp. z o.o., a software company in Poland, EU (VAT PL6342984273), running since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Zola tools.
Zola API and MCP: questions
Can I use the Zola 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, choose Zola under Integrations in the console and log in to Zola in its Cloud Browser. The trial starts when you sign up, no card asked.
How do I connect Zola to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Zola 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 Zola account through Cotlet, in their phone apps too.
What can ChatGPT do in Zola?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Zola: add guests from a spreadsheet and invite them to events; weekly RSVP and meal count report; record RSVPs from phone calls and paper cards. You ask in plain words, and anything that reaches other people waits for your OK first.
Can the agent download my guest list as a file?
It reads the same data directly, so no download is needed. Zola's own exports of the guest list, RSVPs and gifts are manual and work from a desktop browser only (checked 11 Oct 2026).
Can the agent send RSVP reminders?
No. None of the Zola tools messages guests. The agent gives you the names per event, and Zola's own Bulk Actions > Send Message on the Guest List emails the guests you select.
Does Zola have webhooks?
No. Zola sends no event when a guest replies or a gift arrives. Run your agent on a schedule instead, for example track_rsvps for each event every Monday until the deadline.
Can it work on my seating chart or budget?
Not yet. The Zola tools cover guests, events, RSVPs, mail tracking and gifts. The zola-mcp server on GitHub has seating and budget tools if you run it yourself.
Is the MCP server different from the REST API?
Only in how you call it. Both carry the same 10 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Zola?
No. Cotlet is independent and not affiliated with Zola, 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.