request_recording(ticket_id, prompt)
Ask the customer to record. Returns a video_id and the recording_url to send them.
MCP server · mcp.videosupport.io
Plug your own AI agent into VideoSupport through one MCP endpoint. It can ask a customer for a video mid-chat, read the transcript and visual triage, then answer with your tools, your rules and your voice.
request_recording(“HS-42”, “Show the router lights”)get_visual_triage(video_id)check_warrantyyour toolreply_to_customer(“HS-42”, …)How it works
VideoSupport handles capture, detection and the handoff to your team. Your agent handles the thinking, using the same tools and docs it already uses.
Mid-conversation, it calls request_recording and sends the customer a link. No app, no install.
Camera or screen, on any device. Live guidance helps them capture what support actually needs.
We transcribe the audio and detect the devices on screen and the likely issue, then hand it to your agent as structured data.
It runs your business logic, then replies or hands off to a human with the video, transcript and its notes attached.
Your agent → VideoSupport
Six tools, grouped by what your agent is doing. Every call is logged on the ticket.
request_recording(ticket_id, prompt)
Ask the customer to record. Returns a video_id and the recording_url to send them.
get_recording(video_id)
Status, playback and download links, duration, and whether the transcript and triage are ready.
get_transcript(video_id)
Everything the customer said, as full text plus timed segments.
get_visual_triage(video_id)
Devices on screen, the likely issue, possible causes and a summary, before your agent writes a word.
reply_to_customer(ticket_id, message)
Answer on the ticket. Replies land in your helpdesk, where your video tickets already live.
escalate_to_human(ticket_id, reason)
Hand off to your team with every video, transcript and triage on the ticket attached.
Get started
Create a workspace, plug the key into your agent, and run a sample conversation to see it work end to end.
Your workspace holds your tickets, videos and API keys. Tell us how customers will record.
Workspace created. Your API key is in the next step.
Your agent uses this key to connect. We only show it once, so copy it or download it now.
Pick your client and add the config below. After step 1, your key is filled in automatically.
So your agent can read new videos, VideoSupport needs to notify us when a customer records. Add this webhook URL in VideoSupport.
The URL contains a secret token. Treat it like a password.
Check the connection, then run a sample conversation. We play the customer, so you can watch each tool call your agent would make.
The sample creates a ticket named demo-… in your workspace with made-up video data.
FAQ
Any MCP-capable agent or client that supports remote (Streamable HTTP) servers: Claude, Cursor, VS Code, the OpenAI Agents SDK, LangChain, or your own code. Send your API key as Authorization: Bearer <key>.
Yes. Recordings are captured by VideoSupport, so you need either an API token or a public link from your account. Agent access through MCP is included on the Pro and Enterprise plans.
No. Recordings your own agent answers through MCP don't count against your monthly AI review allowance.
Call get_recording. Its status changes from requested to recorded, and transcript_status and visual_triage_status become ready when that data arrives.
Every reply and escalation is saved on the ticket. With a helpdesk bridge set up, they're also delivered to HubSpot, Intercom, Zendesk, Crisp or Monday.com, signed so your system can verify them. Talk to us to set that up.
Keys are stored hashed, so we can't show one again. Contact us and we'll issue a new key and revoke the old one.
Yes. Each API key only sees its own workspace's tickets and videos, and every action your agent takes is logged on the ticket.
Bring the agent you've already tuned on your docs and systems. We'll handle the video.
Get your API key