Ask Claude about your engagement data.
Boxli is a Claude connector. Add it once, and any conversation with Claude can surface hot leads from your real telemetry, add contacts as you talk, tune your alert rules, and draft campaigns you describe — everything except sending, which stays in the app.
Connect in claude.ai
Add a custom connector
In claude.ai, open Settings → Connectors and click Add custom connector.
Paste the Boxli connector URL
https://app.sendaboxli.com/api/mcp/mcp
Sign in and allow
Claude sends you to Boxli to sign in (if you aren’t already) and shows a consent screen listing exactly what Claude can and cannot do. Click Allow access — done.
Using Claude Code instead?
One command: claude mcp add --transport http boxli https://app.sendaboxli.com/api/mcp/mcp, then run /mcp and choose Authenticate — the same sign-in and consent flow opens in your browser.
What Claude can see
🔍Search contacts
Find people by name, company, or email.
👤Contact summary
One contact’s full picture: watch counts, total attention, locations, their sends.
📈Engagement events
The chronological record — video watches with durations, QR / NFC scans, landing-page time, each in the recipient’s local timezone.
🔥Hot leads
Who engaged recently, with the evidence: event counts, watch seconds, places, last activity.
📦Send status
Delivery state and recent activity for any send.
➕Add contacts & companies
Paste a list, forward a signature block, or describe who to add — Claude creates the records.
🔔Alert control
Create, tune, or pause engagement alert rules — workspace-wide or for a single send.
🎯Campaign drafts
Describe the campaign you want — audience, message, which moments deserve alerts — and Claude drafts it in Boxli for your review.
Things to ask
- “Who are my hot Boxli leads right now, and what did they actually watch?”
- “Pull up Jane Doe in Boxli and tell me her engagement story.”
- “Add these five people from the conference to Boxli” (paste the list — Claude structures it).
- “Set up alerts so we hear about it the first time anyone watches, but at most once a day.”
- “Draft a Q4 renewal campaign in Boxli: top 20 accounts, thank-you message, alert us on any re-engagement.”
Claude reaches for the Boxli tools on its own when a question calls for them; saying "use Boxli to…" nudges it if needed. It gets even better combined with your other connectors — "cross-reference my hot Boxli leads against open HubSpot deals" joins your engagement telemetry with your CRM in one answer.
Access and security
- No boxes, no spend. Claude can read your data and create contacts, draft campaigns, and manage alert rules — but it cannot send boxes or spend credits. Sending stays in the app.
- Attributed and role-checked. Every change is attributed to the account that approved the connection, and admin-level actions (alerts, campaigns) require an owner or admin account.
- Workspace-scoped. The connection sees only the workspace of the account that approved it — enforced server-side on every request.
- Standard OAuth. You approve the connection on Boxli's own consent screen; credentials are never shared with Claude. Disconnect anytime from your Claude settings.
- Open protocol. The connector speaks MCP (Model Context Protocol), so it works with any MCP-capable client — claude.ai, Claude Code, and beyond.