Allow setting the location of the temporary screenshot file

[james2doyle]

Is your feature request related to a problem? Please describe.
The problem is that other tools may not have access to the location that the screenshot is being saved. I want the location to be predictable and consistent so that other tools can pick up that temporary file and use them.

Describe the solution you'd like
A new argument for take_screenshot that allows you to set the path for the output

Describe alternatives you've considered
An alternative would be to be able to force call to take_screenshot to return a base64 string instead of writing a file

Additional context
This would allow other MCPs to take action on this file or allow other tools in a chain to find the screenshots and use them

[OrKoN]

I think it makes sense to have this. What we currently do:

1. if the image is less than 2 MB we return it as an image content according to the MCP.
2. if it is larger than 2 MB, we save it to a tmp file.

Generally, the tmp folder should be accessible but I imagine in some setups the client/other tools might lack permission.

[james2doyle]

Thanks for the support.

I’m actually using the devtools mcp to create bug tickets for issues it finds. The problem I’m facing is that the MCP for my bug tracking tool always requires an image path for attaching files to bug tickets. Since I can’t force an image file output, that step can fail when the image is base64.