Publish and schedule from Claude, ChatGPT, or any AI agent

Re-run the sign-in for the server in your client (Claude Code: /mcp → viralfarm → Authenticate; Codex: codex mcp login viralfarm). If you used a key, check it is not revoked under Settings → API Keys and that it is sent as an Authorization: Bearer header. A 401 from the server means the key or token is missing, revoked, or malformed; create a fresh key and try again.

Accounts are connected in the ViralFarm web app, not from chat: open Home → connect an account, finish the platform’s own sign-in, then ask your assistant to list accounts again. An account that shows as disconnected in the app was revoked on the platform side — reconnect it there.

Each generation deducts credits when it starts (slideshow 4, reel 2, pin 1) and refunds slots that fail on our side. Credits reset to your plan’s allowance on each paid invoice and do not roll over. Check the balance with get_me or under Settings, and upgrade or wait for the next cycle. Uploading and scheduling existing content does not use credits.

Ask for the failed post (list_posts) — the record carries the platform’s error. Common causes: a token the platform expired (reconnect the account), media the platform rejects (format, size, or aspect ratio), missing required options such as a Pinterest board or YouTube visibility, or a paused subscription. Fix the cause and use retry_post, or retry from the queue in the app. Publishing is paused while a subscription is inactive and posts are marked failed until you resubscribe and retry them.

The ViralFarm MCP server is a hosted Model Context Protocol endpoint (https://www.myviral.farm/api/mcp) that lets AI assistants such as Claude, ChatGPT, Cursor, and Codex generate social media posts and schedule them to your connected accounts. Connect it once and your assistant can create slideshows and Pinterest pins, upload your own media, and publish or schedule to TikTok, Instagram, Pinterest, LinkedIn, Threads, Facebook, YouTube, and X — all from chat.

Yes. With ViralFarm connected, Claude, ChatGPT, or any MCP-capable agent can publish or schedule posts to TikTok, Instagram, Pinterest, LinkedIn, Threads, Facebook, YouTube, and X. Ask in plain language — “post this to my TikTok drafts now” or “schedule it to Instagram tomorrow at 6pm” — and the assistant is instructed to confirm the choices that matter, such as live vs drafts on TikTok, before it calls the publish tool. Whether it pauses for your approval depends on your assistant's settings: ViralFarm does not enforce a confirmation step on its side, so treat an instruction to publish as final.

Pick your app on this page and follow the two-step setup. Claude and ChatGPT connect by signing in with OAuth as a custom connector; Cursor, Windsurf, Cline, Claude Code, Codex, and other MCP clients use the same server URL, with an API key for clients that do not support OAuth. Setup takes about two minutes. You need a ViralFarm account on the 7-day free trial or a paid plan: the trial requires a card and converts to the paid plan unless you cancel; generating posts uses your credits, and publishing or scheduling requires an active subscription plus at least one social account connected in the ViralFarm app.

Any MCP-capable agent: Claude (web, desktop, and Claude Code), ChatGPT (web, mobile, and Codex), Cursor, Windsurf, Cline, and custom agents built on the Claude or OpenAI SDKs. Developers can also call the ViralFarm REST API directly, documented at https://www.myviral.farm/api/v1/openapi.

Yes. Ask for a slideshow or Pinterest pin from any link, topic, or text and ViralFarm builds it on templates modeled on real viral posts. Describe the look in plain words — “dark and moody”, “use my product photos”, “make it 8 slides” — and the assistant picks the matching template, photo pack, or setting. Every post comes back with a View & edit link so you can tweak it in the editor before it goes out.

No. Generating from chat uses the same credits as the ViralFarm app: 4 credits per slideshow, 2 per reel, and 1 per pin. There is no separate charge for connecting an agent. Credits come with the paid plan (400 per month on Pro) and start with the 7-day free trial, which requires a card and converts to the paid plan unless you cancel before it ends.

Yes. Ask your assistant to open the upload picker, then choose photos or videos there. If your chat client cannot show it, your assistant gives you a browser-upload link instead. Large files upload directly from your browser and interrupted uploads can resume; return to chat when finished. The picker accepts up to 1 GiB per file, subject to storage limits. Agents with access to files on your computer, such as Cursor, can also upload them directly. The 3 MiB limit applies only to the small-file inline upload fallback. Each social platform still has its own file, format and duration limits.

ViralFarm does not enforce a confirmation step on its side: when your assistant calls the schedule tool, the post is scheduled or published right away, so treat an instruction to publish as final. What keeps a surprise post from happening is, first, the tool instructions, which tell the assistant to confirm the choices that matter, such as live vs drafts on TikTok, the Pinterest board, or the YouTube visibility, before it calls the tool; second, your assistant's own tool-approval prompts, since Claude and ChatGPT ask before running a tool that changes something unless you have allowed it; and third, safe defaults, such as sending TikTok posts to your drafts. Live TikTok posts default to visible to everyone with comments and music on. You can always ask what is queued and cancel anything that has not published yet, in chat or in the ViralFarm app.

Revoke its key under Settings → API Keys in the ViralFarm app. Sign-in (OAuth) connections appear there too, named after the app, and can be removed the same way.

Yes, and which credentials you need depends on what runs the job. Scheduled tasks that run inside the assistant itself, such as ChatGPT scheduled tasks or Claude's scheduled routines, use the ViralFarm connector you already authorized: the OAuth sign-in happens once, interactively, and later runs reuse that connection without anyone present. A job you launch separately, such as a cron job, launchd timer, or CI run, has no access to that connection, so it needs credentials in its own environment: create a key under Settings → API Keys in the ViralFarm app and either call the ViralFarm REST API with it or add the MCP server with the key as a header or environment variable (Claude Code: claude mcp add --transport http viralfarm https://www.myviral.farm/api/mcp --header "Authorization: Bearer vf_your_key_here"; Codex: bearer_token_env_var in config.toml). And if the job only publishes on a timetable, you may not need one at all: ask your assistant once to schedule a week of posts and ViralFarm publishes them at the right times by itself.

Yes. Everything the MCP server does is also available over the ViralFarm REST API — generations, posts, accounts, and media — with an OpenAPI spec at https://www.myviral.farm/api/v1/openapi. Use it from your own code, any agent framework, or any unattended job such as a cron or CI run. Authenticate with an API key from Settings → API Keys; GET /api/v1/me returns your account plus a short list of the endpoints to start from.