fetchpage
Fetch web pages using browser automation with full JavaScript rendering. Supports automatic cookie management, localStorage, CSS selectors, and dynamic content. Cookies are automatically loaded from local storage if available.
LABSCO SUMMARY
One tool, and the reason to reach for it over a plain fetch is the cookie store: it reuses a session you already have instead of asking you to supply one.
Everything else follows from running a real browser — scripts execute, localStorage is available, and waitFor lets the caller name a CSS selector to block on rather than guess at a delay. There is no extraction beyond that wait, so what comes back is the page itself and not a parsed subset of it; anything narrower is work for whatever reads the result.
What it is
A single-tool page fetcher that drives browser automation instead of issuing an HTTP request, so a page whose content arrives by script comes back rendered.
What you get
- fetchpage loads the url with full JavaScript rendering, so dynamic content is present in what returns rather than missing from the markup.
- waitFor takes a CSS selector and timeout bounds the wait, so the page is read once the part you care about has appeared.
- Cookies load automatically from local storage where they exist, and localStorage is supported, so a page depending on a session you already hold still returns content.
- CSS selectors and dynamic content are handled by the same call, so the page that comes back is the one a browser would have shown.
Requirements
Nothing to supply but the url. A page that depends on being signed in relies on cookies already sitting in local storage, since that is where this tool loads them from.
Setup effort
One command — npx -y mcp-fetch-page@latest
USE CASES
01
Reading a page that is empty until its JavaScript runs
Load it in a real browser and wait on the selector that marks the content as present before taking the result.
02
Fetching a page that only loads when you are signed in
Reuse the cookies already stored locally so the page returns its signed-in content rather than a login screen.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-fetch-page": {
"command": "npx",
"args": [
"-y",
"mcp-fetch-page@latest"
]
}
}
}npx
TERMINAL
npx -y mcp-fetch-page@latest
