Connect Reader Radius to your assistant.

ChatGPT / Codex — manual installation

In Claude or Cowork, adding Reader Radius as a custom connector requires no install, no terminal, no Node.js. You generate a credential pair on our side, paste it into Cowork's connector form, and Claude can read your accounts and schedule posts on your behalf.

1. Generate your connector credentials

Sign in to Settings → Integrations and find the Use Reader Radius inside Claude or ChatGPT card. It walks you through three numbered steps: connect your social accounts, generate a credential pair, then pick where you use Claude (a Claude.ai connector tab for the browser/desktop app and a Claude Code plugin tab for the terminal). In step 2, name the credential, choose which pen names it can act on, and click Generate credential pair. We'll give you three things — keep all three handy:

We hash the secret on save and never store the plaintext. If you close the dialog before copying it, you'll need to revoke and regenerate.

2. Add the custom connector in Cowork

1. In Cowork, open Settings → Connectors → Add custom connector.
2. Name it Reader Radius.
3. Paste the MCP server URL into the “Remote MCP server URL” field.
4. Open Advanced settings. Paste the Client ID and Client Secret into their fields.
5. Click Add. If Cowork initially shows “Connection has expired”, click Connect, sign in if prompted, click Approve, and the connector finishes authenticating within a few seconds.

3. Install the plugin for skills

The connector you just added gives Claude the tools. This step adds the skills (pen-name switching, Trial Reels, Threads chains, YouTube Shorts, Reddit, campaign builder) and the /aa-post + /aa-campaign slash commands. One marketplace, two paths to install — pick whichever Claude you're using.

In Cowork

1. Settings → Plugins → click the + next to Personal.
2. Add a marketplace from URL — paste:

https://github.com/chellehoniker/claude-code-author-automations

3. Click Sync, then click the + next to Reader Radius to install. Older clients may show author-automations-social; the internal identifier is unchanged.
4. Recommended: three-dot menu on the marketplace → Sync automatically: ON so future skill updates flow without re-adding.

In Claude Code (CLI)

/plugin marketplace add https://github.com/chellehoniker/claude-code-author-automations
/plugin install author-automations-social@author-automations

4. Try it

Open a new chat in Cowork and ask:

List my connected social accounts.

Cowork should show the accounts within the selected credential's allowed pen names. From there, try “write me an Instagram post about my new book and schedule it for Friday at 9am.”

Claude Code is the developer-oriented CLI version of Claude. Our plugin contains skills and slash commands, not a bundled MCP connection. Add the hosted server separately; the skills teach Claude how to write platform-specific captions, run multi-day campaigns, switch pen names, and route to the right post type (Reel vs. Story vs. carousel) based on what you say.

1. Add the marketplace and install

Paste these in any Claude Code session:

/plugin marketplace add https://github.com/chellehoniker/claude-code-author-automations
/plugin install author-automations-social@author-automations

These commands install skills only. Keep the existing plugin ID shown above even though its display name is Reader Radius.

2. Add the MCP connection and sign in

Generate or reuse a credential pair in Settings → Integrations and choose its pen-name access. Replace YOUR_CLIENT_ID below, then run this in your terminal. The Client Secret is requested interactively rather than included in your shell history. Do not paste credentials into chat.

claude mcp add --transport http --scope user --client-id YOUR_CLIENT_ID --client-secret reader-radius https://readerradius.com/api/mcp

In Claude Code, run /mcp, select reader-radius, and authenticate. Complete the browser sign-in and approval. Start a new session and ask to list your accessible pen names before trying a write action. Already connected? Skip adding another server and retain the existing connection.

3. Try a slash command

/aa-post post a Trial Reel about my new cover, schedule for Friday 6pm

/aa-campaign 14-day launch campaign for Curses and Currents on Instagram, Threads, and TikTok

Or skip the slash commands entirely — just describe what you want in plain English. The plugin's skills tell Claude when to switch pen names, how to route a 9:16 video to YouTube Shorts vs. Instagram Reels, when to call the Threads chain feature, etc.

For Make.com scenarios, Zapier zaps, n8n workflows, custom Node/Python scripts, third-party integrations. Bearer-token auth, JSON in, JSON out, a stable v1 URL space.

1. Generate an API key

In Settings, find the API Key card and click Generate. The key is shown once — store it somewhere you can find it again. It starts with aa_sk_.

2. Make a request

curl -H "Authorization: Bearer aa_sk_..." \
  https://readerradius.com/api/v1/accounts

curl -X POST \
  -H "Authorization: Bearer aa_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hello from the API!",
    "accountIds": ["682..."],
    "publishNow": true
  }' \
  https://readerradius.com/api/v1/posts

Multiple pen names?

Pass an X-Profile-Id header to scope a request to a specific pen name. Without it, your primary pen name is used. Discover your pen name IDs by calling GET /api/v1/profiles.