Integration

Screendesk integration

Screendesk collects screen recordings from customers and support agents (bug reports, helpdesk tickets, live calls). List the recordings of the account, filtered by a helpdesk ticket or conversation id, read one recording with its customer, technical details and AI summary, rename it or edit its summary and description, download its video file, and read its timestamped transcript. Admins can also list the account's users and find a user by email. Account settings and SCIM provisioning are left out. API access requires the Screendesk Enterprise plan; authentication is a personal API token (Personal Settings, API Tokens) sent as a Bearer token in the Authorization header, with the same rights as the user who created it.

Connect Screendesk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Screendesk

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.

Recording, 4 operations

download_recordingDownload recordingGETDownloads the recording's video file (MP4, WebM or QuickTime) and returns it as a stored file: the edited version when one exists, else the processed one, else the original upload.
get_recordingGet recordingGETGets one recording by uuid: title, summary, description, metadata (duration, type, public url, helpdesk ticket), technical details, console logs, customer email, owning user and live-call insights.
list_recordingsList recordingsGETLists recordings, up to 100 per page (page param), returned in records[]. Members see only their own recordings, admins all of the account. Filter by a helpdesk ticket or conversation id with ticket_id (and provider).
update_recordingUpdate recordingPATCHUpdates a recording's title, summary and/or description (admin only); returns the updated recording. Send only the fields to change inside recording.

User, 2 operations

list_usersList usersGETLists the users of the Screendesk account with email, name, role (admin or member) and notification settings. Admin only.
search_userSearch userGETFinds one user of the account by exact email address and returns email, name, role, created_at and notification settings; answers 404 when no user has that email. Admin only.

Recording transcript, 1 operation

get_recording_transcriptGet recording transcriptGETGets the timestamped transcript of a recording (live calls included), up to 100 segments per page. Check status: processing means try again later, unavailable means there is none.

Use Screendesk from Claude Code, Cursor or Codex

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

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