browse_webpage
Extract content from a webpage with optional CSS selectors for specific elements
LABSCO SUMMARY
Selectors decide what the model reads, so a long page costs a paragraph.
The selectors parameter is the whole argument for it: without one the page comes back whole, with one only the matched elements do. That makes it a fit for pages whose structure you already know, since the tool takes selectors rather than working out which part mattered.
What it is
A single-tool page extractor: a url, plus optional CSS selectors naming the elements worth returning.
What you get
- browse_webpage returning the content of a page at a url
- Selectors narrowing that to matched elements, so a table or an article body arrives without the navigation and footer wrapped around it
Requirements
Nothing to supply — no account, no key; a URL the machine can reach, and the selectors for the part you want. MIT licensed.
Setup effort
One command — uvx web-browser-mcp-server
USE CASES
01
Pulling one section out of a page you already know
Give the URL and the selector for the part that matters — a pricing table, a changelog list — and the rest of the document never enters the conversation.
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
uvx 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": {
"web-browser-mcp-server": {
"command": "uvx",
"args": [
"web-browser-mcp-server"
]
}
}
}uvx
TERMINAL
uvx web-browser-mcp-server
