Skip to main content
Glama
klajdishira

Swapcard MCP Server

by klajdishira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Swapcard MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Microsoft Events MCP Server

      trsdn
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to search, filter, and analyze Microsoft events (conferences, workshops, webinars) using the Microsoft Events API.
      4
      2
      MIT

    • Wisembly MCP Server

      juliengrelet
      F
      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
      -

    • mcp-swagger

      awssam
      A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      8
      2
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 32 tools

    Disambiguation3/5

    Most tools target clearly distinct resources, but there are confusing overlaps: swapcard_create_document vs swapcard_create_event_document and swapcard_update_document vs swapcard_update_event_document are easy to mix up. get_my_exhibitors vs list_exhibitors and upsert_exhibitors vs update_exhibitor also require careful reading.

    Naming Consistency3/5

    The swapcard_ verb_noun prefix pattern is consistent, but the verb choice is mixed: get_event/get_events use 'get' while list_event_people/list_sessions/list_exhibitors use 'list'. Pluralization is inconsistent too, with delete_webhook singular but delete_event_documents and delete_custom_fields plural.

    Tool Count2/5

    32 tools is heavy for even a broad event management server, and the set spans many subdomains including events, people, sessions, exhibitors, documents, webhooks, custom fields, meetings, leads, and analytics. This will overwhelm an agent during tool selection. The count clearly exceeds the 25-tool threshold where coherence tends to degrade.

    Completeness3/5

    Core workflows are well covered: people import/list/delete, session list/import/delete, exhibitor list/upsert/update/delete, webhook CRUD, and custom field CRUD. However, events are read-only, meetings only have a list operation, and community-level documents have no list or delete tool, leaving notable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources