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.22611 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.11544 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.30597 npm14MIT
- 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.535 npm59MIT
- FlicenseNot gradedqualityDmaintenanceA 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 have clearly distinct purposes across wedding planning domains, and descriptions clarify scope (e.g., set_event_guests vs invite_guest_to_event). However, some overlapping invitation tools and guest management operations could cause misselection, and the sheer breadth increases cognitive load.
Tools predominantly follow a consistent snake_case verb_noun pattern (list_guests, add_vendor, update_page, remove_faq). Minor deviation with zola_healthcheck and a few long compound names, but overall highly predictable.
77 tools is an extreme mismatch for a single MCP server, far exceeding the 50+ threshold for severe over-scoping. While the wedding platform is broad, many tools could be consolidated or organized into sub-servers.
Many domains have full CRUD (vendors, FAQs, home sections, POIs, travel, registry), but notable gaps exist: no inquiry reply, no unseat guest, no event create/delete, no page create/delete, and no budget item add/remove. These missing operations create dead ends for common workflows.