Paperboy for Dify
Give Dify agents and workflows Paperboy's topic, drafting and fact check tools through one MCP entry.
Set up
You will add Paperboy as an MCP server in Dify's Tools area and add an Authorization header.
In Paperboy, open Settings and create an API key. It starts with pb_live_.
In Dify, go to Integrations > Tools and add an MCP server.
Enter the URL, a name and a unique server identifier such as paperboy.
Add an Authorization header with the value Bearer pb_live_YOUR_KEY.
Save so Dify connects and imports the tools.
Add the Paperboy tools to an agent or workflow app and run get_sites.
Server URL: https://paperboyseo.com/mcp
Name: Paperboy
Server identifier: paperboy
Headers:
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
After saving, Dify imports the server's tools. Confirm the Paperboy tools are listed, then call get_sites from an app.
How to remove it
Remove the server from Integrations > Tools. Apps that used its tools will need those tools replaced.
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
Dify connects to MCP servers over HTTP from Integrations > Tools. You give it a URL, a name and an identifier, and it can send custom headers with every request. A static Authorization header carries your Paperboy key.
Choose the identifier carefully. Apps refer to the server by it, and changing it later breaks the tools in those apps. Exported apps use the same identifier, so match it when you move to another workspace.
Compare
Same engine, two ways in. Pick the one that fits how you already work.
| Feature | Dashboard | Dify | Source |
|---|---|---|---|
| Where you work | paperboyseo.com/app: sites, calendar, fact checks | Open source platform for building LLM apps, agents and workflows. | Dify docs: Use MCP ToolsRead Oct 30, 2026 |
| How it connects | Sign in and paste your site address. The first article is free. | Remote MCP. Dify acts as an MCP client for servers on HTTP transport. | Dify docs: Use MCP ToolsRead 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 Dify 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 MCP servers with HTTP transport are supported.
Do not change the server identifier later, because tools stop working in apps that used the old one.
Exported apps reference servers by identifier, so recreate the server with the same identifier in another workspace.
Dynamic Client Registration is on by default for OAuth. Paperboy uses a header key, so you do not need it.
FAQ
Yes. The docs say Dify sends additional HTTP headers with every request, such as Authorization: Bearer <token>.
Integrations > Tools, per the docs.
Tools stop working in apps that used the old identifier.
The docs say only HTTP transport is supported, which is what Paperboy's URL uses.
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 Dify 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).