Connect hosted or local MCP to PB

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, optional bounded workspace reads and, from version 0.3.0, separately authorized article-draft tools. Read the developer tools overview before assuming a client's packaged tools match the hosted service.

In a compatible remote MCP client, add:

https://mcp.prerenderbuddy.com/mcp

Complete 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:

The service publishes OAuth connection metadata at https://mcp.prerenderbuddy.com/.well-known/oauth-protected-resource/mcp.

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.

The published local stdio package can run in a compatible local MCP client:

npx --yes @prerenderbuddy/mcp@0.3.1

It 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.

For local workspace reads, create a narrowly scoped Developer API key and pass it to the trusted process as PRERENDER_BUDDY_API_KEY. Use sites to select websites and add only the evidence scopes you need. The package README explains client configuration. Do not paste keys into prompts, commit them or expose them to browser code.

Local evidence tools return bounded sites, Health, activity, visibility, recommendations and content-status evidence. These reads do not start fresh collections. get_content_status returns article metadata rather than article bodies.

Version 0.3.1 includes list_article_ideas, prepare_article_proposal, get_article_task and generate_article. Reading ideas and tasks needs content; preparing a proposal and generating its draft also need content:write. A key without that scope remains read-only.

List an eligible idea, prepare its proposal with a stable request UUID and poll the task at the returned interval. Review the proposal and remaining allowance before explicitly confirming generation. The completed task returns the saved Markdown draft and its PB review link. The draft is unapproved; these tools cannot approve, publish or schedule it.

An installed plugin may pin an older package. Check its version and available tools before assuming it supports generation. Follow the package README for the current local workflow.

Neither MCP surface grants unrestricted account control. They do not clear cache, change tracked questions or manage advertising campaigns. Use Agent for supported in-app plans, and the application or Developer API for separate reviewed publishing actions.