Paperboy for Goose
Add Paperboy to Goose as a Streamable HTTP extension and let it save topic ideas and drafts straight into your project.
Set up
You will add paperboy as a Remote Extension (Streamable HTTP) with an Authorization header.
Create a key in Paperboy Settings (it starts with pb_live_).
Run goose configure and select Add Extension.
Choose Remote Extension (Streamable HTTP). Name it paperboy and enter https://paperboyseo.com/mcp as the endpoint URI.
Keep the default timeout of 300 seconds or set your own, then add a short description.
Answer Yes to "Would you like to add custom headers?". Use the header name Authorization and the value Bearer pb_live_YOUR_KEY.
Desktop instead: open the sidebar, click Extensions, then Add custom extension. Pick the Streamable HTTP type, fill in the details, add the same Authorization header, and click Add.
goose configure
What would you like to configure? Add Extension
What type of extension would you like to add? Remote Extension (Streamable HTTP)
What would you like to call this extension? paperboy
What is the Streamable HTTP endpoint URI? https://paperboyseo.com/mcp
Please set the timeout for this tool (in secs): 300
Enter a description for this extension: Paperboy SEO tools
Would you like to add custom headers? Yes
Header name: Authorization
Header value: Bearer pb_live_YOUR_KEY
Add another header? NoReplace 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
In Goose Desktop, open Extensions in the sidebar and check the toggle next to paperboy is on, or use the extensions button at the bottom of a chat. In the CLI, goose configure then Toggle Extensions lists installed extensions, and a solid mark means enabled. Then ask Goose to list the Paperboy tools it can call.
How to remove it
Disable the extension first. Desktop: click the button on the extension under Extensions and choose Remove Extension. CLI: goose configure, then Remove Extension, and select the disabled paperboy entry.
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 and pull my top search queries. Find the ones sitting on page two and save three topic ideas to topics.md in this repo.”
Uses get_sitesget_queriessuggest_topics
“Take the first topic in topics.md, write the article with paperboy, fetch it, and save the markdown into content/blog/ in this project.”
Uses write_articleget_article
“Fact-check the draft at content/blog/draft.md with paperboy and list every claim it flags, with the sources it found.”
Uses check_claims
Why
Goose adds remote servers as extensions, and only Streamable HTTP is supported. SSE is not. The docs now live at goose-docs.ai under the Agentic AI Foundation, and the old block.github.io address returns 404, so older guides point the wrong way.
Goose acts on its own by default, so set a permission mode before it can call write_article or publish_article. The extension timeout is 300 seconds, which is plenty for a call that returns an id at once. The config file holds your key as typed, so treat it as a secret.
Compare
Same engine, two ways in. Pick the one that fits how you already work.
| Feature | Dashboard | Goose | Source |
|---|---|---|---|
| Where you work | paperboyseo.com/app: sites, calendar, fact checks | Native open source AI agent: desktop app, CLI, and API | Goose docs: Using extensionsRead Oct 29, 2026 |
| How it connects | Sign in and paste your site address. The first article is free. | Remote MCP. Goose adds remote MCP servers as Streamable HTTP extensions and lets you attach custom request headers, so a bearer key works. | Goose docs: Using extensionsRead 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 Goose 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.
Goose operates autonomously by default, so it can run tools without asking. Before you let it call write_article or publish_article, set a permission mode or per-tool permissions (see Configuring Access Controls in the Goose docs).
Remote extensions must be Streamable HTTP. SSE is not supported and old SSE entries need to be migrated to streamable_http. The extension timeout (300 seconds by default) is how long Goose waits for one tool call, so raise it if a long call times out.
The headers map in ~/.config/goose/config.yaml holds the key as you typed it, so treat that file as a secret. Toggling an extension in the sidebar changes defaults for new sessions, while toggling in a chat affects only that chat.
FAQ
Yes. Goose supports Remote Extension (Streamable HTTP) entries, and config.yaml uses type: streamable_http with a uri. SSE is not supported.
In goose configure, answer Yes to "Would you like to add custom headers?" and enter Authorization as the name and Bearer pb_live_YOUR_KEY as the value. In config.yaml, put the same pair under the extension's headers map.
Goose runs tools without approval by default. Configure the Goose permission mode and tool permissions, which the extensions docs point to under Configuring Access Controls.
Disable the extension first, then remove it. In Desktop use Remove Extension on the extension's menu, and in the CLI use goose configure and Remove Extension.
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 Goose 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).