MCP File Preview Server

Created By
seanivorea year ago
MCP server for HTML file preview and analysis - Has been weird with OS but good on Cline so WIP
Overview

what is MCP File Preview Server?

MCP File Preview Server is a Model Context Protocol (MCP) server designed to provide capabilities for HTML file preview and analysis, enabling users to capture full-page screenshots of HTML files and analyze their structures.

how to use MCP File Preview Server?

To use the MCP File Preview Server, clone the repository, install the dependencies, build the project, and then configure it for use with either the Claude desktop app or the Cline VSCode extension.

key features of MCP File Preview Server?

  • Full-page screenshots of HTML files capturing the complete CSS styling.
  • Detailed analysis of HTML structures including counts of headings, paragraphs, images, and links.
  • Support for local file paths and resources, allowing the handling of files directly from the user’s system.
  • Organized management of screenshots saved to a designated directory.

use cases of MCP File Preview Server?

  1. Previewing and capturing screenshots of local HTML documents for web development.
  2. Analyzing the structure of HTML files for documentation or development purposes.
  3. Testing and debugging web pages using local resources.

FAQ from MCP File Preview Server?

  • What types of files can be previewed?

The server primarily supports local HTML files for previewing and analyzing.

  • Can I customize the screenshot dimensions?

Yes, you can specify optional width and height parameters when capturing screenshots.

  • Is the server free to use?

Yes, the MCP File Preview Server is open-source and can be used for free.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
seanivore
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago