WebRendererMCP

Created By
zys5945a year ago
MCP server that renders HTML produced by LLMs
Overview

what is WebRendererMCP?

WebRendererMCP is a server that renders HTML produced by Large Language Models (LLMs) using Playwright, providing a way to visualize web content dynamically.

how to use WebRendererMCP?

To use WebRendererMCP, install it by adding the following configuration to your MCP servers:

{
  "mcpServers": {
    "WebRenderer": {
      "command": "npx",
      "args": ["web-renderer-mcp"]
    }
  }
}

Then, you can call the provided tool to render HTML content.

key features of WebRendererMCP?

  • Renders HTML content generated by LLMs.
  • Utilizes Playwright for rendering, ensuring high fidelity.
  • Exposes a simple command interface for integration.

use cases of WebRendererMCP?

  1. Rendering dynamic web pages generated by AI models.
  2. Testing and visualizing HTML outputs from LLMs.
  3. Integrating with other applications that require HTML rendering.

FAQ from WebRendererMCP?

  • What is the main purpose of WebRendererMCP?

It is designed to render HTML content produced by LLMs, making it easier to visualize and interact with AI-generated web content.

  • How do I install WebRendererMCP?

You can install it by adding the provided configuration to your MCP servers and using the command npx web-renderer-mcp.

  • Can I use WebRendererMCP for any HTML content?

Yes, as long as the HTML is generated by an LLM, WebRendererMCP can render it.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zys5945
Star
0
Language
JavaScript
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)

a day ago
Crevio

2 days ago