zola-mcp
Related Servers
Alternatives to zola-mcp
No user-submitted related servers found.
Related Servers
- 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.221,373 npm1MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.251,216 npm10MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.111,254 npm1MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that integrates Google Calendar with Claude Desktop, enabling users to manage calendar events (view, create, update, delete) through natural language.589 npm59MIT
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables Claude (or any MCP client) to read and write Clio Manage data—contacts, matters, activities—directly from chat, with flat-fee billing support in one call.-
- 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
TDQS
Scored across 77 tools
Most tools target a distinct resource and action (e.g., guests, events, vendors, registry, website sections), making their purposes clear. A few pairs could be confusing — search_vendors vs search_storefronts and set_page_hidden vs update_page — but the descriptions mostly resolve the boundaries.
The vast majority of tools follow a consistent verb_noun pattern (list_*, add_*, remove_*, update_*, get_*). Minor deviations exist: zola_healthcheck is a prefixed noun instead of a verb, and there's a singular/plural mismatch between get_website_customizations and update_website_customization.
77 tools far exceeds the threshold where an agent can efficiently scan and select the right one.pycountry The server attempts to cover an enormous wedge of wedding planning functionality, but the count creates an extreme mismatch for an MCP tool surface.
The surface is broad, covering guests, events, vendors, website content, registry, cards, seating, budget, and themes. However, there are notable gaps: no create/delete events, no update for guest contact details beyond address, no delete for card projects or seating charts, and budget only supports updating existing items.