Skip to main content
Glama

Related Servers

Alternatives to b2match-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      B
      maintenance
      Enables 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
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables read-only access to public Swedish sports competition data, including federations, districts, schedules, results, standings, team searches, matches by date, and detailed match protocols. It provides these capabilities through MCP tools without requiring login, a browser, or credentials.
      9
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the Wisembly API to fetch and manage event data, including event details, participants, organizers, and locations.
      2
      1
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to browse curated city event feeds, retrieve full details for individual events, and list an organizer's public calendar without authentication. It returns only public event metadata, stripping attendee, guest, host, and manager data before responding.
      580 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to browse public event listings from explore pages and fetch full detail for a single event — titles, descriptions, times, locations, host display names, and aggregate RSVP counts — across eight supported city regions. Keyless and read-only, with no guest lists, contact info, or authentication required.
      268 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only access to Crisp customer support, live chat, CRM, and helpdesk data, including conversations, contacts, knowledge base, campaigns, operators, visitors, and site settings, via the official REST API v1.
      MIT

    TDQS

    A4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action scopes, and descriptions actively cross-reference alternatives (e.g., list_participants vs get_participant vs my_participation). The scheduling cluster (my_schedule, my_meetings, my_availability, find_meeting_slots, meeting_recommendations) is the main area where an agent could still hesitate, but the descriptions provide enough differentiation.

    Naming Consistency4/5

    Names overwhelmingly use snake_case with predictable get_/list_/find_/my_ verb or scope prefixes. A few outliers (auth_status, meeting_recommendations, list_my_events) and the my_* prefix mixing viewer scope with noun phrases are minor deviations rather than a broken pattern.

    Tool Count3/5

    At 22 tools this is a heavy surface, with many parallel read operations across events, participants, organisations, opportunities, agenda, meetings, conversations, and notifications. Most tools do earn their place given the breadth of the platform, but the count sits in the borderline-heavy range.

    Completeness3/5

    Read/discovery coverage is broad, spanning events, participants, organisations, opportunities, agenda, speakers, meetings, conversations, and notifications. However, the surface is largely read-only: there is no send-message, meeting request/book/cancel, event registration, or profile-edit tool, which are notable gaps for an event-networking workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues