Post to Facebook from Claude Cowork

Hand Cowork a week of Facebook posts as one task and it works through them: research, render, and posts held as drafts on your Page for you to check.

Hermoso is a marketing MCP server: 876+ tools over one OAuth’d endpoint that let an agent research the ads already running in a market, generate finished image and video ads, publish them, and build the paid campaigns behind them. Claude Cowork reaches all of it through one connection. This page covers one slice of that: what Claude Cowork can actually do on Facebook, and what Facebook will not let it do.

Connect Hermoso to Claude Cowork

  1. Copy the connector URL. https://app.hermoso.ai/mcp
  2. Claude → Customize → Connectors → + Add → Add custom connector. Name it Hermoso and paste the URL. Leave the sign-in option on Claude’s default: Hermoso accepts Claude’s published client identity and also registers clients automatically, so there is no client ID to create.
  3. Connect and approve. Sign in with your Hermoso account on the consent page. No key is pasted.
  4. Open Cowork and hand it the job. Cowork sees the same connector. Ask it to list your connected channels first, so you know which accounts it can reach.
  5. Ask Cowork for something. “Pull my three closest competitors’ longest-running ads and remix the best hook into a 9:16 video,” or “post this render to the channel.” The agent picks the tools; you approve the spend.

Anthropic’s help center lists custom connectors on Claude, Cowork and Claude Desktop, and Cowork itself on the paid plans: Pro, Max, Team and Enterprise. On Team and Enterprise an Owner adds Hermoso once under Organization settings, Connectors, and members press Connect. One detail decides the route: a local server in claude_desktop_config.json is not available in Cowork, so the hosted connector is the way in, not npx hermoso mcp. Read from Anthropic’s help center on 2026-10-03. Hermoso is not affiliated with or endorsed by Anthropic.

Then connect Facebook itself, once, under Settings → Connectors in Hermoso. That is an OAuth consent screen, so it is the one step that needs a browser. Everything after it is a tool call.

The Facebook tools Claude Cowork gets

  • post_to_meta: publishes text, an image, a video or a multi-photo post to the Page, and takes pageId so it never has to guess which Page.
  • schedule_post: queues the same post for a time you choose, on one calendar shared with every other channel.
  • list_meta_pages: lists the Pages the account has connected, with their ids.
  • manage_meta_post: edits the copy of a published post, or deletes it.
  • list_meta_comments / reply_to_meta_comment / moderate_meta_comment: reads the comments under a post, replies as the Page, and hides or deletes what should not be there.
  • meta_page_insights / meta_post_insights: Page-level and per-post reach, impressions and engagement.
  • upload_meta_asset: puts a finished render into the ad account’s asset library.

Facebook is also the one channel with native remote scheduling. post_to_meta takes a scheduleAt between ten minutes and thirty days out and hands the timing to Meta itself. Instagram and Threads have no such thing in Meta’s API, and passing it for them is refused rather than quietly posted immediately.

Facebook limits worth knowing before you automate anything

TextA Facebook post can run to 63,206 characters, which is effectively no limit. It is enforced when the post is created or queued, so an overlong post is refused while you are still there to fix it instead of being silently cut on the way out.
VisibilityPublic or draft. A draft is a genuinely unpublished Page post, which is the useful one for review: it exists in Meta Business Suite and nobody outside can see it. There is no unlisted and no private option: “a Facebook Page post is either published or held as an unpublished draft”.
Carousel2 slides and up, photos only. Meta publishes no maximum for attached_media that we could source, so Hermoso does not invent one and attribute it to Facebook. The only bound is ours, at 30 slides, and the refusal says whose it is: “Facebook publishes no documented maximum for attached_media, so this bound is ours, not theirs.” Video cannot ride in a Facebook photo carousel; that is a different edge on Meta’s API and Hermoso refuses rather than silently dropping the clip.
Which accountpageId. It matters the moment a brand connects more than one Page: the publish path refuses by name instead of picking one for you, and a schedule that could not carry the answer would turn that refusal into a failure hours later with nobody watching.

Try it in Claude Cowork

Ask for it in ordinary language. These are plain sentences, not a DSL:

“Plan five Facebook posts for next week from our latest product news, render an image for each, and hold all five on our Page as unpublished drafts.”

That walks find_competitors → search_meta_ads → plan_ad → render_ad → list_meta_pages → post_to_meta. How often Cowork stops to check with you is Cowork’s behaviour, not ours. Hermoso’s gates hold either way: campaigns are born paused, and spend switches and deletes need an explicit confirmation.

