K
kopachlager/prerenderbuddy-mcp
The MCP companion to the Prerender Buddy AI visibility and crawler-readiness
★ 1·更新 2026-11-13
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 1 ★ · kopachlager/prerenderbuddy-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 1 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
kopachlager/prerenderbuddy-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Prerender Buddy MCP
以下摘录自该仓库的 README(片段)
The MCP companion to the Prerender Buddy AI visibility and crawler-readiness
platform. It checks what public crawlers can read and can optionally retrieve
evidence from a Prerender Buddy workspace, with optional confirmed article generation.
The server wraps the open-source
@prerenderbuddy/cli.
The public audit tools do not run a browser, execute JavaScript, call the
Prerender Buddy API, or require an account. Starter, Growth and Pro users can optionally configure
an API key to add account-aware health, activity, visibility, recommendation,
and content-status tools.
Prefer a terminal or CI workflow? Use the
prerenderbuddy-cli
directly. See the
Prerender Buddy tools overview
to compare the CLI, MCP server, Chrome extension, and managed service.
## Quick start
Run the stdio server:
bash
npx --yes @prerenderbuddy/mcp
Generic MCP client configuration:
json
"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:
text
check_crawler_readability
compare_http_responses
check_discovery_files
With PRERENDER_BUDDY_API_KEY configured, the server also lists:
text
list_sites
get_site_overview
get_health_evidence
get_crawler_activity
get_ai_visibility
get_recommendations
get_content_status
## Grok Build
Grok Build can launch the local stdio server:
bash
grok mcp add prerenderbuddy -- npx --yes @prerenderbuddy/mcp@0.4.0
Or install the official plugin, which already includes Claude-compatible manifests:
bash
grok plugin marketplace add kopachlager/prerenderbuddy-plugins
grok plugin install prerenderbuddy --trust
Set PRERENDER_BUDDY_API_KEY in the process environment when workspace evidence is required. Unresolved placeholders such as ${PRERENDER_BUDDY_API_KEY} are treated as absent.
## Streamable HTTP / Grok Bot
Grok Bot on grok.com, iOS, and Android cannot start a local npx process. It needs a public HTTPS MCP URL.
Run Streamable HTTP locally:
bash
npx --yes @prerenderbuddy/mcp@0.4.0 --http --port 8787
Loopback HTTP (127.0.0.1) allows unauthenticated public diagnostic tools and still rate-limits requests. Binding a public interface (--host 0.0.0.0 or a non-loopback HOST) requires a Bearer token:
a valid, unrevoked eligible workspace API key (pb_live_... or pb_test_...), verified with the PB API before each authenticated request, which also enables workspace tools; or
MCP_HTTP_SHARED_TOKEN, a connector token for public diagnostics only.
bash
MCP_TRANSPORT=http HOST=0.0.0.0 PORT=8787 MCP_HTTP_REQUIRE_AUTH=true \
npx --yes @prerenderbuddy/mcp@0.4.0
Health check: GET /health. MCP endpoint: POST /mcp. Authenticated GET and DELETE on /mcp return 405; this stateless JSON endpoint does not offer an SSE session stream.
Deploy the Dockerfile as a dedicated service with MCP_TRANSPORT=http,
HOST=0.0.0.0, and MCP_HTTP_REQUIRE_AUTH=true; retain the hosting platform's
PORT. railway.json configures the health check. Never set
PRERENDER_BUDDY_API_KEY on a shared HTTP service: HTTP tools use only the
request's workspace key, and never inherit the process key.
The default ingress cap is 120 MCP requests per minute per process, including
platform. It checks what public crawlers can read and can optionally retrieve
evidence from a Prerender Buddy workspace, with optional confirmed article generation.
The server wraps the open-source
@prerenderbuddy/cli.
The public audit tools do not run a browser, execute JavaScript, call the
Prerender Buddy API, or require an account. Starter, Growth and Pro users can optionally configure
an API key to add account-aware health, activity, visibility, recommendation,
and content-status tools.
Prefer a terminal or CI workflow? Use the
prerenderbuddy-cli
directly. See the
Prerender Buddy tools overview
to compare the CLI, MCP server, Chrome extension, and managed service.
## Quick start
Run the stdio server:
bash
npx --yes @prerenderbuddy/mcp
Generic MCP client configuration:
json
"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:
text
check_crawler_readability
compare_http_responses
check_discovery_files
With PRERENDER_BUDDY_API_KEY configured, the server also lists:
text
list_sites
get_site_overview
get_health_evidence
get_crawler_activity
get_ai_visibility
get_recommendations
get_content_status
## Grok Build
Grok Build can launch the local stdio server:
bash
grok mcp add prerenderbuddy -- npx --yes @prerenderbuddy/mcp@0.4.0
Or install the official plugin, which already includes Claude-compatible manifests:
bash
grok plugin marketplace add kopachlager/prerenderbuddy-plugins
grok plugin install prerenderbuddy --trust
Set PRERENDER_BUDDY_API_KEY in the process environment when workspace evidence is required. Unresolved placeholders such as ${PRERENDER_BUDDY_API_KEY} are treated as absent.
## Streamable HTTP / Grok Bot
Grok Bot on grok.com, iOS, and Android cannot start a local npx process. It needs a public HTTPS MCP URL.
Run Streamable HTTP locally:
bash
npx --yes @prerenderbuddy/mcp@0.4.0 --http --port 8787
Loopback HTTP (127.0.0.1) allows unauthenticated public diagnostic tools and still rate-limits requests. Binding a public interface (--host 0.0.0.0 or a non-loopback HOST) requires a Bearer token:
a valid, unrevoked eligible workspace API key (pb_live_... or pb_test_...), verified with the PB API before each authenticated request, which also enables workspace tools; or
MCP_HTTP_SHARED_TOKEN, a connector token for public diagnostics only.
bash
MCP_TRANSPORT=http HOST=0.0.0.0 PORT=8787 MCP_HTTP_REQUIRE_AUTH=true \
npx --yes @prerenderbuddy/mcp@0.4.0
Health check: GET /health. MCP endpoint: POST /mcp. Authenticated GET and DELETE on /mcp return 405; this stateless JSON endpoint does not offer an SSE session stream.
Deploy the Dockerfile as a dedicated service with MCP_TRANSPORT=http,
HOST=0.0.0.0, and MCP_HTTP_REQUIRE_AUTH=true; retain the hosting platform's
PORT. railway.json configures the health check. Never set
PRERENDER_BUDDY_API_KEY on a shared HTTP service: HTTP tools use only the
request's workspace key, and never inherit the process key.
The default ingress cap is 120 MCP requests per minute per process, including
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/kopachlager-prerenderbuddy-mcp/)
- 来源
- awesome · https://github.com/kopachlager/prerenderbuddy-mcp
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。