Skip to main content
Glama
Sign In
vitta-mcp

vitta-mcp

by leonardobrigolini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to vitta-mcp

No user-submitted related servers found.

    Related Servers

    • G-Guest MCP server

      BlondeDevRules
      A
      license
      A
      quality
      B
      maintenance
      Book a table, an appointment or a place in a class at a real local business. Live availability, instant confirmation, no account and no API key. Eight tools: search, fetch, get_business, check_availability, create_booking, check_booking, cancel_booking and request_listing. Guest emails in eight languages. Hosted at https://g-guest.app/api/mcp
      8
      10 npm
      MIT

    • Booksy MCP Server

      cotletdev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and scripts to run a Booksy Biz account through your own signed-in Chrome session, exposing 28 tools for appointments, open slots, time off, clients, services, staff, reviews, Message Blasts, and reports over MCP, REST, or Python. Read-only mode and confirmation-gated client-facing actions let you plan schedules, reschedules, and outreach with human approval.
      2
      28
      152 PyPI
      6
      Elastic 2.0
    • OpenBooking MCP Server

      OpenBooking MCP Serverofficial

      openbooking-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to discover availability, place expiring holds, and confirm or cancel appointments for connected booking businesses, with idempotent retries and explicit user consent.
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct step of the booking lifecycle: business lookup, availability discovery, booking, listing the user's appointments, and cancellation. There is no overlap or risk of misselection, and descriptions explicitly state prerequisites (service_id, appointment_id, starts_at).

    Naming Consistency5/5

    All names follow a consistent verb_noun snake_case pattern (get_business, list_my_appointments, find_available_slots, book_appointment, cancel_appointment). Verbs are distinct and predictable throughout.

    Tool Count5/5

    Five tools map cleanly onto the minimal end-to-end booking flow, with each tool earning its place. Nothing feels padded or thin for a single-purpose booking server.

    Completeness4/5

    The core lifecycle (discover business → check availability → book → list → cancel) is fully covered with no dead ends. Minor gaps remain: no reschedule/update appointment and no business search by name or location, though agents can work around these.

    Resources