LeadBoxer
Lead generation platform that gives you real-time info about companies and people that visit your website. Turning anonymous web traffic into actionable data.
Verdict
Common use cases
- Score inbound leads during morning standup
- Tag high-intent visitors after demo calls
- Pull session history before sales outreach
- Log backend conversions from Slack threads
- Audit lead scoring formulas across datasets
Integration
- Vendor
- LeadBoxer
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 9
- Composio slug
leadboxer
Tools
- Add or Update Lead Tags
Tool to add or update lead tags in LeadBoxer. Use when you need to manage lead tags by adding new tags, removing specific tags, or overwriting all existing tags for a specified user.
- Delete Custom Tracking Domaindestructive
Tool to delete a custom tracking domain entry for a dataset. Use when you need to remove a specific custom tracking domain (CTD) associated with a dataset in LeadBoxer.
- Get Custom Tracking Domains
Tool to fetch custom tracking domain entries for a dataset. Use when you need to retrieve all custom tracking domains that are created or in progress for a specific datasetId.
- Get Events
Tool to fetch events for specified sessions from LeadBoxer. Use when you need to retrieve behavioral data including pageviews, clicks, form submissions, email interactions, and custom events. Events can be filtered by session ID, email, use
- Get Lead Detail
Tool to fetch detailed information about a lead based on filters. Use when you need comprehensive lead data for a specific lead ID. The default view type is B2B. Note: On initial pageview, there may be a few seconds overhead before data is
- Get Lead Score Formula
Tool to fetch the lead score formula for a specific dataset. Use when you need to understand how lead scores are calculated for records in a dataset. The formula defines scoring based on criteria types: Range (number ranges), Match (exact v
- Get Sessions
Tool to fetch sessions for a specified lead ID from LeadBoxer. Use when you need to retrieve session data for a user, with optional filtering by email, user ID, Smartlist ID, or segment ID. A session represents a single visit to the site, a
- Log Server-Side Event
Tool to track server-side events in LeadBoxer. Use when tracking backend events, page views, or custom activities from your server. This endpoint supports tracking user interactions, conversions, and other activities that occur on the serve
- Post Event Data
Tool to send event data for tracking user activities via POST request. Use when tracking events by sending data in the request body with application/x-www-form-urlencoded format.
Setup
Setup guide
- 11. In Switchy, open Settings and navigate to the Integrations tab. 2. Search for LeadBoxer and click Connect. 3. Paste your LeadBoxer API key (find it under Account Settings → API in your LeadBoxer dashboard). 4. Enter your dataset ID, which appears in the LeadBoxer URL when you view a dataset. 5. Click Save to authorize the connection. 6. Open any Space and type '@LeadBoxer get lead detail' followed by a lead ID to test retrieval. 7. If the response includes session counts and tags, the connection is live. 8. Use '@LeadBoxer' at the start of any prompt to invoke tools like tagging leads, fetching events, or logging server-side activity.
What teammates see: by default, memories from LeadBoxer are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Qualify Top Leads
@LeadBoxer get lead detail for the five highest-scoring leads in dataset 12345 from the past week, including session counts and tags.Open in a Space →
Tag Demo Attendees
@LeadBoxer add the tag 'demo-attended' to leads with IDs abc123, def456, and ghi789 in dataset 12345.Open in a Space →
Review Scoring Logic
@LeadBoxer get the lead score formula for dataset 12345 and summarize the criteria and point values.Open in a Space →
Pull Session Timeline
@LeadBoxer get sessions for lead ID abc123 in dataset 12345, ordered by most recent first.Open in a Space →
Log Backend Event
@LeadBoxer log a server-side event named 'trial-started' for user email user@example.com in dataset 12345 with metadata plan:pro.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@LeadBoxer show me the lead score formula for our main dataset and explain which activities contribute most to qualification
The lead score formula for dataset ds_abc123 assigns points as follows: Email opens = 5 points, form submissions = 25 points, pricing page views = 15 points, demo requests = 50 points, and return visits within 7 days = 10 points. Based on this configuration, demo requests and form submissions are your highest-value qualification signals. Leads scoring above 75 points (typically 2+ high-value actions) enter your 'hot lead' segment automatically. The formula was last updated 14 days ago.
This example shows LeadBoxer's scoring transparency—useful when sales and marketing need to align on what 'qualified' means. Requires read access to dataset configuration. Note that changing the formula itself requires admin permissions and isn't available through this MCP.
@LeadBoxer add tags 'enterprise-interest' and 'Q1-2024-campaign' to lead ID lead_xyz789, then confirm the update
Successfully added 2 tags to lead lead_xyz789. The lead now has tags: ['enterprise-interest', 'Q1-2024-campaign', 'product-qualified', 'north-america']. The first two tags were newly added; the latter two were already present. This lead's tag set was last modified 3 minutes ago. Tag changes are immediately visible in LeadBoxer dashboards and will affect any Smartlist filters that reference these tags.
Demonstrates write operations for lead segmentation. This is additive tagging—existing tags remain unless you explicitly use the 'overwrite' mode. Useful for automated lead routing workflows, but be cautious: incorrect tagging can misroute high-value leads. API key must have write permissions.
@LeadBoxer pull the last 30 days of sessions for lead ID lead_abc456, then summarize their engagement pattern and identify their primary interest areas
Lead lead_abc456 has 12 sessions over the past 30 days, with 8 sessions in the last week showing increased engagement. Session analysis reveals: 67% of pageviews focused on your API documentation and developer guides, 4 visits to the enterprise pricing page (avg. 3.2 minutes each), and 2 form submissions for technical whitepapers. The lead accessed your site primarily during US business hours (9am-5pm EST) from a corporate IP range. This pattern suggests a technical evaluator researching integration requirements before a potential enterprise purchase decision.
Showcases the MCP's ability to retrieve behavioral data and pair it with AI reasoning for lead intelligence. Sessions include pageviews, clicks, and form events—helpful for understanding buyer intent. Be aware that session data volume can be large for highly active leads; consider date-range filtering to manage response size.
Use-case deep-dives
When LeadBoxer bridges marketing signal to sales context
A 6-person B2B SaaS team runs HubSpot for email campaigns but needs richer behavioral data before sales calls. LeadBoxer's Get Lead Detail and Get Sessions tools pull pageview sequences, form submissions, and email clicks into a single lead profile. The MCP lets your AI assistant surface "this lead visited pricing 4 times in 48 hours" without opening the LeadBoxer dashboard. This works when your sales cycle is short (under 30 days) and you're tracking under 500 active leads per month—beyond that, the manual tagging overhead (Add or Update Lead Tags) becomes a bottleneck. If your team already lives in a CRM with native event tracking, LeadBoxer adds complexity. Use this MCP when you need to enrich existing marketing automation with session-level detail for a small, high-touch sales motion.
Score trial users by backend activity, not just pageviews
A 3-person product team at a developer tool startup tracks trial signups but can't tell which users are actually integrating the API versus just browsing docs. LeadBoxer's Log Server-Side Event tool sends backend events (API key created, first request, webhook configured) alongside frontend pageviews. The Get Lead Score Formula tool shows how these events weight into a composite score. Your AI assistant queries Get Events to answer "which trial users hit the integration milestone this week?" in Slack. This setup breaks down if your product generates more than 10k events per day—LeadBoxer's pricing jumps and query latency climbs. It's the right call when you need lightweight event scoring without building a data warehouse, and your trial volume is under 200 signups per month.
Route support tickets by account engagement history
A 5-person support team at a SaaS company uses Zendesk but has no visibility into which accounts are actively using the product versus churning. LeadBoxer's Get Sessions and Get Lead Detail tools pull recent activity (last login, feature usage, support doc views) into the ticket context. The AI assistant tags high-priority tickets when a lead's session count drops 50% week-over-week or when they visit the cancellation page. This works for teams handling under 100 tickets per week with a defined set of engagement signals (pricing page, help docs, feature pages). If your support volume is higher or your product has dozens of features to track, the 9-tool MCP becomes too narrow—you'll need a full analytics platform. Use LeadBoxer here when support needs lightweight engagement context without analyst overhead.
Frequently asked
What does the LeadBoxer MCP do in Switchy?
It lets your AI agents read lead data, session history, and behavioral events from LeadBoxer, plus write server-side events and manage lead tags. You can ask questions like 'show me high-scoring leads from last week' or 'tag this lead as qualified' without opening the LeadBoxer dashboard. The MCP surfaces pageviews, form submissions, email interactions, and custom events your team has already tracked.
Do I need admin access to connect LeadBoxer?
You need an API key from your LeadBoxer account. LeadBoxer doesn't use OAuth, so whoever has access to generate API keys in your workspace can connect it. The key grants full read/write access to leads, sessions, events, and custom tracking domains for the datasets you specify. Check with your LeadBoxer admin if you're unsure who controls API key creation.
Can the MCP create new leads or only read existing ones?
It can log server-side events and update lead tags, but it doesn't create leads from scratch. Leads are created when LeadBoxer's tracking pixel fires on your site or when you import them via CSV. The MCP's 'Log Server-Side Event' tool lets you track backend conversions or custom activities that tie to existing leads, and you can add or remove tags to segment them.
How is this different from using LeadBoxer's API directly?
The MCP wraps nine of LeadBoxer's most-used endpoints so your AI agents can query and update lead data in natural language. You skip writing API calls, handling pagination, and parsing JSON responses. If you need bulk exports or webhook configuration, you'll still use LeadBoxer's full API or dashboard. The MCP is for conversational, on-demand access to lead intelligence.
Who on the team should connect this MCP?
Whoever owns your lead qualification workflow—usually a sales ops lead or marketing ops manager. They'll know which datasets matter and can decide if agents should tag leads or just read session data. The API key grants access to all datasets, so connect it in a Switchy workspace where only trusted team members can prompt the AI.