Integration

LiveSession integration

LiveSession records website visitor sessions for replay and product analytics. List the recorded sessions of a website (filter by identified visitor email, visitor id and date range, with duration, pages, device, browser, UTM data and click and error statistics), list and add tracked websites, and manage alerts (event-based notifications sent to Slack or to a webhook) and the webhook endpoints they deliver to. Visitor IP addresses, visitor geolocation, the dashboard replay link of each session, webhook endpoint URLs and the webhook creator are not returned. Funnels, metrics, dashboards, the GraphQL API and the browser SDK are not exposed. Authentication is a Personal Access Token created in LiveSession settings (API Tokens), scoped to one website and to chosen scopes (users.sessions:read, websites, alerts, webhooks read or write), sent as a Bearer token. Each token is limited to 2 requests per second.

Connect LiveSession How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with LiveSession

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.

Alert, 4 operations

create_alertCreate alertPOSTCreates an alert that sends a real notification to a Slack channel or a webhook each time one of its events happens on the website. Needs the alerts:write scope.
delete_alertDelete alertDELETEDeletes an alert for good: its notifications stop. Returns the alert_id and deleted=true. Needs the alerts:write scope.
list_alertsList alertsGETLists every alert of the account with its events, provider (slack or webhooks), target Slack channel or webhook id and enabled state. Needs the alerts:read scope.
update_alertUpdate alertPUTChanges an alert (name, events, provider, target). The docs do not say whether left-out fields are kept: read it with list_alerts and send every field back with your change. Needs alerts:write.

Webhook, 4 operations

create_webhookCreate webhookPOSTRegisters a webhook endpoint for a website; alerts with provider webhooks then POST real JSON events to it. Needs webhooks:write and an Admin or Owner role.
delete_webhookDelete webhookDELETEDeletes a webhook endpoint for good: alerts using it stop delivering there. Returns webhook_id and deleted=true. Needs the webhooks:write scope.
list_webhooksList webhooksGETLists the webhook endpoints of the account with their id, website, API version and enabled state (endpoint URLs are not returned). Needs the webhooks:read scope.
update_webhookUpdate webhookPUTReplaces a webhook endpoint's URL and website. Both are required by LiveSession on every update, so pass the website_id from list_webhooks when only the URL changes. Needs webhooks:write.

Website, 2 operations

create_websiteCreate websitePOSTAdds a website to track in the LiveSession account and returns its website_id and host. Needs the websites:write scope.
list_websitesList websitesGETLists the websites tracked by the account with their website_id and host. Use the website_id with create_webhook. Needs the websites:read scope.

Session, 1 operation

list_sessionsList sessionsGETLists recorded sessions, up to 100 per page (page and size). Filter by visitor email, visitor_id or a date range. Needs the users.sessions:read scope.

Use LiveSession from Claude Code, Cursor or Codex

Connect LiveSession in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its LiveSession 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 LiveSession

Create your workspace
Sign up free. Nothing to install.
Connect LiveSession once
Add your LiveSession 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.