LiveSession MCP server
10 operations0 webhooks
Session replay and product analytics API for listing recorded sessions, managing alerts and webhooks, and listing tracked websites.
Try LiveSession with your agent
Connect LiveSession, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in LiveSession on my account, then run one read-only example and show me the result.
LiveSession tools and triggers
Tools are what your agent can do in LiveSession through Corsair's MCP server. Triggers are the LiveSession events a routine can start from.
Alerts
- CreateWrite
Create an alert delivered to Slack or a webhook
alerts.create
- DeleteDestructive
Permanently delete an alert by ID
alerts.delete
- ListRead-only
List all alerts configured for the token scope
alerts.list
- UpdateWrite
Update an existing alert by ID
alerts.update
Webhooks
- CreateWrite
Create an outbound webhook for a website
webhooks.create
- DeleteDestructive
Permanently delete an outbound webhook by ID
webhooks.delete
- ListRead-only
List all outbound webhooks for the token scope
webhooks.list
- UpdateWrite
Update an outbound webhook by ID
webhooks.update
Sessions
- ListRead-only
List recorded sessions with page, size, visitor, email, timezone, and date filters
sessions.list
Websites
- ListRead-only
List all websites available to the token
websites.list
Connect LiveSession to Claude, ChatGPT or Cursor
- 1
Connect LiveSession in Corsair
Add your LiveSession API key once in Corsair. Corsair stores the credential encrypted and makes the LiveSession API calls for your agent, so it never goes into a prompt or a config file. Connect LiveSession
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs LiveSession. On a ChatGPT personal plan, connect LiveSession here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, LiveSession's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/livesession, add the LiveSession plugin, and connect with an API key. Then call methods like corsair.livesession.api.alerts.create() from your app. Corsair keeps each tenant isolated.
Yes. LiveSession requires an API key from your LiveSession account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit LiveSession, GitHub, Notion, Stripe, and the rest. Trigger LiveSession from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for session replay and product analytics API for listing recorded sessions, managing alerts and webhooks, and listing tracked websites. Common builds include sync jobs, admin tooling, and agents that call LiveSession APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per LiveSession API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/livesession in the open repo. When LiveSession ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your LiveSession data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store LiveSession data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put LiveSession on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive LiveSession operations. You can change a link's mode at hub.corsair.dev/me.