Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Clean raw HTML into LLM-ready text before agents spend tokens.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
APIFY_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"refinery": {
"command": "npx",
"args": [
"-y",
"@larelabs/refinery-mcp"
],
"env": {
"APIFY_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add refinery --env APIFY_TOKEN=your-value -- npx -y @larelabs/refinery-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"refinery": {
"command": "npx",
"args": [
"-y",
"@larelabs/refinery-mcp"
],
"env": {
"APIFY_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"refinery": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@larelabs/refinery-mcp"
],
"env": {
"APIFY_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account LareLabs, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: APIFY_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.6) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Clean HTML before your agent burns tokens.
Refinery MCP wraps the Refinery Apify Actor as an MCP server so Claude, Cursor, and other agents can turn raw HTML or URLs into clean LLM-ready text plus word_count.
flowchart LR
A[Agent needs web context] --> B[Fetch URL or raw HTML] B --> C[Refinery MCP] C --> D[Refinery Apify Actor] D --> E[Clean text + word_count] E --> F[RAG / embeddings / LLM context]
Agents are getting good at fetching web pages. The problem is what they fetch:
<html>
Home · Pricing · Login · Docs · Blog · Careers Subscribe to our newsletter
How ACME cut support ticket routing time by 63% ACME routes 40,000 monthly support tickets through an AI triage system. The team reduced retrieval noise by cleaning HTML before chunking.
Legal · Privacy · Cookie settings · LinkedIn · X
The model does not need most of that. It needs this:
How ACME cut support ticket routing time by 63%
ACME routes 40,000 monthly support tickets through an AI triage system. The team reduced retrieval noise by cleaning HTML before chunking.
Refinery MCP gives your agent a tool for that middle step:
fetch page -> refine HTML -> send clean text to RAG / embeddings / LLM
Agents can fetch pages, but raw HTML is noisy and expensive:
Refinery is the middle step your agent can call before it stuffs web context into a prompt:
fetch/render -> clean/refine -> chunk/embed/answer
It is not a crawler. Use Firecrawl, Crawl4AI, Playwright, browser automation, or your own fetcher when you need rendering. Use Refinery when you already have a URL or raw HTML and want a cheap cleanup pass before the LLM.
Use Refinery MCP when:
word_count / token-ish savings before embeddingDo not use it as your browser renderer, anti-bot layer, or site crawler.
clean_urlFetches a URL through the Refinery Apify Actor and returns dataset rows with clean text and metadata.
Example input:
{
"url": "https://docs.stripe.com/payments", "removeScripts": true, "removeStyles": true }
clean_htmlCleans raw HTML your agent, crawler, or browser session already fetched.
Example input:
{
"html": " Home Pricing Login Vendor security update We now support SOC 2 exports for enterprise accounts. Legal Privacy Careers ", "extractMentions": false, "extractHashtags": false }
Example result:
{
"text": "Vendor security update\n\nWe now support SOC 2 exports for enterprise accounts.", "word_count": 10, "content_type": "web", "language": "en", "processing_time_ms": 44.96, "success": true }
estimate_savingsLocal helper that compares raw HTML vs cleaned text and estimates token savings. This does not call Apify.
Example output:
{
"raw_chars": 168, "clean_chars": 41, "estimated_raw_tokens": 42, "estimated_clean_tokens": 11, "estimated_token_savings": 31, "reduction_pct": 76 }
npx -y @larelabs/refinery-mcp
Set your Apify token:
export APIFY_TOKEN=apify_api_xxx
export REFINERY_ACTOR_ID=larelabs/refinery-html-to-llm-cleaner
Use the published package:
{
"mcpServers": { "refinery": { "command": "npx", "args": ["-y", "@larelabs/refinery-mcp"], "env": { "APIFY_TOKEN": "apify_api_xxx", "REFINERY_ACTOR_ID": "larelabs/refinery-html-to-llm-cleaner" } } } }
Or run from source during development:
git clone https://github.com/LareLabs/refinery-mcp
cd refinery-mcp npm install npm run build
{
"mcpServers": { "refinery": { "command": "npm", "args": ["run", "dev", "--prefix", "/absolute/path/to/refinery-mcp"], "env": { "APIFY_TOKEN": "apify_api_xxx" } } } }
npm run build
APIFY_TOKEN=apify_api_xxx npm run smoke
The smoke test starts the MCP server over stdio, lists tools, and calls estimate_savings without spending Apify credits.
Use Refinery MCP to clean this docs page before summarizing it:
https://docs.stripe.com/payments
Return the clean text, word_count, and a short summary. Do not summarize raw HTML.
Another useful prompt:
I fetched this page HTML with Playwright. Use Refinery MCP clean_html before adding it to my RAG ingestion queue. Return the cleaned text and estimated token savings.
glama.json added — submit at https://glama.ai/mcp/servers)MIT