fullpageshot-mcp
Drives a Brave browser instance via the Chrome DevTools Protocol to open URLs, take full-page screenshots, read saved screenshots back as images, close the browser, and report browser status, with headless background capture by default.
Drives Google Chrome via the Chrome DevTools Protocol to open URLs, capture full-page screenshots, read saved screenshots back as images, close the browser, and report browser status, with headless background capture by default.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fullpageshot-mcp screenshot https://en.wikipedia.org/wiki/Web_browser and read it back to me"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fullpageshot-mcp
An MCP server that gives an agent the ability to:
open a website (
open_url)take a screenshot of it (
screenshot) — full-page by defaultread the screenshot back as an image (
read_screenshot)
Capture runs in the background by default (headless Chromium), so it needs no open window and no browser extension. It drives a Chromium-based browser you already have via the Chrome DevTools Protocol — zero npm dependencies.
Companion to the FullPageShot browser extension. The extension is for humans clicking the toolbar; this server is for agents and scripts.
Requirements
Node.js | >= 22 (uses the built-in |
Browser | Any Chromium-based browser: Google Chrome, Brave, Chromium, Microsoft Edge |
OS | macOS, Linux, Windows |
Dependencies | none |
The server finds a browser automatically. Override with FULLPAGESHOT_CHROME=/path/to/browser.
Related MCP server: Browser Intelligence MCP
Install
git clone https://github.com/TanasiDesigns/fullpageshot-mcp
cd fullpageshot-mcp
node src/server.mjs --version # sanity check, no install step neededOr run it straight from a checkout in any MCP client config (below). No npm install is required.
Add it to an MCP client
Generic stdio configuration (Claude Desktop, Cursor, Cline, Continue, pi, etc.):
{
"mcpServers": {
"fullpageshot": {
"command": "node",
"args": ["/absolute/path/to/fullpageshot-mcp/src/server.mjs"]
}
}
}With the optional bin link:
{
"mcpServers": {
"fullpageshot": { "command": "fullpageshot-mcp" }
}
}Tools
Tool | What it does |
| Navigate to a URL. |
| Capture the current page, or a |
| Read a saved screenshot file back as image content. |
| Shut the browser down and remove its throwaway profile. |
| Show running/headless/version/output-dir state. |
Example agent prompts
"Open
https://example.comand screenshot it.""Take a full-page screenshot of
https://en.wikipedia.org/wiki/Web_browserand tell me what the infobox says.""Screenshot
https://stripe.com/pricingat 1440×900 and read it back.""Capture
https://github.comand crop-check the footer." (capture, thenread_screenshot)
Background capture
Capture is headless by default (--headless=new) so it works with no visible window:
screenshot({ url, headless: true })→ background, no window.open_url({ url, headless: false })→ visible window (useful for debugging).Env
FULLPAGESHOT_HEADLESS=0forces a visible window for every call.
Each run uses a throwaway profile under the system temp dir, so it never touches your real browser profile or logins.
Configuration
Env var | Default | Meaning |
| auto-detected | Path to the browser binary. |
|
|
|
| temp dir | Where screenshots are saved. |
How it works
MCP stdio -> fullpageshot-mcp -> launches Chromium (headless)
-> CDP over WebSocket
Target.createTarget
Page.navigate
Page.getLayoutMetrics
Page.captureScreenshot{captureBeyondViewport}
-> PNG on disk + base64 image back to the agentFull-page capture uses captureBeyondViewport with a clip sized to the page's content, scaled down if it would exceed the 16384 px screenshot ceiling. screenshot also scrolls the page once (settle) to trigger lazy-loaded content before measuring.
Security & privacy
Runs entirely locally. No telemetry, no accounts, no network calls except the pages you ask it to open.
Never attaches to your everyday browser or its profile — it launches a separate throwaway instance.
The only "remote control" surface is the browser it starts itself.
Compatibility
Tested with Brave 154.0.8037.93 (Chromium 154) on macOS, headless. The CDP methods used (Target.*, Page.navigate, Page.getLayoutMetrics, Page.captureScreenshot) are long-stable and supported by Chromium 100+; Chrome/Brave/Edge/Chromium all work.
License
MIT — see LICENSE. Do whatever you want with it: use, modify, fork, sell, ship in your own product. Just keep the copyright notice.
Available Tools
5 toolsbrowser_statusA
Report whether the browser is running, whether it is headless, its version, and the screenshot output directory.
Inputs: no named parameters.
close_browserA
Shut down the controlled browser and clean up its temporary profile.
Inputs: no named parameters.
open_urlB
Open a website in a controlled Chromium browser. Runs headless (background) by default; set headless=false for a visible window.
Inputs: url (required), width, height, settle, +2 more.
read_screenshotA
Read a previously saved screenshot file back as image content.
Inputs: path (required).
screenshotA
Capture a full-page screenshot (default) of the current page or of a URL. Saves a PNG/JPEG/WebP to disk and returns the image so it can be read.
Inputs: url, path, read, maxPx, +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct action on the controlled browser: open, capture, read file, close, and report status. The only mild overlap is that screenshot can accept a URL directly, which slightly blurs the line with open_url, but otherwise the boundaries are clear.
Most tools follow a verb_noun pattern (open_url, read_screenshot, close_browser) which is consistent and readable. screenshot and browser_status deviate (noun-only), but the set is still predictable.
Five tools is a snug, well-scoped set for a headless-browser screenshot server, covering the core lifecycle without bloat. It sits at the lower end but each tool earns its place.
The browser lifecycle is well covered: open, capture, read back, close, and status. Minor gaps like page interaction (click, scroll, navigate) exist, but for a screenshot-focused purpose the surface is essentially complete.
Maintenance
Related MCP Connectors
Give your agent eyes: screenshots of any web page it can see, pages as markdown, and PDFs.
Hosted browser for agents: open pages, search the web, extract data, read PDFs and take screenshots.
Capture website screenshots, run bulk captures, and manage screenshot schedules and history.
Capture websites as PNG, JPEG, WebP or PDF, extract their content, or analyse them with AI.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables agents to take screenshots and extract text from web pages using a persistent Chrome browser via CDP, with built-in SSRF protection.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to capture screenshots, scrape structured page content, and run automated visual checks on live websites via a headless Chromium browser.3MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to capture web pages or render HTML as images or PDFs, with screenshots returned inline to the assistant.343 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to open and navigate sites on emulated phones, tablets, and desktops through a connected browser extension, capture transparent PNG screenshots, and render device-emulated screenshots headlessly with Playwright.MIT