MCP File Preview Server
Related Servers
Alternatives to MCP File Preview Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceCaptures screenshots of web URLs or local HTML files using Playwright Chromium and exposes them as resources.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server for parsing HTML, fetching URLs, rendering terminal-style screenshots, and executing JavaScript on static HTML without external dependencies.3MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for lightweight web browsing: fetch and parse pages, extract structured content, run isolated JavaScript, and render to SVG/PNG/PDF with a minimal CDP interface.MIT
- AlicenseCqualityCmaintenanceA server that allows AI agents and clients to programmatically capture screenshots of websites with options for image format and viewport selection.15 npm9MIT
- AlicenseNot gradedqualityDmaintenanceScreenshot and HTML Rendering MCP Server for AI Agents. Capture screenshots, render HTML to images, and generate PDFs via simple API calls. Compatible with Claude, Cursor, and any MCP client.1MIT

polydoc-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP server that converts HTML or URLs to PDF, captures screenshots, and generates EU-compliant e-invoices (Factur-X/ZUGFeRD).216 npmMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: analyze_content focuses on structural analysis of HTML content, while preview_file handles file preview and screenshot capture. There is no overlap in functionality, making it easy for an agent to select the appropriate tool without confusion.
Both tools follow a consistent verb_noun naming pattern (analyze_content and preview_file), with clear, descriptive names that align with their functions. There are no deviations or mixed conventions, ensuring predictability and readability.
With only two tools, the server feels thin for a 'File Preview Server' that might be expected to handle more file types or operations beyond HTML. While the tools are focused, the count is borderline too few for the apparent scope, limiting functionality.
The server is severely incomplete for file preview purposes, as it only supports HTML files with no coverage for other common formats (e.g., images, PDFs, text files). There are significant gaps in the tool surface that will likely cause agent failures when dealing with non-HTML content.