[Feature Request] MCP Chrome: Add screenshot save-to-file action and quality control

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

---

Problem Statement

Who: Developers using Claude Code with MCP Chrome browser automation for QA, testing, and documentation workflows.

What: When using the computer tool's screenshot action in MCP Chrome, there is no way to:

1. Save the captured screenshot as a local file
2. Control the screenshot quality (currently compressed to ~50% JPEG)

When: During browser automation workflows that require sharing visual evidence with external systems.

Where: MCP Chrome extension's computer tool / mcp__claude-in-chrome__computer

Why this is needed:

I was automating Jenkins CI test result verification and needed to attach the screenshot to a JIRA issue as evidence. The workflow should be simple:

1. Navigate to Jenkins → Take screenshot → Upload to JIRA

However, I discovered:

• Claude can see the screenshot (via Vision)
• Claude cannot save it as a file
• The only workaround is extracting base64 data from ~/.claude/projects/*/*.jsonl transcript files - which is hacky and unreliable
• Screenshot quality is ~50% JPEG (measured: 60KB for 1535x800 = 0.049 bytes/pixel), making text hard to read

Real-world use cases blocked by this limitation:

• Uploading test failure screenshots to JIRA/GitHub Issues
• Attaching visual bug reports to ticketing systems
• Documenting UI states in Wiki/Confluence
• Sharing browser state via Slack/Email
• Creating visual test evidence for QA workflows

---

Proposed Solution

Option A: Add save action to computer tool

{
  "action": "save_screenshot",
  "imageId": "ss_abc123",
  "output_path": "/tmp/screenshot.png",
  "quality": 90
}

Option B: Add download parameter to screenshot action

{
  "action": "screenshot",
  "save_to": "/tmp/screenshot.png",
  "format": "png",
  "quality": 100
}

Option C: Add quality option to existing gif_creator's export
The gif_creator tool already supports download: true. Similar functionality for single screenshots would be consistent.

---

Alternative Solutions

Current workaround I built (not ideal):

1. Take screenshot with MCP Chrome
2. Parse JSONL transcript file to find base64 data at .toolUseResult[].source.data
3. Decode base64 and save to file
4. Upload to external system

This is fragile because:

• Depends on internal JSONL structure
• Session ID must be known
• Multiple screenshots require manual imageId tracking
• Quality is already degraded before extraction

---

Priority

Medium-High - Blocks common automation workflows involving visual documentation

---

Feature Category

Browser automation / MCP tools

---

Additional Context

• Environment: macOS, Claude Code 2.x, MCP Chrome Extension 1.0.40
• Related issue: #16592 (Expose pasted image data to hooks and plugins) - similar problem for pasted images
• The upload_image tool exists for uploading TO pages, but no equivalent for downloading/saving FROM the extension