Claude Cowork on Facebook: the part that bites

Drafts are the natural fit for a task that runs on its own: Cowork finishes the batch, and nothing is public until you publish it from Meta Business Suite. If the brand has more than one Page connected, have Cowork run list_meta_pages at the start of the task, because the publish path refuses to guess which Page you meant.

Cowork can run shell commands, but Anthropic’s default network setting for that sandbox allows package registries rather than every domain, so the hermoso command line is not something to rely on there. The connector is unaffected: Anthropic says connector traffic keeps working whatever the sandbox’s network setting is.

Research Facebook before you post

The Meta Ad Library is the richest public creative archive there is, and search_meta_ads reads it by keyword or by page, covering both Facebook and Instagram placements. pull_competitor_ads and competitor_teardown build on it, and find_competitors works out who to point them at.

The paid half

Facebook is the deepest paid surface Hermoso has. create_meta_campaign, create_meta_adset and create_meta_ad build the whole tree with real targeting: geography down to a city radius, interests, behaviours, custom audiences and lookalikes, placements, dayparting, bid and cost caps. Everything is created PAUSED with no caller override, and the summary your agent reports is built from a read-back of what Meta actually stored, never from what was requested. Before a budget is committed, preview_meta_ad renders the real ad per placement as a link you can look at and estimate_meta_reach says how many people the targeting actually reaches. One warning that saves money: an ad set created with no locations defaults to the United States only, and the read-back says so loudly.

What Claude Cowork cannot do on its own

An agent with a budget is only useful if the blast radius is bounded, so the fence is in the server rather than in a prompt. Every ad campaign, ad set, ad group and ad is created paused, and the status switches that arm real money refuse to run without an explicit confirmation flag. Every render is quoted first (hermoso_capabilities publishes each model’s exact credit cost before anything spends). Credits are reserved before the first provider call and settled at the exact cost afterwards, so a failed dispatch refunds rather than leaving you billed for nothing. Deletes are confirm-gated too, and every campaign tree is read back from the ad platform before your agent tells you what it built.

One step is deliberately not headless: linking an account is an OAuth consent screen, so you connect the channel once in a browser. Everything after that is a tool call.

The rest of the matrix

From Claude Cowork, post to: Instagram · Threads · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Claude Cowork can publish to.

Post to Facebook from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat · Perplexity Computer · Paperclip · AI marketing in Claude

Frequently asked questions

Can Claude Cowork post to Facebook?

Yes, through the Hermoso connector you add in Claude. In Claude, open Customize, Connectors, add a custom connector with https://app.hermoso.ai/mcp and approve it with your Hermoso account. Cowork uses the same connector, and there is no key to paste. Claude Cowork then has 876+ tools, including the ones that publish to Facebook, plus the ones that research the ads already running in your market and render the creative in the first place.

How do I connect Facebook to Claude Cowork?

Two steps, once each. In Claude, open Customize, Connectors, add a custom connector with https://app.hermoso.ai/mcp and approve it with your Hermoso account. Cowork uses the same connector, and there is no key to paste. Then connect Facebook inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Claude Cowork publishes to Facebook as an ordinary tool call.

What is the Facebook caption limit when posting from Claude Cowork?

A Facebook post can run to 63,206 characters, which is effectively no limit. Hermoso enforces it when the post is created or queued, so Claude Cowork is told immediately rather than failing later when nobody is watching.

Can Claude Cowork schedule a Facebook post for later?

Yes. schedule_post queues it on one calendar shared with every other channel, with a per-channel caption if the copy should differ, and list_scheduled and cancel_scheduled read and pull it back. Facebook is one of the ten channels that queue.

Can Claude Cowork post privately or as a draft to Facebook?

Yes. Facebook is the one channel with a genuine draft: an unpublished Page post that exists in Meta Business Suite and that nobody outside can see. Hermoso refuses a visibility Facebook cannot honour at the moment you ask for it, rather than quietly publishing something weaker.

What does it cost to post to Facebook from Claude Cowork?

Publishing to Facebook costs no credits, because Meta charges nothing per API call. Credits are spent on generation: rendering the image or video the post carries. Plans are $19, $49 and $149 a month for 1,000, 3,000 and 10,000 credits, and every feature is on every plan including Free. The only exception is enterprise SSO.

Start free with 30 credits at signup and 250+ more to earn. Every feature is on every plan. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free.

Start free →   See pricing