Bookwhen MCP server
Related Servers
Alternatives to Bookwhen MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients like Claude and ChatGPT to query and manage TicketSource box office data, including events, performances, bookings, customers, and seats, through natural language.7MIT
- FlicenseCqualityBmaintenanceEnables interaction with the Swapcard event platform API, providing tools to manage events, people, sessions, exhibitors, documents, custom fields, meetings, webhooks, and analytics through natural language.32-
- AlicenseBqualityDmaintenanceEnables querying ChurchSuite bookings, resources, ministries, and serving patterns via MCP tools, providing read-only access to church management data.16MIT
- AlicenseNot gradedqualityCmaintenanceProvides structured, read-mostly access to small-business back-office data including customers, invoices, and account notes, allowing Claude to query overdue invoices, revenue summaries, and more.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search, filter, and analyze Microsoft events (conferences, workshops, webinars) using the Microsoft Events API.42MIT
- FlicenseBqualityDmaintenanceMCP server for Cal.com scheduling, providing ~70 tools to manage schedules, event types, bookings, calendars, webhooks, and teams. Enables natural language control of Cal.com from Claude or any MCP-compatible client.68-
TDQS
Scored across 9 tools
Tools are largely distinct, with clear get/list pairs for events, tickets, and locations. get_event side-loads tickets, leaders, and attachments that other specialized tools also expose, creating mild overlap, but descriptions help an agent choose correctly.
All tool names use consistent snake_case with get_ or list_ prefixes and follow a predictable verb_noun pattern. There are no mixed conventions or vague verbs.
With 9 tools, the server is well-scoped for a read-oriented event-booking query surface. Each tool covers a distinct resource or action without obvious redundancy.
The surface covers read/query operations across events, tickets, locations, leaders, attachments, and class passes. However, it lacks any create, update, delete, or booking/checkout operations, which is a notable lifecycle gap for a booking platform.