socialclaw

SocialClaw is the public home for:

• the socialclaw npm CLI

• the OpenClaw and ClawHub skill bundle

• the Claude Code plugin and /socialclaw command asset

• public usage docs, provider notes, and schedule examples

The hosted SocialClaw service lives at:

• https://getsocialclaw.com

Install

npm install -g socialclaw
socialclaw login
socialclaw accounts list --json

Install as an AI agent skill (Claude Code, Cursor, Cline, Codex, and more):

npx skills add ndesv21/socialclaw

Related MCP server: atlas-social-mcp

What the CLI covers

• workspace API key login and hosted dashboard bootstrap

• browser OAuth connect plus manual Discord and Telegram connect

• hosted asset upload and deletion

• schedule validation, campaign preview, apply, inspect, clone, and draft publishing

• post, run, attempt, analytics, job, usage, and health inspection

• provider-side deletion for supported published posts

• Claude Code command installation through socialclaw install --claude

CLI at a glance

socialclaw login
socialclaw accounts list --json
socialclaw assets upload --file ./image.png --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --json
socialclaw posts delete --post-id <post-id> --json

____             _       _      ____ _
/ ___|  ___   ___(_) __ _| |    / ___| | __ ___      __
\___ \ / _ \ / __| |/ _` | |   | |   | |/ _` \ \ /\ / /
 ___) | (_) | (__| | (_| | |   | |___| | (_| |\ V  V /
|____/ \___/ \___|_|\__,_|_|    \____|_|\__,_| \_/\_/

socialclaw login
socialclaw accounts list --json
socialclaw assets upload --file <path> --json
socialclaw campaigns preview -f <schedule.(yaml|yml|json)> --json
socialclaw validate -f <schedule.(yaml|yml|json)> --json
socialclaw apply -f <schedule.(yaml|yml|json)> --json
socialclaw posts get --post-id <id> --json
socialclaw posts delete --post-id <id> --json
socialclaw status --run-id <id> --json
socialclaw analytics post --post-id <id> --json

Watch the Demo

Built for Agent-Driven Publishing

Authentication and access

Running socialclaw login without an API key opens the hosted dashboard so the user can:

• sign in with Google

• connect social accounts

• create or copy a workspace API key

• activate a trial or paid plan for CLI and API access

Important:

• the CLI works against a deployed SocialClaw workspace via API key auth

• an API key alone is not enough for agent execution; the workspace must also have an active trial or paid plan

• if a command returns plan_required or subscription_*, go to https://getsocialclaw.com/pricing or https://getsocialclaw.com/dashboard

Quick start

socialclaw login
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts list --json
socialclaw accounts capabilities --provider pinterest --json
socialclaw accounts connect --provider pinterest --open
socialclaw accounts connect --provider discord --webhook-url <webhook-url> --json
socialclaw accounts connect --provider telegram --bot-token <bot-token> --chat-id @yourchannel --json
socialclaw assets upload --file ./image.png --json
socialclaw campaigns preview -f schedule.json --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --json
socialclaw posts delete --post-id <post-id> --json
socialclaw workspace health --json
socialclaw usage --json

Agent integrations

MCP server

The package ships a Model Context Protocol server. Any MCP client (Claude Code, Claude Desktop, Cursor, and others) gets 17 validation-first publishing tools over your connected workspace accounts: list accounts and capabilities, upload media, validate and preview schedules, apply with idempotency keys, publish drafts, and inspect posts, attempts, runs, analytics, usage, and health.

Claude Code:

claude mcp add socialclaw \
  --env SOCIALCLAW_API_KEY=sc_live_your_key \
  -- npx -y socialclaw mcp

Claude Desktop, Cursor, and other JSON-configured clients:

{
  "mcpServers": {
    "socialclaw": {
      "command": "npx",
      "args": ["-y", "socialclaw", "mcp"],
      "env": {
        "SOCIALCLAW_API_KEY": "sc_live_your_key"
      }
    }
  }
}

If you have already run socialclaw login --api-key <key>, the server reuses the saved credentials and the env block is unnecessary. See getsocialclaw.com/mcp for the full tool list.

Claude Code plugin

Install the packaged Claude Code plugin from inside Claude Code:

/plugin marketplace add ndesv21/socialclaw
/plugin install socialclaw@socialclaw

This installs the marketplace plugin from skills/socialclaw/ with metadata from .claude-plugin/. It is the cleanest option if you want Claude to auto-invoke SocialClaw when a user asks to connect accounts, upload media, schedule posts, inspect delivery, or check analytics.

Claude slash command and skill file

If you want the explicit /socialclaw command instead of the full plugin flow:

socialclaw install --claude

That installs the bundled command file from skill/claude/socialclaw.md into ~/.claude/commands/socialclaw.md.

Use this path when you want a lightweight Claude Code setup that:

• exposes one clear SocialClaw command

• keeps the workspace API key flow explicit

• still lets Claude use the same hosted SocialClaw API and CLI workflow

OpenClaw and ClawHub

The OpenClaw-compatible skill bundle lives in skill/.

It is designed for OpenClaw and other compatible agent runtimes that can load a SKILL.md, work from a workspace API key, and call either:

• the SocialClaw HTTP API directly

• the socialclaw CLI as a client for the hosted service

This is the bundle to publish to ClawHub for OpenClaw discovery.

Other agents

SocialClaw is not limited to one agent framework. The repo also includes an agent manifest in skill/agents/openai.yaml, and the CLI works well for any runtime that can execute shell commands or make HTTP requests.

That makes SocialClaw a good fit for:

• Codex and terminal-native agent workflows

• Claude Code via plugin or command file

• OpenClaw and ClawHub skills

• custom internal agents that need one stable publishing surface for social channels

In practice, all of these share the same model:

• connect customer accounts inside SocialClaw

• create a workspace API key

• upload media, validate, apply, inspect, analyze, and optionally delete supported posts through the hosted service

Supported providers

• X

• Facebook Pages

• Instagram Business

• Instagram standalone professional accounts

• LinkedIn profile

• LinkedIn page

• Pinterest

• TikTok

• Discord

• Telegram

• YouTube

• Reddit

• WordPress

Pinterest is exposed as the pinterest provider in the public CLI and skill bundle. Its main publish target is board-centric, with support for standard pins, video pins, multi-image pins, board creation and section or catalog discovery, plus pin and account analytics. Product, collection, and idea surfaces should be treated as capability-gated or beta rather than assumed for every workspace.

TikTok supports one video or one photo gallery per post. Photo galleries can include up to 35 images and expose autoAddMusic plus photoCoverIndex; selecting a specific TikTok song or sound is not available through TikTok's Content Posting API. For photo galleries, normalize images before upload, preferably to 1080x1920 JPEGs for vertical slides or another standard TikTok-compatible aspect/size. Oversized or unusual image dimensions may pass SocialClaw validation and initial TikTok acceptance, then fail later with picture_size_check_failed; reconcile photo posts after publish to confirm TikTok reports PUBLISH_COMPLETE.

Publishing

Bump the version with npm version:

npm version patch
git push && git push --tags
npm publish --access public

To sync reference files manually after editing skill/references/:

npm run sync:references

Notes

• Users connect accounts inside the hosted SocialClaw dashboard.

• The dashboard and API live at https://getsocialclaw.com.

• The npm package ships the CLI, skill docs, Claude Code plugin, and command asset.