holoscrape-mcp
Click on "Install 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., "@holoscrape-mcpExtract the list of items from the current tab into a table."
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.
holoscrape-mcp
Give an AI agent your own logged-in browser. This runs locally, does not upload anything, and never sees your passwords — the HoloScrape Chrome extension does the actual reading, in your own signed-in Chrome, and this process is only the bridge that lets an MCP-speaking agent (Claude Code, Claude Desktop, Cursor, Windsurf) ask it to.
Use it
You do not install this — your agent's MCP config runs it on demand:
{
"mcpServers": {
"holoscrape": { "command": "npx", "args": ["-y", "holoscrape-mcp"] }
}
}Then pair it once:
npx -y holoscrape-mcp --codeprints a one-time code. Open the HoloScrape side panel in Chrome and enter it there. That's the whole setup — the code is remembered, so this is a one-time step, not a per-session one.
Related MCP server: ma-browser
What it can do
Once paired, an agent can read whatever list is on a page you've allowed — a search results grid, a directory listing, a table — and walk its pages. Nothing runs until you've explicitly allowed the site in the HoloScrape panel; an agent cannot grant that to itself.
On a page with more than one scrollable region — a chat app's sidebar list beside an open
conversation, a filter rail beside results — the automatic ranking favours the denser pane, which
may not be the one you mean. The fix is two calls: page_study lists every candidate with its
selector, and list_extract with that selector pinned reads exactly that pane:
page_study { tabId: 12 } → lists[1].selector: "aside.rail>div.chats…"
list_extract { tabId: 12, selector: "aside.rail>div.chats…" } → grows and reads the sidebar, not the feedWhy local
The alternative is a hosted relay that sees every page it reads. This process listens only on
127.0.0.1, and the pairing code is the only thing that can talk to it — printed once, typed once,
checked before a socket is even allowed to open.
Tools
Tool | What it does |
| The tab the person has open right now, and whether it can be read. The place to start for "I have a page open, scrape it". |
| Every http(s) tab currently open — for when |
| Point a tab you already have at a URL, and wait until it is loaded. The navigation primitive. |
| Every repeating structure on a tab, ranked with evidence — not one verdict, several candidates so the caller chooses. Flags page furniture (footers, filter sidebars) that a naive reading mistakes for the real list. |
| Read the rows already on this page into a table, following its pages. The fast path, and the one to try first. Takes an optional |
| A list page and the records behind its links — many pages, one call, no rows through the agent. Opens one page per record in parallel lanes, so it costs minutes: if the fields you need are already on the cards, |
| Make a list longer and report whether it actually grew — press a load-more, or scroll a named pane to its own bottom. |
| Read the layers under the rendered page: the app's own in-memory store, and the network responses it renders from. Discovery first (what exists, with the path to read each part), then a data path. For virtualized lists, where the DOM holds only the mounted window, and for fields the markup omits. |
| Saved tables and the runs that fill them, under one |
Try it without an agent
node try.mjs tabs
node try.mjs study <tabId>Drives the same stdio protocol an agent would, useful for checking the whole chain — this script → the server → the WebSocket → the extension → a real tab — works before pointing a real agent at it.
Requirements
Node.js 18+
The HoloScrape Chrome extension, installed and paired
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Hosted MCP server for live public-data APIs and Skills for AI agents.
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Related MCP Servers
AlicenseAqualityBmaintenanceA local MCP server that lets AI agents bypass bot detection, geo-restrictions, and JavaScript rendering challenges when scraping the web, backed by ScraperAPI's services285MIT- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents use your real browser as an API, accessing any website with your login state, no keys or scrapers needed.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.63MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/joshghal/holoscrape-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server