@waitlister/mcp
Related Servers
Alternatives to @waitlister/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that connects AI assistants like Claude to your todo app, enabling natural, friendly reminders and task management without a server to run.811 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that gives AI assistants (like Cursor, Claude, Windsurf) the ability to remember user information across conversations using vector search technology.-
- AlicenseAqualityDmaintenanceTurn any data source into an MCP server in 5 minutes. Build knowledge bases that AI assistants like Claude and Cursor can query directly.23 npm23MIT
- AlicenseBqualityDmaintenanceAn MCP server providing comprehensive access to the ClickUp API, enabling AI assistants to manage docs, tasks, spaces, lists, and more.89MIT
- AlicenseNot gradedqualityBmaintenanceAn unofficial MCP server that connects AI assistants to Microsoft Planner, enabling natural language task management such as creating tasks, organizing plans, and managing buckets.17MIT
- AlicenseBqualityDmaintenanceAn MCP server that connects Claude with Todoist for complete task and project management through natural language.86203 npm246MIT
TDQS
Scored across 14 tools
Each tool targets a distinct resource and action: waitlists (create/list), stats, subscribers (add/list/get/update/delete), views, and landing pages (get/create/update/publish/generate). There is no overlap between tools; even get_stats and get_landing_page serve different purposes.
All tool names follow a consistent verb_noun pattern in snake_case (create_waitlist, list_subscribers, publish_landing_page, etc.). Verbs are appropriate and uniformly placed at the start, making the set predictable and easy to navigate.
14 tools is well within the ideal 3-15 range and each tool serves a clear purpose in managing waitlists, subscribers, and landing pages. The count feels proportionate to the domain's complexity without being bloated.
The waitlist lifecycle is incomplete: you can create and list waitlists but cannot update or delete them. There is also no single-waitlist getter (only list), which forces agents to filter through the list. However, subscriber and landing page coverage is thorough, so the gaps are workable.