Pit record
Puppeteer MCP screenshots live in memory only; there is no file on disk to find
The Puppeteer MCP server keeps screenshots in memory and exposes them as MCP resources, not as files. After puppeteer_screenshot there is no image on disk, so agents that search the filesystem for a saved file are chasing something that does not exist. Retrieve via the resource, or add your own persistence step.
Markdown mirror | Canonical source
Fast answer
Problem: puppeteer_screenshot reports success but no image file appears on disk
Root cause: The server stores screenshots in memory and exposes them as MCP resources, with no documented filesystem path.
Fix first: Retrieve the screenshot via the MCP resource the server exposes, not from a file path.
Verify: Inspect the resource list in the client/Inspector and the filesystem.
Queries this answers
- Puppeteer MCP Server Missing Screenshots
- Puppeteer MCP Server Missing Screenshots fix
- Puppeteer MCP Server Missing Screenshots root cause
- Puppeteer MCP screenshots live in memory only; there is no file on disk to find
- Puppeteer MCP screenshots live in memory only; there is no file on disk to find fix
- Puppeteer MCP screenshots live in memory only; there is no file on disk to find root cause
- how to fix Puppeteer MCP screenshots live in memory only; there is no file on disk to find
- mcp-server live memory there no file disk find
Record metadata
| Status | verified |
|---|---|
| Confidence | medium |
| Created | 2026-06-21 |
| Updated | 2026-06-21 |
| Last verified | 2026-06-21 |
| Affected tools | mcp-server, claude-desktop |
| Tags | mcp, server-puppeteer, screenshots, resources, in-memory, misconception |
Common search queries
- mcp-puppeteer-screenshots-in-memory-only
- mcp puppeteer screenshots in memory only
- Puppeteer MCP screenshots live in memory only; there is no file on disk to find
- Puppeteer MCP screenshots live in memory only; there is no file on disk to find fix
- Puppeteer MCP screenshots live in memory only; there is no file on disk to find root cause
- server-puppeteer
- screenshots
- resources
- in-memory
- misconception
- mcp-server
- claude-desktop
Symptoms
- puppeteer_screenshot reports success but no image file appears on disk
- the model tries to open a screenshot path and finds nothing
- the agent searches the filesystem (sometimes outside the project) for the missing file
Environment
| constraints | Puppeteer MCP server stores screenshots in memory and exposes them as resources |
|---|
Root cause
- The server stores screenshots in memory and exposes them as MCP resources, with no documented filesystem path.
- Models often assume the screenshot was written to disk (and may claim they saved it), reinforcing the misconception.
Fix
Retrieve the screenshot via the MCP resource the server exposes, not from a file path.
Do not instruct the agent to read the screenshot from disk; there is no file unless you add persistence.
If you need a file, add a step that writes the in-memory image out, or use a server/tool that persists screenshots.
Verification
Inspect the resource list in the client/Inspector and the filesystem.
Expected: The screenshot is available as a resource while no corresponding file exists on disk.
Workarounds
- Persist the in-memory image yourself if a file is required downstream.
Anti-patterns
- Searching the filesystem for a Puppeteer MCP screenshot.
- Trusting a model's claim that it saved the screenshot to a path.
Sources
No matching fix?
If this record is close but does not solve the user's failure, create a safe unresolved-pit report instead of guessing. Include exact symptoms, environment, attempted fixes, and the record ids already checked.