thrumeThe connection details.
Server URL: https://dash.thrume.app/mcp. Transport: Streamable HTTP. Authentication: OAuth with PKCE. Scope: recordings:read. Use the server URL as a remote MCP server, not a webpage or an API key. Client capabilities and account restrictions vary.
Start inside the Thrume web app.
Sign in to your approved Thrume account and open AI connections from the sidebar. Choose your client: Cursor and VS Code open their installation prompts; Codex and Claude Code provide setup commands; Claude provides guided connector instructions. The page includes configuration fallbacks and links to each client’s current setup guide.
Review the authorization.
Complete your client’s browser sign-in and confirm the account, workspace and evidence permissions shown by Thrume. Approve only a client you trust. Installation does not grant access by itself, and opening the MCP server URL in a browser does not connect an assistant. Organization policies may require a client administrator to enable custom connections.
Make the first request.
Copy the test prompt from AI connections and run it in your assistant. Review any tool-use approval your client requests; browser sign-in does not approve every tool call. Refresh status in Thrume: authorization appears first, and a verified first request appears only after the client contacts the MCP server. An empty library is valid. Then use a synthetic recording to check a screenshot or event around a known timestamp. Request verification does not certify the assistant’s reasoning.
Understand the access.
The connection can read recordings, available transcripts, screenshots and selected logs allowed by your account. It can also request generated frames and clips, which uses processing. The scope name does not mean every request is computationally free. Content sent to the client is handled under that client’s policies.
Recover an unconfirmed processing request.
If a frame or clip request reports that startup is unconfirmed, check its status first. In Thrume, open the recording and choose Check processing status, then Retry start if needed. In MCP, poll get_job; when dispatchPending is true, retry_job_start retries the saved request. Keep the same job ID. A failed status check does not prove that processing stopped.
If the connection fails.
Check that the client supports remote Streamable HTTP and OAuth, that you signed into the right approved account, and that you can open the recording in Thrume. Remove an outdated client connection and authorize again. Do not paste a sign-in code, session cookie or another person’s credentials into a config file.
Disconnect when you are done.
Open AI connections in Thrume, find the client and choose Revoke access. Remove its server configuration in your assistant if you no longer need it. To reconnect, repeat the client’s setup and sign-in. Revocation stops future authorized access; it cannot retract copies already exported to a client. Hosted transcription/summary settings are separate from external MCP consent.