# Zola (remote · mcp.zola.com)

Find US wedding vendors, registry gifts and invitations, and Zola's wedding planning answers.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.zola.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-zola-zola/mcp.md), [page](https://verifymcp.io/servers/com-zola-zola/mcp)

## Channel facts

- Endpoint: `https://mcp.zola.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.55`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3030 tokens (~189/item across 16 items; 15 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Zola MCP server?

Zola is a hosted endpoint at https://mcp.zola.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-zola-zola 'https://mcp.zola.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-zola-zola": {
      "url": "https://mcp.zola.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-zola-zola": {
      "type": "http",
      "url": "https://mcp.zola.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-zola-zola]
url = "https://mcp.zola.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-zola-zola": {
      "type": "remote",
      "url": "https://mcp.zola.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-zola-zola --url 'https://mcp.zola.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-zola-zola:
    url: "https://mcp.zola.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-zola-zola": {
      "Transport": "http",
      "Url": "https://mcp.zola.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-zola-zola -t streamable-http -u 'https://mcp.zola.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-zola-zola": {
      "type": "http",
      "url": "https://mcp.zola.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 69, 0)

- [functional] Server version: 1.0.55 → 1.0.56

### 2026-11-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 68)

First indexed and scored.

## MCP tools (15)

### `zola_search_vendors` (~930 tokens)

Search Zola Wedding Vendors

Browse and search wedding vendor listings on Zola by type, location, price, and style. Returns vendor profiles with photos, ratings, and pricing. Supports venues, photographers, videographers, florists, bands and DJs, hair and makeup, caterers, cakes and desserts, planners, bar services, officiants, and other services such as attire, dance floors, and floral preservation. Only call this tool if the user is looking to find or compare specific vendors, not for general wedding planning advice.

Input parameters:

- `city` (string): City name to search in (optional)
- `filters` (object): Map of filter keys to arrays of filter values. Available filters vary by vendor_type. Can be null or omitted if no filters are needed. venue filters: - "venue-service-level": ["venue-service-level-a…
- `limit` (number): Number of results to return. Always use 8 unless user explicitly specifies a different number (max: 20)
- `max_price_cents` (number): Maximum price in cents (optional)
- `max_venue_capacity` (number): Maximum venue guest capacity (only for venue)
- `min_price_cents` (number): Minimum price in cents (optional)
- `min_venue_capacity` (number): Minimum venue guest capacity (only for venue)
- `offset` (number): Results to skip for pagination (max: 200). Always use 0 unless user requests pagination
- `state` (string): State code (e.g., 'NY', 'CA') to search in (optional)
- `target_dates` (array): Target wedding dates in ISO 8601 format
- `vendor_type` (string, required): Type of wedding vendor to search for

Output parameters:

- `location_candidates` (array): The places that match the city, with ambiguous_location
- `search_params` (object): Search parameters used
- `status` (string): Why there are no vendors: Zola has no location for the city, or more than one place has the name
- `total` (number): Total number of vendors returned
- `vendors` (array): Summary of matching vendors

### `zola_get_vendor_details` (~78 tokens)

Get Zola Vendor Details

Get detailed information about a specific wedding vendor on Zola including pricing, packages, FAQs, reviews, and more. Use the vendor slug from search results.

Input parameters:

- `slug` (string, required): The vendor slug (e.g., 'brooklyn-winery', 'stanley-productions-inc'). This is the URL-friendly identifier for the vendor.

Output parameters:

- `badges` (array): Vendor badges and awards
- `description` (string): Full description of the vendor
- `faqs` (array): Frequently asked questions
- `headline` (string): Short tagline or headline
- `location` (object): Location information
- `name` (string): Vendor business name
- `packages` (array): Available packages
- `pricing` (object): Pricing information
- `reviews` (object): Review summary
- `slug` (string): URL-friendly identifier
- `vendor_url` (string): URL to vendor's Zola page

### `zola_estimate_wedding_budget` (~205 tokens)

Estimate Wedding Budget

Use this when the user asks how much a wedding costs in general, or how to split a budget. Zola's general estimate of the total cost of a wedding in a US city, state, or wedding market, and the typical cost of each budget category (venue, catering, photographer, and more), from Zola data. Not for finding vendors. Do not use for the couple's own budget, costs or payments: use zola_get_my_budget.

Input parameters:

- `guest_count` (integer): Number of guests. Omit when the user did not say.
- `location` (string): City and state (for example 'Chicago, IL'), a state ('Texas'), or a wedding market ('Long Island'). Omit for a United States estimate.
- `total_budget` (integer): The couple's own total budget, in whole US dollars, from 1,000 to 10,000,000. When given, the categories split this total.

Output parameters:

- `categories` (array): Typical cost of each budget category
- `estimate_location` (string): The place that the estimate is for. It can be the state or the country when Zola has no data for the requested place.
- `guest_count` (number): Guest count of the estimate
- `guest_count_note` (string): Why the guest count of the estimate is not the requested count
- `location_candidates` (array): The places that match the requested name, when there is more than one
- `requested_location` (string): The place name that was asked for
- `status` (string): estimate: the estimate is in this result. ambiguous_location: more than one place matches. location_not_found: Zola does not know the place.
- `total` (object): Estimated total wedding cost
- `total_budget_cents` (number): The couple's own total budget, in cents. When present, the categories split this total.

### `zola_get_planning_timeline_template` (~188 tokens)

Get Wedding Planning Timeline Template

Use this when the user asks what a couple usually does by when, for a wedding date. Zola's general planning timeline template, dated: the planning milestones for a wedding date and a wedding format (traditional, small, destination, elopement, or courthouse). Each milestone has a start date and a due date, counted back from the wedding date, and a status relative to today: late, now, later, or after the wedding. A milestone that applies only in some cases, for example a honeymoon, is marked optional. Do not use for the couple's own tasks or progress: use zola_get_my_checklist or zola_get_my_planning_overview.

Input parameters:

- `format` (string): Wedding format. The default is traditional.
- `wedding_date` (string, required): Wedding date, YYYY-MM-DD. From today to 5 years after today.

Output parameters:

- `format` (string): Wedding format of the timeline
- `milestones` (array): The milestones of the format, late and now first, then by due date
- `today` (string): The day that the statuses are relative to, YYYY-MM-DD (UTC)
- `wedding_date` (string): Wedding date, YYYY-MM-DD

### `zola_get_tipping_guide` (~139 tokens)

Get Wedding Tipping Guide

Zola's general tipping guide: how much couples tip wedding vendors (caterer, hair and makeup, photographer, videographer, DJ or band, planner, drivers, officiant, florist, delivery and setup teams), from Zola's tipping guide and Zola's 2026 Wedding Spend Survey. With a vendor type and its service cost, also gives the tip range in US dollars.

Input parameters:

- `service_cost` (number): What the vendor costs, in US dollars. Only with vendor_type, for a vendor with a percent tip.
- `vendor_type` (string): Vendor type. Omit for all vendor types.

Output parameters:

- `source` (object): The Zola article that gives these values
- `vendors` (array): The tips for each vendor type

### `zola_suggest_cash_gift_amount` (~76 tokens)

Suggest a Wedding Gift Amount from Zola's Guide

Zola's general guideline for how much a guest spends on a wedding gift, in cash or from the registry, for the guest's relationship to the couple, and the average wedding gift from Zola's 2026 First Look Report.

Input parameters:

- `relationship` (string, required): The guest's relationship to the couple

Output parameters:

- `average_gift_usd` (number): Average wedding gift in Zola's 2026 First Look Report, in US dollars
- `high_usd` (number): High end of Zola's guideline, in US dollars
- `low_usd` (number): Low end of Zola's guideline, in US dollars
- `most_guests` (object): What most guests spend, from Zola's 2026 First Look Report
- `open_ended_high` (boolean): True when the guideline is high_usd or more
- `relationship` (string): The guest's relationship to the couple
- `source` (object): The Zola article that gives these values

### `zola_get_who_pays_guide` (~70 tokens)

Get Who Pays Guide for the Wedding

Zola's general guide to who traditionally pays for each wedding cost (the bride's parents, the groom's parents, the couple, the wedding party, or the guests), and how couples pay for their wedding today, from Zola's guide. It gives no percentages.

Output parameters:

- `facts` (array): How couples pay for their wedding today
- `items` (array): Wedding costs and who traditionally pays for each
- `source` (object): The Zola article that gives these values

### `zola_get_wedding_day_timeline_template` (~140 tokens)

Get Wedding Day Timeline Template

Use this when the user asks for an example schedule of a wedding day. Zola's general wedding day timeline template, from the guest arrival to the farewell, moved to the given ceremony time. The example day starts 1 hour before the ceremony and ends 5 hours after it, so the ceremony time must be from 07:00 to 19:00. Do not use for the times of the couple's own events: use zola_get_my_wedding_events.

Input parameters:

- `ceremony_time` (string, required): Ceremony time, HH:MM, 24-hour, from 07:00 to 19:00

Output parameters:

- `ceremony_time` (string): Ceremony time, HH:MM, 24-hour
- `events` (array): The events of the wedding day, in time order
- `source` (object): The Zola article that gives these values

### `zola_estimate_wedding_alcohol` (~327 tokens)

Estimate Wedding Alcohol

Zola's general estimate of how much alcohol to buy for a wedding bar: the total drinks, the bottles of wine, the 750 ml bottles of liquor, the cases of beer, and the champagne for a toast. It counts 1.5 drinks per guest who drinks in the first hour and 1 drink each hour after, multiplied by 0.75 for a crowd that drinks below average and 1.5 for a crowd that drinks above average. The pours are the standard US pours: 5 oz of wine, 1.5 oz of liquor, 12 oz of beer. The default mix is 50% wine, 30% liquor, and 20% beer. For a beer-and-wine bar, give a mix with 0% liquor. It gives no cost.

Input parameters:

- `champagne_toast` (boolean): Add 1 glass of champagne per guest who drinks for the toast. Default false
- `crowd` (string): How much the guests drink. Default average
- `guest_count` (integer, required): Number of guests
- `hours` (number, required): Hours of the bar, with the cocktail hour, in half hours, from 1 to 12
- `mix_percent` (object): Share of the drinks for each type, in percent, that adds up to 100. Default 50% wine, 30% liquor, 20% beer
- `non_drinkers` (integer): Guests in guest_count who will not drink alcohol, with the guests under 21. Default 0

Output parameters:

- `assumptions` (object): The values that the estimate uses
- `beer` (object): Beer
- `champagne_toast` (object): Champagne for the toast, only with champagne_toast
- `crowd` (string): How much the guests drink
- `drinking_guests` (number): Guests who drink: the bar and the toast are for them
- `guest_count` (number): Number of guests
- `hours` (number): Hours of the bar
- `liquor` (object): Liquor
- `non_drinkers` (number): Guests who do not drink alcohol
- `sources` (array): The Zola article, and the Moët page for a toast
- `total_drinks` (number): Drinks for the whole bar, rounded up. The toast is not in it
- `wine` (object): Wine

### `zola_search_help_articles` (~169 tokens)

Search Zola Help Center Guides

Use this when the user asks how a Zola product or service works. Zola's general help articles from the Zola Help Center, about Zola's own products and services: the registry, gift orders and shipping, cash funds and fees, the wedding website, invitations and paper orders, the guest list, the vendor marketplace, and the Zola account. Not for general wedding advice. Do not use for the state of the couple's own orders, gifts, cash fund or store credit: use zola_get_my_order_history, zola_get_my_gift_tracker, zola_get_my_cash_fund_status or zola_get_my_credits.

Input parameters:

- `query` (string, required): The question about Zola, for example 'How do guests ship a gift to my address?'

Output parameters:

- `help_center_url` (string): The Zola Help Center
- `results` (array): The best help articles, best first
- `status` (string): no_results when the help center has no answer for the question

### `zola_search_wedding_advice` (~87 tokens)

Search Zola Wedding Advice

Search the Zola expert advice articles for wedding planning and etiquette: dress codes, invitation wording, traditions, ceremony and reception ideas, and how-to guides. Each result links its Zola article. Not for questions about Zola's own products and orders.

Input parameters:

- `query` (string, required): The wedding planning topic or question, for example 'what does black tie optional mean'

Output parameters:

- `results` (array): The best Zola expert advice articles, best first
- `status` (string): no_results when no Zola article matches

### `zola_find_couple` (~156 tokens)

Find a Couple on Zola

Find the Zola wedding website and registry of one couple, for a guest who knows the couple. Give the first and last name of one partner, and the name of the other partner or the year and month of the wedding. Gives the links of one couple only, from the couples who let guests find them on zola.com. When no single couple matches, gives the zola.com couple search.

Input parameters:

- `first_partner` (string, required): The first and last name of one partner
- `second_partner` (string): The name of the other partner
- `wedding_month` (string): The year and month of the wedding, YYYY-MM, for example 2027-06. Necessary when second_partner is not given

Output parameters:

- `names_on_zola` (string): With found_close_names only: the Zola spelling of the names that the user gave
- `registry_url` (string): The couple's Zola registry
- `search_url` (string): With not_found: the zola.com couple search for the names given
- `status` (string): found: one couple with the names given. found_close_names: one couple with names that are near the names given, which the user must make sure of. not_found: no single couple matches, so use search_url
- `website_url` (string): The couple's Zola wedding website
- `wedding_month` (string): The month of the wedding, for example 'June 2027'

### `zola_search_registry_products` (~101 tokens)

Search the Zola Registry Shop

Search the products of the Zola registry shop, for registry ideas or a gift: kitchen, home, travel, experiences, and more, with the price and the product page. Not for finding a couple's own registry.

Input parameters:

- `max_price` (integer): The highest price in whole US dollars
- `query` (string, required): What to find, with the type, brand, color, or style, for example 'cast iron dutch oven'

Output parameters:

- `products` (array): The matching products of the Zola registry shop
- `search_url` (string): The zola.com shop search, when the products of the search are all above max_price
- `status` (string): no_results when no product of the Zola registry shop matches

### `zola_search_invitations` (~173 tokens)

Search Zola Invitations and Paper

Search the Zola paper shop for wedding invitations, save the dates, thank-you cards, and other wedding paper, by color, motif, and finish (foil, letterpress, custom photo). Each design links its page on zola.com.

Input parameters:

- `card_type` (string, required): The kind of card
- `colors` (array): Colors, for example 'green' or 'dusty blue'. A search without a match gives the available colors
- `custom_photo` (boolean): Only designs with the couple's photo
- `foil` (boolean): Only designs with foil
- `letterpress` (boolean): Only letterpress designs
- `motifs` (array): Motifs or styles, for example 'floral' or 'barn & country'. A search without a match gives the available motifs

Output parameters:

- `available_colors` (array): Color values for the colors filter
- `available_motifs` (array): Motif values for the motifs filter
- `card_type` (string): The card type of the search
- `designs` (array): The matching designs, in the zola.com shop order
- `status` (string): no_results when no design matches the filters
- `total` (number): Number of designs that match on zola.com

### `zola_get_support_options` (~82 tokens)

Get Zola Customer Support Options

Get the contact details for Zola customer support: email, phone number, support hours, and the Zola Help Center, plus the contacts for wedding vendors, product vendors, and the press. Use when the user asks how to contact Zola, or needs a person to solve a problem with an order, a payment, or a Zola account.

Output parameters:

- `email` (string): Zola customer support email address
- `help_center_url` (string): Zola Help Center with answers to common questions
- `hours` (string): When customer support answers email and phone, in US Eastern Time (IANA time zone America/New_York)
- `other_contacts` (array): Contacts for vendors and the press. Couples and guests use email and phone
- `phone` (string): Zola customer support phone number, in the US, with the country code

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-zola-zola/mcp#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68

## Common questions

### What is the Zola MCP server?

Zola is an MCP server listed in the public MCP registry as com.zola/zola. Find US wedding vendors, registry gifts and invitations, and Zola's wedding planning answers. This page covers its hosted endpoint (https://mcp.zola.com/mcp).

### Is the Zola MCP server safe to use?

Zola scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Zola MCP server expose?

Zola exposes 15 tools: zola_search_vendors, zola_get_vendor_details, zola_estimate_wedding_budget, zola_get_planning_timeline_template, zola_get_tipping_guide, and 10 more. Their descriptions and schemas cost roughly 2,921 tokens of context every time the server is loaded.

### Does the Zola MCP server require authentication?

No. We connected to Zola without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zola MCP server still maintained?

Zola is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zola MCP server?

VerifyMCP ran 13 checks on Zola, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about Zola: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.zola.com/mcp
- Website: https://www.zola.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-zola-zola/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-zola-zola/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-zola-zola/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-zola-zola/mcp
