Connect and sign in
Add that URL as a remote HTTP MCP server in your client. Approve the OAuth flow with the account that can view the relevant workspace. For Claude Code:captures:read. Write tools ask for an additional scope and still recheck workspace role and folder access. Keep the client endpoint exact; a mismatched resource URL can appear as a bare 401.
Investigate a capture
Start with the capture reference and request only the evidence needed:
Inspect capture CAPTURE_ID, find the failed request around the checkout error, and cite the console and network evidence that supports the diagnosis.
Tools include getDetails, getDiagnosis, getConsoleLogs, getNetworkRequests, getRequest, getEvents, getEnvironment, getFrames, getScreenshots, getVideoChapters, getSubtitles, listComments and searchCaptures. Use cursors for large event sets.
Share and write access
Clients that support custom headers can send the full share URL or token tail inmcp-capture-share for a bounded read. A Without DevTools share does not become diagnostic through MCP. Expiry, revocation and audience continue to apply.
Write tools can update captures, comments, reactions, folders, recording links, lifecycle state and integrations when the account has the required scope. Video analysis is an explicit request/poll workflow and its generated output is untrusted evidence. See MCP tools and authentication.