Skip to content
Discussion options

You must be logged in to vote

navigate_page itself does not return the raw PDF bytes. It performs the navigation and returns page state.

Current chrome-devtools-mcp has a separate network-response path:

  1. Navigate to the URL.
  2. Call list_network_requests, optionally filtering for document.
  3. Take the PDF request's reqid.
  4. Call get_network_request with that reqid and a responseFilePath.

For example:

get_network_request({
  reqid: 12,
  responseFilePath: C:/tmp/file.network-response
})

With responseFilePath, the implementation calls response.buffer() and saves the raw bytes. Without it, the response is formatted for the MCP result rather than being a reliable binary-download mechanism. You can rename the saved file to .pdf

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@JBetz
Comment options

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