Paperboy for Open WebUI
Give your Open WebUI models a way to read your search data, write an article and fact check it, all through Paperboy tools.
Set up
You will add an External Tool Server connection of type MCP (Streamable HTTP) in the admin settings, with Bearer authentication and your Paperboy key.
In Paperboy, open Settings, API keys, and create a key. It starts with pb_live_.
In Open WebUI, sign in as an administrator and open Settings, Admin, Integrations. Under External Tool Servers, click + Add Connection.
Set Type to MCP (Streamable HTTP). Do not choose OpenAPI, which the docs say can crash the UI for an MCP server.
Enter https://paperboyseo.com/mcp as the URL, set Auth to Bearer, and paste pb_live_YOUR_KEY in the Key field. Leave Function Name Filter List empty to expose all eight tools.
Click Verify Connection, then Save. In a chat, open the + menu, Integrations, Tools, enable the Paperboy tools, and ask for get_sites.
Type: MCP (Streamable HTTP)
URL: https://paperboyseo.com/mcp
Auth: Bearer
Key: pb_live_YOUR_KEY
Function Name Filter List: (leave empty to expose all tools)Replace 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
Click Verify Connection in the connection dialog, which confirms the server is reachable. Then enable the tools from + > Integrations > Tools in a chat and ask the model to list your Paperboy sites.
How to remove it
Remove the Paperboy connection from Settings, Admin, Integrations, External Tool Servers. The docs fetched do not describe the delete control. Revoke the key in Paperboy Settings, API keys, if you no longer need it.
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.
“List my Paperboy sites, pull the top queries for the first one, and suggest three article topics with the reason for each.”
Uses get_sitesget_queriessuggest_topics
“Write an article on the best topic you found, then keep calling get_article until it finishes and show me the verdict and sources. Do not publish it.”
Uses write_articleget_article
“Fact check the text I paste below with Paperboy and list every claim that has no supporting source. Then show me this month's clicks and impressions with get_performance.”
Uses check_claimsget_performance
Why
Open WebUI supports MCP over Streamable HTTP only, from v0.6.31, and only an administrator can add the connection. In Settings, Admin, Integrations, add an External Tool Server, set the type to MCP (Streamable HTTP) and not OpenAPI, then choose Bearer and paste the Paperboy key.
Each user still switches the tools on from the + menu in a chat. Use a model that can call tools, and expect write_article to return an id at once while get_article is polled for the result. Paperboy has no OAuth yet, so the OAuth options do not apply.
Compare
Same engine, two ways in. Pick the one that fits how you already work.
| Feature | Dashboard | Open WebUI | Source |
|---|---|---|---|
| Where you work | paperboyseo.com/app: sites, calendar, fact checks | Self-hosted web interface for local and hosted AI models, with tool servers. | Open WebUI docs: MCPRead Oct 30, 2026 |
| How it connects | Sign in and paste your site address. The first article is free. | Remote MCP. Open WebUI connects to MCP servers over Streamable HTTP only, from v0.6.31, through an admin-added connection of type MCP (Streamable HTTP) with Bearer authentication and a Key field. | Open WebUI docs: MCPRead Oct 30, 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 Open WebUI 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.
Only administrators can add MCP servers. The docs say regular users cannot register their own, so ask your admin or use an admin account.
Open WebUI needs v0.6.31 or later for MCP. It supports Streamable HTTP only, so there is no stdio or SSE route to Paperboy, and Paperboy has no OAuth yet, so choose Bearer and not an OAuth option.
Selecting Bearer without a Key sends an empty header and Paperboy will reject it with an authentication error.
Pick a model that handles tool calling, and enable the tools in each chat. The docs warn against pre-enabling OAuth 2.1 tools as defaults, but that does not apply to a Bearer connection.
FAQ
Pick MCP (Streamable HTTP). The docs say choosing OpenAPI for an MCP server causes UI crashes.
Use Bearer and paste the pb_live_ key into the Key field. Open WebUI sends it as the bearer credential. Paperboy has no OAuth yet, so the OAuth options do not apply.
According to the docs, no. Only administrators add MCP servers in Settings, Admin, Integrations, External Tool Servers.
Open WebUI can also add OpenAPI tool servers, and Paperboy publishes an OpenAPI 3.1 spec at https://paperboyseo.com/api/v1/openapi.json. Whether Open WebUI accepts that spec location as a tool server URL is not covered by its docs, so MCP is the documented route.
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 Open WebUI comes from the pages below, read on Oct 30, 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).