Connect

Three ways to talk to Author Automations.

Pick the path that fits how you already work. Most authors use the Claude Cowork connector — it's the fastest setup and the tool runs as a chat. Developers grab the Claude Code plugin or the REST API. They all hit the same backend, so you can mix.

Claude Cowork

Best for non-coders. Paste a URL plus a credential pair into Cowork's “Add custom connector” form. ~3 minutes.

Recommended →

Claude Code (CLI)

For developers using Claude in the terminal. Two slash commands to install, sign in once, done.

Skim guide →

REST API

For Make.com, Zapier, n8n, or your own scripts. Long-lived API key, Bearer auth, JSON.

See full reference →

Claude Cowork — web connector

Cowork is the desktop/browser version of Claude. Adding Author Automations as a custom connector takes about three minutes — 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.

Two-step walkthrough — generate credentials, then add the connector. ~3 minutes.

1. Generate your connector credentials

Sign in to Settings and scroll to the Claude Cowork Connector card. Click Generate credential pair. We'll give you three things — keep all three handy:

MCP server URLhttps://authorautomations.social/api/mcp
Client IDstarts with aacw_ — looks like a username
Client Secretstarts with aacs_ — like a password. Shown once. Copy now or you'll need to regenerate.

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 Author Automations Social.
  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. Cowork shows “Connection has expired” — that's expected on first add. 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-campaignslash 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
  1. Click Sync, then click the + next to author-automations-social to install.
  2. 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 every platform you've connected in the dashboard. From there, try “write me an Instagram post about my new book and schedule it for Friday at 9am.”

Claude Code — terminal plugin

Claude Code is the developer-oriented CLI version of Claude. Our official plugin bundles the same remote MCP server the Cowork connector uses, plus skills that 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:

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

No git clone, no npm install, no Node.js requirement. The plugin manifest points at our hosted MCP, so you get updates the moment we ship them.

2. Sign in (OAuth, one-time)

The first time Claude calls one of the plugin's tools, it prompts you to authorize. A browser window opens to /authorize on our site, you click Approve, and the window closes. Claude Code stores the resulting access token locally and refreshes it as needed.

If Claude Code asks for Client ID and Client Secretinstead of running a browser flow, that's the manual auth path — generate a credential pair in Settings → Cowork Connector and paste them. Same credentials work for both Cowork and Claude Code.

3. Try a slash command

Single post
/aa-post post a Trial Reel about my new cover, schedule for Friday 6pm
Multi-day campaign
/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.

REST API

For everything that isn't Claude — 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

List your connected accounts
curl -H "Authorization: Bearer aa_sk_..." \
  https://authorautomations.social/api/v1/accounts
Create a post (publish now)
curl -X POST \
  -H "Authorization: Bearer aa_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hello from the API!",
    "accountIds": ["682..."],
    "publishNow": true
  }' \
  https://authorautomations.social/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.

Which credential do I need where?

Three different secrets for three different surfaces. They all authenticate to the same backend, but they're not interchangeable.

ForCredentialGenerated in
Cowork connectoraacw_… Client ID + aacs_… Client SecretSettings → Cowork Connector
Claude Code plugin (manual)Same as above — aacw_… + aacs_…Settings → Cowork Connector
Claude Code plugin (browser)None — Claude opens our /authorize pageAuto, on first tool call
REST API / Make / Zapieraa_sk_… API keySettings → API Key

Each credential is scoped to specific pen names

When you generate a Cowork credential pair or an API key, you pick which pen names that credential is allowed to act on. Default is all of your pen names; restrict at generation time when you want a credential limited to a subset (e.g., a virtual assistant who manages one pen name shouldn't see the others).

In Cowork or Claude Code, switch the active pen name by saying “switch to my [pen name]” — the plugin routes the next call accordingly, within whatever pen names the credential has access to. From the API, pass the X-Profile-Id header — call GET /api/v1/profiles to discover the IDs the credential can reach.

If something goes wrong

Cowork says “couldn't reach connector” or “authentication failed”

Almost always one of three things:

  1. The credential pair was copied with extra whitespace. Re-paste, no leading/trailing spaces.
  2. The Client Secret is from a different account than the one you signed in with on Cowork. Generate a new pair while signed into the right account.
  3. The credential was revoked or you deleted it. Generate a new pair.
Claude Code can't see my accounts after install

Two things to check:

  1. Did the OAuth approval window actually finish? Run any plugin tool (e.g. “list my accounts”) and watch for an authorize prompt. If you missed it, the plugin will re-prompt next call.
  2. Do you have multiple pen names? An empty result usually means the call went to the wrong pen name. Say “switch to [the one with accounts]” and try again.
Image upload hangs in Cowork

The plugin uploads images directly to a CDN host, and Cowork's sandbox blocks egress to most domains by default. Open Cowork's Settings → Capabilities → Allow Network Egress and switch it to All Domains. A single-domain allowlist won't catch it — the CDN uses per-bucket subdomains.

I lost my Client Secret / API key

We hash both on save and never store plaintext, so we can't look them up. Revoke the old credential and generate a fresh one in Settings. Any Cowork connector or script using the old credential will need to be updated to the new one.

Still stuck? Email [email protected] with the credential type, what tool you're trying to connect from, and the exact error. We usually reply within a business day.

Pick a path and get started

Most authors land on the Cowork connector and never need anything else. Devs grab the CLI plugin or the API. They all hit the same backend, so you can always add another later.