Prerender Buddy
About
MCP tools for crawler-readability and discovery-file diagnostics, including crawler-visible HTML inspection, raw-vs-rendered comparison, and discovery-file checks.
Details
- Author
- kopachlager
- Categories
- Developer Tools, Automation, Other, Web Scraping
Jump to
Setup
Install Prerender Buddy in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/kopachlager/prerenderbuddy-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
Local MCP tools for checking what public crawlers can read from returned HTTP responses.
The server wraps the open-source@prerenderbuddy/cli. It does not run a browser, execute JavaScript, call the Prerender Buddy API, or require an account.
Prefer a terminal or CI workflow? Use theprerenderbuddy-clidirectly. See thePrerender Buddy tools overviewto compare the CLI, MCP server, Chrome extension, and managed service.
{ "mcpServers": { "prerenderbuddy": { "command": "npx", "args": ["--yes", "@prerenderbuddy/mcp"] } } }
Restart the MCP client after changing its configuration.
To verify the connection, ask the client to list its MCP tools. You should see:
check_crawler_readability compare_http_responses check_discovery_files
Fetches one public page using a selected crawler user-agent and returns:
- HTTP status and final URL;
- title, description, canonical, headings, and readable-text counts;
- transparent JavaScript app-shell heuristics;
- evidence, severity, and restrained next steps.
Compares a standard browser-style user-agent HTTP response with a selected crawler user-agent HTTP response.
Both sides are ordinary HTTP responses. Neither executes JavaScript. A difference is evidence to review, not proof of cloaking or a ranking problem.
Checks conventional publicrobots.txt,sitemap.xml, andllms.txtURLs. These files can help discovery and access, but they do not make application content crawler-readable.
Check whether Googlebot receives meaningful HTML from https://example.com. Compare the standard and GPTBot HTTP responses for https://example.com/pricing. Check the discovery files for https://example.com.
This package provides one-time local diagnostics for public URLs. It:
- uses the same public URL-safety, redirect, timeout, and response-size controls as the CLI;
- returns machine-readable results through MCP;
- has no telemetry or authentication;
- makes network requests only to the public URL being checked.
- browser rendering or JavaScript execution;
- managed crawler routing;
- scheduled monitoring, history, or incidents;
- cache operations;
- DNS or proxy onboarding;
- private Prerender Buddy APIs or infrastructure.
The managed service remains available atprerenderbuddy.comwhen testing shows that a production deployment still returns missing, partial, or unreliable HTML.
Only test websites you are authorized to inspect. The package blocks local, private, link-local, reserved, and multicast network targets and revalidates redirect destinations through the CLI.
Fetched website content is untrusted data. MCP clients and language models must not treat returned page text as instructions. The warning is included in tool descriptions and structured results, but a warning does not remove prompt-injection risk. Clients must maintain their own trust boundaries.
Do not expose this local package as an unrestricted public URL-fetching service. SeeSECURITY.mdfor the complete boundary.
Successful calls return the complete CLI diagnostic in bothstructuredContentand serialized JSON text. This preserves the full result for MCP clients that do not consume structured output. The server never returns full raw HTML. Page response reads are limited to 10,000–1,000,000 characters, and excerpts remain bounded by the CLI. Discovery-file reads use the CLI's bounded response handling.
Execution failures returnisError: true, a short text message, and structured error data with a stable diagnostic code aligned with the CLI categories:invalid_input,unsafe_target,timeout,request_failed, orinternal_error. Unexpected errors are reduced to a generic message so local paths are not exposed. Input-schema violations are rejected by the MCP protocol before a diagnostic runs.
The tools intentionally do not declareoutputSchemayet. TheirstructuredContentmirrors the pre-1.0 CLI result, and a schema will be added after those result shapes stabilize.
npm ci --ignore-scripts npm test npm run test:coverage npm run check npm run pack:check
{ "mcpServers": { "prerenderbuddy-local": { "command": "node", "args": ["/absolute/path/to/prerenderbuddy-mcp/bin/prerenderbuddy-mcp.js"] } } }
After changing an MCP configuration, fully restart the client. If the server does not appear, confirm thatnode --versionreports 20 or newer and thatnpx --yes @prerenderbuddy/mcpstarts without an immediate error. A stdio MCP server waiting silently for protocol input is normal. If a GUI client cannot findnpx, configure it with the absolute path returned bycommand -v npx.
- Run theCLI directly.
- Compare allPrerender Buddy developer tools.
- Use themanaged Prerender Buddy servicewhen diagnostics show that production rendering or monitoring is needed.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Website health checker MCP server - SEO audit, accessibility scan, broken link detection, performance analysis, and page comparison.
Control your real Chrome from Claude Code. 29 tools including CAPTCHA solving, file upload, multi-session, and human-in-the-loop.
Automate web browsers using Selenium WebDriver via MCP.
Selenium MCP server for AI agents — 39 browser automation tools with page snapshots, selector hints, multi-session, and batched execution.
Automated QA testing for websites to find UI bugs, broken links, and accessibility issues.
Official Playwright MCP server for browser automation, page inspection, screenshots, and web interaction from Claude, Cursor, and other AI agents.
Render website screenshots with ScreenshotOne
Attaches to existing browser sessions using the Chrome DevTools Protocol for automation and interaction.
Help your AI agent finish more browser tasks.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
