Connect hosted or local MCP to PB
Choose hosted evidence and confirmed article tools or the published local read package, with explicit scopes and action boundaries.
On this page
Choose the connection surface
Hosted MCP and the published local package have different tools. Use the hosted service for supported remote evidence and confirmed article-draft workflows. Use the local package for public HTTP diagnostics and optional bounded workspace reads. Read the developer tools overview before assuming a client's packaged tools match the hosted service.
Connect to hosted MCP
In a compatible remote MCP client, add:
https://mcp.prerenderbuddy.com/mcpComplete PB authorization through the client's connection flow, or supply a supported scoped API key in protected connection configuration. Client support and directory/marketplace approval vary; the endpoint alone does not establish a finished connection.
Current Starter, Growth and Pro include eligible Developer API access. Effective legacy entitlements remain account-specific. Grant only the scopes for the evidence and actions you intend to use:
| Scope | Hosted MCP use |
|---|---|
sites | List available websites and overview evidence |
health | Read bounded website-health evidence |
activity | Read recorded crawler activity |
visibility | Read AI answer/source/competitor summaries and recommendations |
content | Read article ideas, content status and tasks |
content:write with content | Prepare proposals and generate explicitly confirmed, unapproved drafts |
The service publishes OAuth connection metadata at https://mcp.prerenderbuddy.com/.well-known/oauth-protected-resource/mcp.
Review proposals before generation
Use an eligible article idea and review the sourced proposal and remaining allowance before confirming a full draft. Confirmed generation uses one shared workspace article allowance unit and saves an unapproved draft. Follow the returned task status to read the result.
A generated draft is not approved or published. Hosted MCP exposes no article approval, delivery or scheduling tool; content:publish is not a hosted MCP authorization scope. Use the application or separately scoped Developer API workflow for reviewed publication. See Article Generation for the complete content process.
Start with local public diagnostics
The published local stdio package can run in a compatible local MCP client:
npx --yes @prerenderbuddy/mcp@0.2.5It requires Node.js 20 or newer. Without a key it inspects public HTTP responses and discovery files. It does not execute JavaScript as a browser renderer or establish indexing, citation or crawler identity.
Add scoped workspace access
For local workspace reads, create a narrowly scoped Developer API key and pass it to the trusted process as PRERENDER_BUDDY_API_KEY. The client package's installation guide explains its configuration. Do not paste keys into prompts, commit them or expose them to browser code.
Know the read-only boundary
The published local package can return bounded sites, Health, activity, visibility, recommendations and content-status evidence. It does not start workspace checks or collections, generate articles, clear cache, change questions, approve or publish, or manage campaigns. Its workspace content read returns metadata rather than full article bodies.
This local-package boundary is separate from hosted MCP's confirmed generation tools and the platform's configured CMS publishing. Buddy's advice is also separate from those action workflows. Follow How PB Works to see the roles together.