Skip to main content
Glama
klajdishira

Swapcard MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
swapcard_get_eventA

Get a single Swapcard event by ID, including title, dates, description, address, groups, community, and stats.

swapcard_get_eventsC

Get multiple Swapcard events by their IDs in one request.

swapcard_list_event_peopleA

List or search attendees/people in an event with optional email filter and cursor-based pagination.

swapcard_import_event_peopleC

Create or update attendees/people in bulk. Supports groups, barcodes, speaker roles, exhibitor memberships, and custom fields.

swapcard_delete_event_peopleB

Permanently delete people from an event by their Swapcard person IDs.

swapcard_list_sessionsA

List or search sessions/plannings in a community. Filter by event, format, speaker; sort by various fields.

swapcard_import_sessionsB

Create or update sessions/plannings in bulk. Supports all formats, video types, access control, and custom fields.

swapcard_delete_sessionsB

Delete sessions/plannings from an event by their IDs.

swapcard_list_exhibitorsC

List or search exhibitors in a community.

swapcard_upsert_exhibitorsB

Create or update exhibitors in an event.

swapcard_update_exhibitorC

Update a single exhibitor's details including features and background image.

swapcard_delete_exhibitorsB

Delete exhibitors from an event by their IDs.

swapcard_list_event_documentsC

List all documents attached to an event.

swapcard_create_event_documentC

Attach a new document (URL-based) to an event.

swapcard_update_event_documentC

Update an existing event document.

swapcard_delete_event_documentsB

Delete one or more event documents by their IDs.

swapcard_create_documentC

Create a community-level document (v2), optionally scoped to an event.

swapcard_update_documentB

Update a community-level document (v2) by its ID.

swapcard_get_custom_fieldsA

Get all custom field definitions for an event, optionally filtered by target entity type.

swapcard_get_select_field_optionsA

Get all Select and MultipleSelect custom field definitions with their option values.

swapcard_create_custom_fieldC

Create a new custom field definition on an event.

swapcard_update_custom_fieldC

Update an existing custom field definition.

swapcard_delete_custom_fieldsB

Delete custom field definitions from an event.

swapcard_list_meetingsA

List meetings in an event with optional ID/date filters and cursor pagination.

swapcard_list_webhooksA

List all webhook subscriptions configured for an event.

swapcard_create_webhookC

Register a new webhook subscription for an event.

swapcard_update_webhookC

Update an existing webhook subscription's endpoint or event types.

swapcard_delete_webhookA

Delete a webhook subscription by its ID.

swapcard_get_my_exhibitorsC

Get the list of exhibitors accessible to the authenticated Leads API token.

swapcard_get_my_leadsB

Get all leads (scanned contacts) for a specific exhibitor at a specific event.

swapcard_scan_badgesB

Scan attendee badges on behalf of an exhibitor. Optionally set rating (1-5) and note per badge.

swapcard_export_analyticsA

Export raw analytics event records for one or more events. Data has ~10-minute delay. Cursor-paginated.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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