Enables AI agents and LLMs to interact with the web and extract information from web pages via the RAG Web Browser Actor.
Connect Rag Web Browser to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Enables AI agents and LLMs to interact with the web and extract information from web pages via the RAG Web Browser Actor. The rag web browser mcp server is what makes that connection.
Implementation of an MCP server for the RAG Web Browser Actor. This Actor serves as a web browser for large language models (LLMs) and RAG pipelines, similar to a web search in ChatGPT.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
name — searchraw-http — Fast (no JS execution) – good for static pagesbrowser-playwright — Handles JS-heavy sites – slower, more robustTools — The Tools tool exposed by this serverPrerequisites — Clone & install: bash git clone https://github.com/apify/mcp-server-rag-web-browser.git cd mcp-server-rag-web-browser npm installBuild — The Build tool exposed by this serverDebugging — Since MCP servers operate over standard input/output (stdio), debugging can be challenging. For the best debugging experience, use the [MCPBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: APIFY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
APIFY_TOKEN) Clone & install:Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Rag Web Browser's toolset — name, raw-http, browser-playwright and 4 more — is a fair guide to whether it matches your workflow. It is maintained by apify; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| name | search |
| raw-http | Fast (no JS execution) – good for static pages. |
| browser-playwright | Handles JS-heavy sites – slower, more robust. |
| Tools | The Tools tool exposed by this server. |
| Prerequisites | Clone & install: bash git clone https://github.com/apify/mcp-server-rag-web-browser.git cd mcp-server-rag-web-browser npm install |
| Build | The Build tool exposed by this server. |
| Debugging | Since MCP servers operate over standard input/output (stdio), debugging can be challenging. For the best debugging experience, use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
{
"mcpServers": {
"rag-web-browser": {
"command": "npx",
"args": ["@apify/mcp-server-rag-web-browser"],
"env": {
"APIFY_TOKEN": "your-apify-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
APIFY_TOKEN) Clone & install:| Variable | Description | Required |
|---|---|---|
| APIFY_TOKEN | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.