Skip to main content
Glama

Related Servers

Alternatives to zola-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A 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.
      22
      820 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -

    TDQS

    B3.3/5.0

    Scored across 77 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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

    ActivityActive
    ResponsivenessUsually handled