Skip to main content
Glama
juliengrelet

Wisembly MCP Server

by juliengrelet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Wisembly MCP Server

No user-submitted related servers found.

    Related Servers

    • Swapcard MCP Server

      klajdishira
      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
      -

    • b2match-mcp

      barzoj
      A
      license
      A
      quality
      A
      maintenance
      Enables read-only access to B2match event and matchmaking data through tools for events, participants, organisations, opportunities, agenda, sessions, speakers, and authenticated meeting, schedule, conversation, and notification workflows. Supports anonymous public queries and secure local token-based access.
      2
      22
      164 npm
      MIT

    • Cvent MCP Server

      cmcintosh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables management of Cvent events, registrations, attendees, sessions, contacts, surveys, reports, custom objects, and webhooks via natural language through the Cvent REST API.
      MIT

    • Partiful MCP Server

      pipeworx-io
      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.
      73 npm
      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

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one fetches event data by keyword, while the other fetches session data by event ID. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the input parameter.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'get_wisembly_' prefix, using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count2/5

    With only 2 tools, the server feels thin for a Wisembly API integration. This minimal set lacks essential operations like creating, updating, or deleting events/sessions, limiting its utility for comprehensive agent workflows in this domain.

    Completeness2/5

    The tool surface is severely incomplete for a Wisembly API server. It only provides read operations (get_event and get_sessions), missing critical CRUD functionality such as create_event, update_event, delete_event, and session management operations, which are essential for full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources