Skip to content
Discussion options

You must be logged in to vote

No dedicated download tool today, and navigate_page doesn't return file bytes. When a response is treated as a download (e.g. Content-Disposition: attachment), Chrome saves it through its own download handling and the MCP server doesn't report where it went, so don't rely on that path.

The reliable way to get the bytes out is through the Network tools:

  1. Open the URL with navigate_page (or new_page). For your PDF example the built-in viewer renders it, but the document request is still recorded.
  2. list_network_requests with resourceTypes: ["document"] (add includePreservedRequests: true if you've navigated since) and note the reqid of the file request.
  3. get_network_request with that reqid and r…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by JBetz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants