Integration

LeadBoxer integration

LeadBoxer identifies the companies and people visiting your website and scores them as leads. List and filter a dataset's leads, read one lead with its sessions and events, enrich an email address, an IP address or a domain into company and contact data, manage segments (saved lead filters with email notifications), tag and assign leads, and hide leads with exclusion rules. Account administration (users, datasets, form tracking, custom tracking domains, credit reports, the account-level user-dataset grants), the CSV export and the default-segment routes (the live host answers 404 on them) are not exposed. Authentication is an API key sent in the x-api-key header; limits are per account and per endpoint, per minute (30 for list_leads and lookup_email, 100 for lookup_ip and lookup_domain).

Connect LeadBoxer How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in LeadBoxer.Built from the 18 LeadBoxer tools below, on the connection you add once.

What you can do with LeadBoxer

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Segment, 5 operations

create_segmentCreate segmentPOSTCreate a segment (saved lead filter) in a dataset: name, type (USER or ACCOUNT visibility), filters in the same format as list_leads, and optional email notifications. Returns its id.
delete_segmentDelete segmentDELETEDelete a segment by its segmentId (smartlistId from list_segments).
list_segmentsList segmentsGETList the segments (saved lead filters) of a dataset for your user. Each segment's smartlistId is the segmentId the other segment tools take.
update_segmentUpdate segmentPUTUpdate a segment's filters, visibility and notification settings (segmentName in the query; emailView and notificationType are required).
update_segment_userUpdate segment userPUTChange the user associated with a segment, which gives that user access to it.

Lead, 4 operations

assign_leadAssign leadPUTAssign a lead (leadId = use_id from list_leads) to a LeadBoxer user (assignee = user ID).
get_leadGet leadGETGet one lead by its use_id (from list_leads): contact data, company enrichment, score, visit metrics, last visit and geolocation.
list_leadsList leadsGETList a dataset's leads (site from list_datasets). timeField and criteriaTimeFilter are required, for example eventEsTimestamp with eventEsTimestamp|lessthan|6 for the last 7 days. Page with metaData.nextToken.
update_lead_tagsUpdate lead tagsPUTAdd or remove tags on a lead (leadId = use_id from list_leads) in a dataset.

Lead exclusion, 3 operations

hide_leadsHide leadsPOSTHide leads in a dataset with an exclusion rule: type (use_id, organizationName, organizationDomain or last_most_likely_company) and the value to exclude in data.
list_lead_exclusionsList lead exclusionsGETList the exclusion rules that hide leads in a dataset, optionally for one type (use_id, organizationName, organizationDomain, last_most_likely_company).
unhide_leadsUnhide leadsDELETERemove an exclusion rule so the matching leads show again: same datasetId, type and data as when hide_leads created it.

Contact, 1 operation

lookup_emailLookup emailPOSTEnrich an email address into a professional profile (name, headline, LinkedIn, seniority, job function, location, experience). Name and company are optional matching hints. Credits are consumed only when a profile is found.

Dataset, 1 operation

list_datasetsList datasetsGETList the datasets (tracked sites) your user can access. Each datasetId is the site or datasetId the lead, segment and exclusion tools take.

Event, 1 operation

list_session_eventsList session eventsGETList the events (pageviews, clicks, form submits...) of one session (sessionId, for example a lead's last_session_id); limit is required (1 to 100).

Ip address, 1 operation

lookup_ipLookup ipGETLook up an IPv4 or IPv6 address: organization, geolocation, ISP and network details. Credits are charged to datasetId when given, else to a dataset linked to the account.

Organization, 1 operation

lookup_domainLookup domainGETLook up a company by domain (a clean domain such as leadboxer.com, no protocol or www): name, type, industry, employee range, address, LinkedIn, specialties.

Session, 1 operation

list_lead_sessionsList lead sessionsGETList the website sessions of one lead (leadId = use_id from list_leads); limit is required (1 to 10000). Filter by segment or minimum duration; page with nextToken.

Use LeadBoxer from Claude Code, Cursor or Codex

Connect LeadBoxer in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its LeadBoxer operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect LeadBoxer

Create your workspace
Sign up free. Nothing to install.
Connect LeadBoxer once
Add your LeadBoxer connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.