spa-reader-mcp
Related Servers
Alternatives to spa-reader-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that fetches and renders dynamic web pages (SPA) using Chromium, returning content as Markdown or text. It uses lightweight HTTP first with automatic fallback to a browser for JS-heavy sites, and includes SSRF protection, login session support, and batch fetching.-
- AlicenseAqualityCmaintenanceAn MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.178 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI agents -- fetch any URL with full JavaScript rendering (Playwright/Chromium) and convert to clean, token-efficient markdown. Works on React, Vue, Angular, and any JS-heavy page. Includes web search, batch fetching, binary file download, LRU cache, SSRF protection, and structured output.29 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that scrapes content from web pages, including JavaScript-heavy sites, and converts it into high-quality Markdown. It leverages Playwright for headless browser automation and Pypandoc for clean content conversion.Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for web content extraction that converts HTML pages into clean, LLM-optimized Markdown using Mozilla's Readability. It supports batch processing, intelligent multi-page crawling, and configurable caching while respecting robots.txt standards.91 npm-
- AlicenseBqualityFmaintenanceAn MCP server that retrieves web page content using Playwright headless browser, capable of extracting main content and converting to Markdown format.35,328 npm1,086MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: spa_read extracts textual content as Markdown for LLM processing, while spa_screenshot captures visual output as PNG for screenshots. There is no overlap in functionality or ambiguity about which tool to use for a given task.
Both tools follow a consistent 'spa_' prefix pattern with descriptive suffixes (read, screenshot), indicating they belong to the same domain and operate on SPA pages. The naming is uniform, predictable, and clearly communicates each tool's function.
With only 2 tools, the server feels thin for a general-purpose SPA reader domain, as it lacks operations like navigation, interaction simulation, or performance monitoring. However, it covers the core tasks of content extraction and screenshot capture adequately for basic use.
The tools provide essential read-only capabilities for SPAs (extracting content and screenshots), but there are notable gaps: no ability to interact with pages (e.g., click buttons, fill forms), navigate beyond initial URLs, or handle dynamic content beyond rendering. This limits advanced agent workflows.