Skip to main content
Glama
ilpr

@waitlister/mcp

by ilpr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @waitlister/mcp

No user-submitted related servers found.

    Related Servers

    • nudge

      davesleal
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that connects AI assistants like Claude to your todo app, enabling natural, friendly reminders and task management without a server to run.
      8
      6 npm
      MIT

    • akyn-ai

      IlyesTal
      A
      license
      A
      quality
      D
      maintenance
      Turn any data source into an MCP server in 5 minutes. Build knowledge bases that AI assistants like Claude and Cursor can query directly.
      2
      5 npm
      22
      MIT

    • wishlist-mcp

      teslakoile
      A
      license
      Not graded
      quality
      B
      maintenance
      Hosted MCP server that lets Claude, ChatGPT, or Codex read and update a user's wishlist.fit wishlist on their behalf, with tool parity matching the web app's capabilities.
      MIT
    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.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources