LogoAI AGENT INTEGRATIONS NOW LIVE
Anthropic Claude + Genviral API

Claude social media automation

Run Claude as your social media control layer — from Claude Code, the Cowork background tab, or your own Agent SDK build. Genviral is the skill and API it uses to handle connected accounts, scheduling, publishing, analytics, and the AI media workflows that feed the next batch.

  • Works with Claude Code, the Cowork tab, and the Agent SDK
  • Genviral publishes to 10 platforms from one API key
  • Drive it via the genviral CLI or the Partner REST API
Start free with GenviralView the skill

Skill is MIT-licensed · @genviral/cli on npm

quick start
# Claude Code: drop the skill in, install the CLI$ git clone https://github.com/fdarkaou/genviral-skill.git \$   ~/.claude/skills/genviral$ npm install -g @genviral/cli# Then ask Claude:# "Use the Genviral skill to post tomorrow's Reel to Instagram."
Genviral publishes to
TikTokInstagramYouTubePinterestLinkedInFacebookXBlueskyMastodonTelegram

Every Claude surface

One integration, every way you run Claude

Claude Code, the Cowork background tab, the Agent SDK, or a raw MCP/HTTP call — they all reach the same Genviral accounts, media, and scheduling through the skill, the CLI, or the Partner API.

Skill + CLI

Claude Code

Anthropic's terminal and IDE agent. Drop the Genviral skill into ~/.claude/skills and Claude Code shells out to the `genviral` CLI for accounts, slideshows, posts, and analytics.

CLI + API

Cowork

The autonomous background tab in the Claude desktop app. Hand it a recurring brief and it runs the CLI or Partner API in its own environment — dispatch hands-off social work without keeping a window open.

CLI + API

Claude Agent SDK

Build your own headless Claude agent in TypeScript or Python. Call the `genviral` CLI from its Bash tool or hit the Partner REST API directly — then wire it into cron, CI, or a GitHub Action.

REST API

Claude + MCP / API

Any Claude that can make an HTTP request talks to the Genviral Partner API directly with a Bearer key — through an MCP server or inline fetch, no CLI install required.

Two layers

Claude reasons. Genviral executes.

Claude is great at planning, conversation, and multi-step work. Genviral is great at being the only tool it actually needs to do social.

Claude owns

  • Runs in the terminal, IDE, or desktop app

    Claude Code lives in your shell and editor; the Cowork tab runs autonomously in the desktop app. The same skill and CLI work from every surface — no rewrite to move between them.

  • Agent Skills system

    Claude loads skills from local files. Drop the Genviral skill in the right folder and Claude knows how to plan, post, render, and check analytics on demand.

  • Persistent context

    Memory and project files survive across turns and sessions. Brand voice, board lists, account rules, and the last week's performance are all there next time you open Claude.

  • Conversational handoff

    Approve, redirect, or rewrite mid-task. Claude can pause for confirmation, accept tweaks in plain English, and resume without losing the thread.

Genviral owns

  • Connected social accounts

    TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, Bluesky, Mastodon, and Telegram behind one API key — no Meta or TikTok partner approval wait.

  • AI media generation

    Slideshows, images, and videos rendered through Genviral's AI Studio. No separate model wiring — Claude calls one endpoint and gets a finished asset.

  • Cross-platform scheduling

    One queue, every platform. Idempotent posting via `external_id`, retry-safe drafts, and per-account cooldowns Claude can drive from one endpoint.

  • Analytics feedback loop

    Genviral feeds last-30-day performance back to Claude so the next batch rewrites hooks against whichever format actually outperformed.

Setup

From zero to a sample post in 5 steps

Each step links to the real surface in your dashboard. Run them once, then let Claude take the recurring work.

  1. 01Step 1 of 5

    Drop the Genviral skill into Claude's skills folder

    Claude Code and Cowork auto-load skills from your local skills directory. The Genviral skill ships an opinionated SKILL.md, slideshow workflow, defaults file, and a feedback loop tuned for social — no manual wiring required. Building on the Agent SDK instead? Point its Bash tool at the same CLI.

    View the skill on GitHub

    Clone the skill into Claude's skills directory

  2. 02Step 2 of 5

    Install the Genviral CLI

    The skill shells out to `genviral`, the same CLI any agent uses. Claude's tool calls run shell, the shell runs `genviral`, and Genviral does the rest. Prefer pure HTTP? Skip the CLI and call the Partner REST API directly.

    View on npm

    Install once, globally

  3. 03Step 3 of 5

    Create a scoped API key

    Create one key per workspace Claude is allowed to drive. Drop it into `GENVIRAL_API_KEY` in your shell profile so the skill picks it up on every session — or pass it as a Bearer token when you call the API directly.

    Create API key

    Set the key once for your shell

  4. 04Step 4 of 5

    Connect your social accounts in Genviral

    Connect TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, Bluesky, Mastodon, and Telegram once in the dashboard. Claude never touches OAuth — it just reads the account list and uses the IDs.

    Connect accounts

    Confirm Claude can see your accounts

  5. 05Step 5 of 5

    Ask Claude to draft one sample post

    From Claude Code, the Cowork tab, or your own Agent SDK build, ask Claude to generate one slideshow, review it, and create a draft post. Claude uses the skill end-to-end — you watch it work before promoting anything to public.

    Read related guides

Use cases

Six recurring Claude workflows

Each one follows the same loop: Claude plans, Genviral renders and publishes, analytics feeds the next session.

  • TikTok

    Daily slideshows from a fixed format

  • Pinterest

    Recurring infographic pins

  • YouTube

    Shorts from a shared queue

  • Instagram

    Reels from an approved media folder

  • LinkedIn

    Posts from release notes & drafts

  • Facebook

    Cross-post filler for brand-page trust

Why an API layer

Claude still needs a real execution surface

You could wire Claude into every platform's API yourself. In practice that's slow and breaks often. Here's the comparison.

Wire it yourself

  • Meta and TikTok partner approvals can take months

  • Every platform has its own auth, post settings, and quirks

  • AI assets need separate model providers and plumbing

  • Scaling to many accounts gets you shadowbanned and locked out

Genviral does this

  • Genviral fronts those approvals so Claude posts on day one

  • One endpoint per concept; Genviral maps it per platform

  • Genviral's AI Studio ships slideshows, images, and video in-API

  • Hosted, pre-warmed accounts keep posting reliable past the early stage

Read the skill source on GitHub

Guides

What to read before you wire this up

The developer surfaces are the source of truth. Each link is one of the integration points Claude calls under the hood.

FAQ

Claude social media questions

The details teams ask before handing recurring social workflows to a Claude agent.

Which Claude surfaces does this work with?

All of them that can run a shell command or make an HTTP request. Claude Code (terminal and IDE) and the Cowork background tab in the desktop app load the Genviral skill and shell out to the `genviral` CLI. The Claude Agent SDK can call the CLI from its Bash tool or hit the Partner API directly. And any Claude with HTTP access — including via an MCP server — can call the Genviral Partner API with a Bearer key. Same accounts, same endpoints, no per-surface rebuild.

How does Claude post to social media?

Claude itself doesn't ship with platform connectors. You either install the Genviral skill plus the `@genviral/cli` package, or point Claude at the Partner REST API. Claude then drives commands for accounts, slideshows, posts, analytics, and trends — Genviral handles auth, rendering, scheduling, and publishing to every supported network.

Do I need the Genviral skill, the CLI, or the API?

It depends on the surface. For Claude Code and Cowork, install the skill (SKILL.md, slideshow workflow, defaults, feedback loop) and the CLI it shells out to — that's the smoothest path. For headless Agent SDK builds or any MCP/HTTP integration, you can skip the CLI entirely and call the Partner REST API directly with your Bearer key.

Can I dispatch Claude to run social tasks autonomously?

Yes. The Cowork background tab runs in its own cloud environment, so you can hand it a recurring brief and let it execute without keeping a window open. For fully scheduled jobs, run the `genviral` CLI on cron, systemd, or a GitHub Action from an Agent SDK build, or use the Hermes Agent integration, which has native scheduled tasks.

Which platforms can Claude post to through Genviral?

TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, Bluesky, Mastodon, and Telegram. Analytics coverage is strongest for TikTok, Instagram, and YouTube. Claude publishes from your connected accounts via one API key — no Meta or TikTok partner approval wait.

Does this need an MCP server?

No. With the skill, Claude shells out to `genviral` directly — there's no separate MCP server to operate. MCP is optional: if you prefer it, you can wrap the Partner API in an MCP server and have any Claude surface call it that way instead.

Should I let Claude publish without confirmation?

Not at first. Post manually for a few days, then have Claude generate one sample post. Review the image, caption, tags, and destination. Only after the sample is right should you let Claude publish without asking. Use draft modes (TikTok MEDIA_UPLOAD, YouTube unlisted, Instagram private) for the first few runs.

Get started

Give Claude a real social media backend

Connect your accounts, scope an API key, and let Claude drive a skill and API built for generated content, scheduled posts, teams, and analytics.

Start freeAPI docs