Log inSubmit server
Prerender Buddy logo

Prerender Buddy

Inspect crawler-readable HTML, compare bot and browser responses, and check public discovery files through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Prerender Buddy

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "prerender-buddy": {
      "command": "npx",
      "args": [
        "--yes",
        "@prerenderbuddy/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 3 tools correctly (1d ago).

Overview

Prerender Buddy MCP server provides local diagnostics for how public crawlers read websites and discover site files. Its public tools fetch ordinary HTTP responses without running a browser or JavaScript, while optional workspace tools retrieve evidence from the Prerender Buddy API. Use it to investigate crawler readability, compare user-agent responses, or review robots.txt, sitemap.xml, and llms.txt. A stdio mode suits local MCP clients, and Streamable HTTP supports hosted connectors such as Grok Bot.

Use cases

  • Check whether Googlebot receives meaningful HTML
  • Compare GPTBot and browser HTTP responses
  • Inspect public robots.txt, sitemap.xml, and llms.txt files
  • Review crawler activity and AI visibility for registered sites

Key features

  • Crawler-specific readability diagnostics
  • Browser-versus-crawler response comparison
  • Discovery-file checks
  • Optional Prerender Buddy workspace evidence
  • Stdio and Streamable HTTP transports
  • URL safety and redirect validation

Tools3

What Prerender Buddy lets your agent do. Expand a tool for its parameters.

Verified live~592 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 49d

What it can do

From the 3 tools this server returned when we ran it; 3 declare their own safety hints.

Runs commands · 1Makes network requests · 3Read-only tools · 2
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age98 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @prerenderbuddy/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.

How Prerender Buddy works

What Prerender Buddy MCP server does

Prerender Buddy exposes website-readiness checks through MCP. The unauthenticated tools inspect public URLs directly and return structured results that an AI client can use when reviewing crawler access and page content. These checks do not require a Prerender Buddy account, do not use browser rendering, and do not execute JavaScript.

An optional workspace mode connects to the authenticated Prerender Buddy Developer API. With an eligible workspace API key, agents can inspect registered sites, health evidence, crawler activity, AI visibility, recommendations, and content-status metadata. Existing evidence tools are read-only; article generation is a separate opt-in capability.

How it works

The public diagnostics make ordinary HTTP requests to the URL being checked. Supported crawler profiles are Googlebot, Bingbot, GPTBot, and ClaudeBot. Results can include the final URL, status, page metadata, headings, readable-text counts, JavaScript app-shell indicators, evidence, severity, and suggested next steps.

compare_http_responses requests a page with a browser-style user agent and a selected crawler user agent, then places the responses side by side. A difference is an investigation signal rather than proof of cloaking or a search-ranking issue.

The server can run over stdio with npx --yes @prerenderbuddy/mcp. It also supports Streamable HTTP, with /health for a health check and /mcp for MCP requests. The HTTP endpoint uses stateless JSON responses and does not provide an SSE session stream.

Setup and configuration

For a local client, add the package as a stdio MCP server with npx --yes @prerenderbuddy/mcp, then restart the client. Set PRERENDER_BUDDY_API_KEY in the process environment to enable workspace tools. The API origin defaults to https://api.prerenderbuddy.com and can be changed with PRERENDER_BUDDY_API_BASE_URL.

To expose the server over HTTP, run it with the HTTP transport and configure its host and port. Public-interface deployments require authentication through an eligible workspace API key or MCP_HTTP_SHARED_TOKEN; loopback HTTP can expose the public diagnostics without authentication. MCP_HTTP_REQUIRE_AUTH enables the explicit authentication requirement. Use HTTPS, rate limits, and a token before exposing the endpoint to a hosted client.

HTTP deployments apply process-local ingress and authenticated-request rate limits. MCP_HTTP_INGRESS_RATE_LIMIT_MAX and MCP_HTTP_RATE_LIMIT_MAX control those limits. A shared gateway limit is appropriate when running multiple replicas.

Tools and capabilities

  • check_crawler_readability fetches one public page using a selected crawler profile and reports its HTTP and readable-content characteristics.
  • compare_http_responses compares browser-style and crawler-style HTTP responses without JavaScript execution.
  • check_discovery_files checks public robots.txt, sitemap.xml, and llms.txt locations.
  • list_sites and get_site_overview provide workspace site and monitoring summaries.
  • get_health_evidence, get_crawler_activity, and get_ai_visibility retrieve bounded workspace evidence.
  • get_recommendations returns the latest evidence-based diagnosis, while get_content_status lists calendar and draft metadata without article bodies.

Limitations and notes

The local public-audit mode is intended for one-time checks. It does not provide browser rendering, JavaScript execution, managed crawler routing, scheduled monitoring, historical incidents, cache operations, DNS or proxy onboarding, or access to private Prerender Buddy infrastructure.

Only inspect websites you are authorized to test. Requests block local, private, link-local, reserved, and multicast targets, and redirect destinations are revalidated. Website responses are untrusted data. In HTTP mode, do not publish an unauthenticated URL-fetching endpoint. Workspace API keys should remain in the process environment rather than prompts or repository files.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Prerender Buddy

Prerender Buddy is an MCP server that connects AI clients to public websites and, optionally, the Prerender Buddy Developer API. Its main tools check crawler readability, compare browser and crawler HTTP responses, and inspect robots.txt, sitemap.xml, and llms.txt files. Workspace tools add site, health, activity, visibility, recommendation, and content-status queries.

Run `npx --yes @prerenderbuddy/mcp` and add that command to your MCP client's stdio configuration. Restart the client after changing its configuration, then ask it to list available MCP tools.

Set `PRERENDER_BUDDY_API_KEY` in the MCP process environment. The key must be a Developer API key from an eligible Prerender Buddy Starter, Growth, or Pro workspace, and the API scopes access to registered sites and permitted evidence groups.

Yes, run the package with the HTTP transport and expose its `/mcp` endpoint over HTTPS for hosted clients. Public-interface deployments require a valid workspace key or `MCP_HTTP_SHARED_TOKEN`; apply authentication and rate limits before publishing the endpoint.

No, the public diagnostics use ordinary HTTP responses and do not run a browser or execute JavaScript. The readability check can identify transparent app-shell indicators, but it does not render the page.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPrerender Buddy AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/prerender-buddy?style=directory)](https://allmcps.com/mcp/prerender-buddy)
HTML Embed
<a href="https://allmcps.com/mcp/prerender-buddy"><img src="https://allmcps.com/api/badge/prerender-buddy?style=directory" alt="Prerender Buddy on AllMCPs" /></a>