Paperboy for v0
Bring Paperboy into v0 with a bearer token while it generates, or keep the key as an environment variable and call the REST API from the app.
Set up
You will add Paperboy as a bring-your-own MCP server from the + menu in v0's prompt form, using Bearer Token or Custom Headers.
v0 supports bring-your-own MCP servers from the + menu in the prompt form, with No Auth, Custom Headers, Bearer Token or OAuth. The tools are only available to v0 while it generates, and the app v0 builds cannot call them. The docs do not name the transport or list the field labels, so verify the connection in a chat.
In the prompt form, open the + menu and select MCPs.
Choose to configure a custom MCP server instead of a preset.
Enter https://paperboyseo.com/mcp as the server URL.
Pick Bearer Token (or Custom Headers) as the authentication and enter your Paperboy key.
Start a new chat or continue an existing one. v0 considers the connected MCP servers and their tools when it generates responses.
For a feature in the shipped app, add PAPERBOY_API_KEY under Project menu ... → Settings → Environment Variables and ask v0 to use it in API calls.
URL: https://paperboyseo.com/mcp
Authentication: Bearer Token
Token: pb_live_YOUR_KEY
Or, with Custom Headers instead:
Authorization: Bearer pb_live_YOUR_KEYReplace pb_live_YOUR_KEY with a key from Settings, API keys, and never commit it. The MCP docs list every client we cover.
How to tell it worked
The docs describe no connection indicator. Start a chat and ask v0 to list your Paperboy sites. v0 considers connected MCP tools automatically, so a correct answer means the server works.
How to remove it
The docs give no removal step. They describe an enabled or disabled state for a custom MCP server that controls whether v0 can use its tools.
What you get
Eight tools, the same engine as the dashboard. Reads are free. A pack is $20 for 100 credits; see how credits work.
get_sitesLists your sites with plan, publishing method and whether Search Console is connected. Every other call starts from a site id.
suggest_topicsReturns the next articles to write, each with the search data that is the reason for it.
write_articleStarts a fact-checked article and returns an id at once. The run takes a few minutes. It does not publish unless you pass publish: true.
get_articleReturns the article's status, its fact-check verdict and every source. Poll it after write_article until it reads published or needs_review.
check_claimsFact checks any public URL or pasted Markdown and returns each cited claim with the sources it was compared against.
publish_articlePublishes an article that passed the fact check to the site's publishing target. It changes the live site, so the agent should ask first.
get_performanceSearch Console clicks, impressions and average position for a site, by day and by article.
get_queriesThe queries a site, or one article, appears for in Search Console. This is where page-two keywords show up.
Try it
Plain requests. The tools each one uses are listed under it.
“Use Paperboy to find queries where my site ranks just off page one, suggest a topic, and build a landing section around the best one.”
Uses get_sitesget_queriessuggest_topics
“Write the article for the best topic with Paperboy and generate a blog post page that renders it.”
Uses write_articleget_article
“Check the claims in my latest Paperboy article and rewrite any unsupported lines on the page.”
Uses get_articlecheck_claims
Why
v0 supports bring-your-own MCP servers from the plus menu in the prompt form, with Bearer Token among the choices. The tools are available only while v0 generates. The app it builds cannot call them.
For a feature inside the shipped app, store the key as a project environment variable and prompt v0 to add a server-side route. The preview can only read variables available to the Development environment, so switch that one on.
Compare
Same engine, two ways in. Pick the one that fits how you already work.
| Feature | Dashboard | v0 | Source |
|---|---|---|---|
| Where you work | paperboyseo.com/app: sites, calendar, fact checks | AI-powered development platform that builds production-ready apps from natural-language prompts. | v0 docs: MCP IntegrationsRead Oct 29, 2026 |
| How it connects | Sign in and paste your site address. The first article is free. | MCP with limits. v0 supports bring-your-own MCP servers from the + menu in the prompt form, with No Auth, Custom Headers, Bearer Token or OAuth. | v0 docs: MCP IntegrationsRead Oct 29, 2026 |
| Does it publish without asking? | Your choice: autopilot, or approve each article by email. | No. write_article defaults to publish: false, and the tool descriptions tell the agent to ask first. | MCP docsPaperboy docs |
| Fact check | Every number and cited sentence is compared with the saved text of its source. An article that fails gets one rewrite, then is held for you. | The same engine and the same check. The verdict comes back to the agent: verified, or held with the reason. | How the check worksPaperboy docs |
| What it costs | Plans from $49 a month per site. The first article is free, no card. | Credits: 12 per article, 1 per topic suggestion, 2 per fact check. $20 buys 100. | CreditsPaperboy docs |
| Search Console | Optional read-only Search Console connection. It picks topics from your impressions and reports clicks per article. | get_performance and get_queries return the same read-only data, by day, by article and by query. | Security and dataPaperboy docs |
Facts about v0 come from the pages linked in the Source column, read on the date shown. Tools change their docs, so confirm there if a step does not match.
Honest notes
Quirks of this client that can cost you an afternoon.
MCP tools work during generation only. The docs say the generation v0 creates cannot use the MCP tools directly, so a Paperboy feature in your shipped app needs the REST API plus an environment variable.
Tool calls follow v0's permission mode. The chat's Ask, Auto or Full mode and any Agent Permissions rules (Settings → Agent Permissions) decide whether a call runs, asks or is blocked. Full skips approval checks, and the docs say a destructive call is not guaranteed to need approval, so review before letting publish_article run.
Environment variables for the REST route: the v0 preview can only read variables available to the Development environment, and sensitive environment variables are inaccessible to v0 previews. Add PAPERBOY_API_KEY as a regular variable with Development turned on.
FAQ
Yes. v0 lists four kinds of authentication for a manually configured server: No Auth, Custom Headers, Bearer Token and OAuth. Open the + menu in the prompt form and select MCPs.
No. The docs say the generation v0 creates cannot use the MCP tools directly. Use the Paperboy REST API with an environment variable for features in the shipped app.
Go to Project menu ... → Settings → Environment Variables and add it. The v0 preview only sees variables available to the Development environment.
It depends on the permission mode. Ask requires confirmation for calls no rule matches, Auto generally runs unmatched calls, and Full skips approval checks. Set Agent Permissions rules to control it.
The tools that read cost nothing. Suggesting topics costs 1 credit, writing a fact-checked article costs 12 credits (refunded if the run fails) and a fact check on its own costs 2 credits. A pack is $20 for 100 credits.
Only if you let it. write_article defaults to publish: false, so a finished article waits for a human, and the tool descriptions tell the agent to ask before publishing. You can also give the agent a read-only key.
Sources
Everything about v0 comes from the pages below, read on Oct 29, 2026. Tools change their docs, so check there if a step does not match. If we got something wrong, write to hello@paperboyseo.com.
Keep going
Add the MCP server, ask for a topic, and read the fact check before anything goes live.
claude mcp add --transport http paperboy https://paperboyseo.com/mcp --header "Authorization: Bearer pb_live_..."npx @paperboyseo/cli coming soonPrefer the dashboard? Write my first article free. Prefer to run it yourself? Self-host it (repo coming soon).