Integrations

BoothRev connects to your other tools in two directions, and both run through the same underlying protocol: MCP (Model Context Protocol). CSV is the third, simplest channel — no live connection, just a file.

Inbound — bringing context in to work with

Integration	What it does	Who
Connecting Claude	Claude (or another MCP client) reads and acts on your BoothRev context conversationally — find leads, check follow-up coverage, draft next steps, even create an event.	Any role, paid plans only
Importing leads	Bring a pre-registered attendee list or a post-event badge scanner file into BoothRev as leads, via CSV.	Event Owner+

Outbound — sending context out

Integration	What it does	Who
Connecting your CRM or enrichment tools	BoothRev connects out to your CRM or an enrichment provider’s MCP server, automatically pulling extra context onto a lead the moment they’re claimed.	Admin, paid plans only
Exporting leads	Hand off qualified leads to your CRM — Salesforce, HubSpot, SAP, or generic CSV — with the full field reference.	Event Owner+

How the two MCP directions relate

Connecting Claude is BoothRev acting as the server: Claude (the client) calls into BoothRev to read and act on your data.
Connecting your CRM or enrichment tools is BoothRev acting as the client: BoothRev calls out to a server your CRM or enrichment provider exposes.

They’re independent — you can use either, both, or neither. Both require a paid plan; neither is available on the Pilot. See pricing.