Integration

UXsniff integration

UXsniff is a website UX analytics tool (session recordings, heatmaps, feedback widget and on-site surveys). An agent can read the feedback visitors left (with visitor email and device context, which is personal data), list surveys and read their responses, list session recordings with links to watch them, list page heatmaps with their pageviews, and permanently delete one visitor's data for a privacy erasure request. The API is read-only apart from that deletion: surveys, widgets and settings are managed in the UXsniff dashboard. Authentication is the website API key from the UXsniff Account page, sent as is in the Authorization header (no Bearer prefix).

Connect UXsniff How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with UXsniff

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Feedback, 1 operation

list_feedbackList feedbackGETAgents: ask firstReturns the feedback visitors left through the UXsniff feedback widget on your website, with the question, comment, rating, page URL, screenshot and visitor context (including the visitor's email when given).

Heatmap, 1 operation

list_heatmapsList heatmapsGETAgents: ask firstReturns the heatmaps of your website keyed by page path, each with its pageviews count and a heatmap_link that opens the page with the UXsniff heatmap overlay.

Recording, 1 operation

list_recordingsList recordingsGETAgents: ask firstReturns the session recordings of your website, grouped by visitor (client_id_<id> keys) then by session (session_id_<id> keys), each with duration, clicks, device, country, referrer and a recording_link to watch it in UXsniff.

Survey, 1 operation

list_surveysList surveysGETAgents: ask firstReturns the surveys set up on your website, each with its survey_id (the id that list_survey_responses takes), its name and whether it is active.

Survey response, 1 operation

list_survey_responsesList survey responsesGETAgents: ask firstReturns the questions of one survey and the responses visitors gave to it (answers, page URL, country, browser, OS, referrer). Pass the survey_id from list_surveys as id.

Visitor data, 1 operation

delete_individualDelete individualPOSTAgents: ask firstPermanently deletes everything UXsniff holds about one visitor (a privacy erasure request), identified by its client_id. Cannot be undone.

Use UXsniff from Claude Code, Cursor or Codex

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

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