Hermoso is a marketing MCP server: 922+ 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. Cursor reaches all of it through one connection. This page covers one slice of that: what Cursor can actually do on Facebook, and what Facebook will not let it do.
Connect Hermoso to Cursor
- Install and sign in.
Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only innpm install -g hermoso && hermoso auth login~/.hermoso/config.json. On a machine with no browser,hermoso auth login --token hmk_…takes a key from MCP & CLI → Terminal & API keys instead. - Add it to
~/.cursor/mcp.json(or the project’s.cursor/mcp.json). No key goes in the file, becausehermoso mcpreads the sign-in above:{ "mcpServers": { "hermoso": { "command": "npx", "args": ["-y", "hermoso", "mcp"] } } } - Or use the one-click install from the MCP page. That deeplink installs the hosted URL and leaves authentication to Cursor’s own OAuth flow. Both work, they are just different prerequisites.
- Ask Cursor 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.
The block above runs the published hermoso npm package on your machine, which is why nothing is pasted and why the tool list costs nothing until a tool is called. If you use the deeplink instead, Cursor performs dynamic client registration against our authorization server and you never hold a key either.
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 Cursor gets
post_to_meta: publishes text, an image, a video or a multi-photo post to the Page, and takespageIdso 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
| Text | A 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. |
|---|---|
| Visibility | Public 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”. |
| Carousel | 2 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 account | pageId. 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 Cursor
Ask for it in ordinary language. These are plain sentences, not a DSL:
“Post the hero image from this branch to our Facebook Page as a draft, and drop the Business Suite link into the PR description.”
That walks find_competitors → search_meta_ads → plan_ad → render_ad → list_meta_pages → post_to_meta. Cursor surfaces each tool call in the composer before it runs, so a publish is a click rather than a side effect.
Cursor on Facebook: the part that bites
The useful pattern in an editor is “post it and tell me where it went”: the tool result carries the post id, and Cursor can put it straight into the PR or the release notes. Ask for a draft when the Page needs someone else’s approval. A Facebook draft is a genuinely unpublished post, not a queue entry Hermoso is holding.
Put the config in the project’s .cursor/mcp.json rather than the home directory when a repo should always run against one brand; hermoso auth login is what pins the workspace otherwise.
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 Cursor 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 Cursor, post to: Instagram · Threads · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Cursor can publish to.
Post to Facebook from: Claude · ChatGPT · Claude Code · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer · Paperclip
Frequently asked questions
Can Cursor post to Facebook?
Yes, through Hermoso's MCP server. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Cursor then has 922+ 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 Cursor?
Two steps, once each. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Then connect Facebook inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Cursor publishes to Facebook as an ordinary tool call.
Does Cursor need my Facebook password?
No. You connect Facebook to Hermoso once through an OAuth consent screen in a browser, and Cursor then reaches it as a tool call. Linking an account is the one step that is not headless; nothing after it needs a password, and no credential is ever handed to the model.
Can Cursor research Facebook before it posts?
Yes. The Meta Ad Library is searchable through search_meta_ads by keyword or by page, and it covers Facebook and Instagram placements together.
Can Cursor post a carousel to Facebook?
Yes, as a Facebook multi-photo post: two slides and up, photos only. Meta publishes no maximum for it that we could source, so Hermoso applies its own bound of 30 slides and says the bound is ours rather than attributing it to Facebook. Cursor calls the same publish tool either way, and a channel that cannot carry a carousel is refused with the real reason attached.
Can Cursor run Facebook ads as well as posting?
Yes. The full Meta campaign tree is buildable (campaign, ad set, ad, targeting, audiences, budgets), with preview and reach-estimate tools before a budget is committed.
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