Paperboy for Amp
Keep research, drafting and fact checking inside Amp by defining Paperboy once in settings.json.
Set up
You will add Paperboy as a remote MCP server in Amp's settings.json with an Authorization header.
Create an API key in Paperboy under Settings. It starts with pb_live_.
Open ~/.config/amp/settings.json (user) or .amp/settings.json (workspace).
Add the amp.mcpServers entry from the block above.
If you used the workspace file, run amp mcp approve paperboy, because workspace servers need approval before they run.
Ask the agent to call one Paperboy tool, such as get_sites.
{
"amp.mcpServers": {
"paperboy": {
"url": "https://paperboyseo.com/mcp",
"headers": {
"Authorization": "Bearer pb_live_YOUR_KEY"
}
}
}
}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
Run amp mcp list, or amp mcp doctor to check the setup, then ask the agent to call get_sites.
How to remove it
Delete the paperboy entry from amp.mcpServers in settings.json.
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. Save it under content/blog.”
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, then write the findings into SEO_NOTES.md.”
Uses get_queriesget_performance
Why
Amp keeps MCP servers under the amp.mcpServers key in settings.json. A remote server is a url plus an optional headers object, so Paperboy is one short entry carrying the Authorization header.
Amp separates user and workspace settings. Workspace servers wait for amp mcp approve before they run, which suits a shared repo, but it also means the key should live in your user file. amp mcp list and amp mcp doctor show what is connected.
Compare
Same engine, two ways in. Pick the one that fits how you already work.
| Feature | Dashboard | Amp | Source |
|---|---|---|---|
| Where you work | paperboyseo.com/app: sites, calendar, fact checks | Coding agent from Sourcegraph with MCP server support in editor and CLI. | Amp docs: MCPRead Oct 30, 2026 |
| How it connects | Sign in and paste your site address. The first article is free. | Remote MCP. Amp documents remote MCP servers in settings.json under amp.mcpServers with a url and an optional headers object. | Amp 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 Amp 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.
Workspace servers in .amp/settings.json show as awaiting approval until you approve them. A workspace file is usually committed, so keep the real key in the user file.
The docs also describe adding remote servers with amp mcp remote add and a --headers flag taking JSON name and value pairs, with secret header values encrypted. The settings.json route above is the one shown with Authorization.
The docs example in settings.json is shown as an entry with the dotted key amp.mcpServers, so use that exact key.
FAQ
Yes. The docs show amp.mcpServers entries with a url and a headers object, such as an Authorization header.
From ~/.config/amp/settings.json for the user, or .amp/settings.json in a workspace.
Servers in workspace settings need explicit approval. Run amp mcp approve with the server name.
The docs list amp mcp list and amp mcp doctor.
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 Amp 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).