STOS + Reader Radius: the social handoff

Install both plugins and authenticate both MCP connections in Claude or ChatGPT.

Two products working together

STOS supplies writing, story bibles, titles, and author-business context. Reader Radius supplies social campaigns, posting, and scheduling. The STOS social-handoff skill intentionally calls Reader Radius tools; it is not an error or a workaround.

Complete the four-part setup

  1. Install the StorytellerOS plugin for guided STOS workflows.
  2. Add and authenticate the STOS MCP connection: follow Claude setup or ChatGPT setup.
  3. Install the Reader Radius plugin using its Settings installation instructions at readerradius.com.
  4. Add and authenticate the Reader Radius MCP connection with your Reader Radius credentials, then enable both products in the conversation.

Installing either plugin does not automatically install or authorize its MCP connection or the other product. Each product retains its own credentials and access checks. Never paste secrets into chat.

Choose the pen name first

  1. Call stos_pen_names_list and match the user's requested identity.
  2. The social-handoff skill reads the pen name's linked Reader Radius profile and uses it with the matching aa_* tools. If no profile is linked, finish the Reader Radius setup first.
  3. List connected accounts before creating content or a campaign.

If social tools are missing

Check that the Reader Radius plugin is installed, its MCP connection is authenticated, and both products are enabled in the conversation. A working STOS connection alone does not complete the social-handoff setup.

STOS-native ads tools

The STOS MCP catalog also exposes the following native ads operations. Their availability does not replace the Reader Radius installation used by the social-handoff skill. Pass the selected STOS penNameId to scoped STOS operations.

  1. Read campaigns and attribution with stos_ads_campaigns_unified.
  2. Use title and Media Studio tools to ground the campaign in the user's books and assets.
  3. Draft with stos_ads_creative_draft, then present objective, success metric, audience, creative, schedule, and total budget for review.
  4. Create with stos_ads_create. Use PAUSED unless the user explicitly approves immediate spend.
  5. Use recommendations as review-only guidance. Never change spend from a recommendation without confirmation.

Attribution boundaries

Amazon-attributed revenue is valid only for Amazon Ads. Do not subtract spend from other networks from it or describe that result as blended profit. Retailer analytics provides a separate business-level lens.

Spend safety

Creating, activating, increasing a budget, or deleting a campaign requires an explicit user decision. Read and analysis tools do not make changes. Mutating calls are idempotent so a retry cannot silently create duplicate spend.