Paperboy for Flowise
Wire Paperboy into a Flowise agent so flows can research topics, draft articles and fact check them.
Set up
You will create a Flowise variable for the key, add a Custom MCP tool to an Agent node, and paste a url plus headers config.
In Paperboy, open Settings and create an API key. It starts with pb_live_.
In Flowise, create a variable named paperboyKey with the value pb_live_YOUR_KEY.
Add a Custom MCP tool to an Agent node.
Paste the JSON above into the MCP Server Config.
Refresh Available Actions to load the tools from Paperboy.
Select the actions you want, then run a chat and ask it to call get_sites.
{
"url": "https://paperboyseo.com/mcp",
"headers": {
"Authorization": "Bearer {{$vars.paperboyKey}}"
}
}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
Refresh Available Actions. If the Paperboy tools are listed, the URL and header work. Then run the flow and call get_sites.
How to remove it
Remove the Custom MCP tool from the Agent node and delete the paperboyKey variable if unused.
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 list my sites, suggest topics for the main one, and write an article for the top topic.”
Uses get_sitessuggest_topicswrite_article
“Fetch my latest Paperboy draft with get_article and run check_claims on it. Tell me which claims need a source.”
Uses get_articlecheck_claims
“Ask Paperboy for my top search queries and page performance this month and summarize what to write next.”
Uses get_queriesget_performance
Why
Flowise adds MCP servers through its Custom MCP tool on an Agent node. For a remote server you paste a small JSON object with a url and a headers object. Paperboy's endpoint and an Authorization header are all it needs.
Flowise lets headers read from variables with the {{$vars.name}} syntax, so store the key as a variable instead of pasting it into the flow. After saving, refresh Available Actions to load the Paperboy tools.
Compare
Same engine, two ways in. Pick the one that fits how you already work.
| Feature | Dashboard | Flowise | Source |
|---|---|---|---|
| Where you work | paperboyseo.com/app: sites, calendar, fact checks | Open source visual builder for LLM flows and agents with a Custom MCP tool. | Flowise docs: Tools & MCPRead Oct 30, 2026 |
| How it connects | Sign in and paste your site address. The first article is free. | Remote MCP. Flowise has a Custom MCP tool for Agent nodes. | Flowise docs: Tools & 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 Flowise 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.
The docs use the {{$vars.<variableName>}} syntax so the key is not hardcoded in the flow.
The docs example has a trailing comma after the headers entry, which is not valid JSON, so the block here leaves it out.
The tools only load after you refresh Available Actions.
FAQ
Yes. The docs show a Custom MCP tool config with a url and headers for streamable HTTP.
Create a Flowise variable and reference it as {{$vars.name}} in the headers.
Refresh Available Actions after entering the config.
The Custom MCP tool on an Agent node, per the Flowise tools and MCP docs.
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 Flowise 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).