Post to a Facebook Page from Claude or ChatGPT with an MCP server

Is there an official Facebook MCP server?

Yes, for advertising only. Meta’s Ads MCP server, in open beta since April 29, 2026, signs in with your Meta business login and handles reporting, campaigns, catalogs and tests. None of its tools publishes an ordinary post to a Page. For Page posts, people use community servers that take a Page token, or a publishing service.

Read on 1 October 2026 from each project’s own page. Descriptions of other servers are their own claims; Mellow has not tested them.

A Page token pasted into a config file works until it expires or leaks, and it carries whatever that token allows. Hub keeps the Page connection on its side, and the assistant gets only the permissions and channels you approve, for the time you choose.

What Facebook account do I need?

A Facebook Page you administer. Personal timelines cannot be published to through the API. You sign in with the Facebook account that manages the Page, and Hub posts as the Page. If the same Page is linked to an Instagram professional account, connect Instagram as its own channel to post to both in one request.

1. Open Accounts in Hub and choose Facebook, or ask the assistant to call connect_channel with platform set to facebook. That tool only returns a link and an instruction for a person. It needs the channels:connect permission.
2. Open the link and sign in to Facebook yourself. Hub never sees your Facebook password.
3. Tell the assistant you are done. It calls list_channels with refresh: true and uses the returned channel ID, which begins with spc_. A username is not a substitute for that ID.

Connect Claude, ChatGPT, Cursor or another MCP client

Every client uses the same server URL, https://www.mellow.world/mcp, over Streamable HTTP. A client signs in with OAuth 2.1 (dynamic client registration and PKCE) or sends an owner-created Hub API key as a Bearer token. Menus change between client versions, so the official guides linked below describe the current screens. The last column says only what Mellow itself has tested, on any network.

1. Add the server in your client and select Connect. Sign in to Mellow if asked. Hub’s consent screen names the app that is asking.
2. Choose the permissions the task needs (below), select your Facebook channel, choose review or autopilot, a daily ceiling and an expiry, then approve.
3. Back in the client, run the read-only check from the prompts below. Confirm the profile, the mode and the Facebook channel ID. Agents shows the grant’s permissions, channels and expiry.
4. If a client cannot complete OAuth, create a key in Agents and set it as the client’s Authorization: Bearer header, from its secret settings or an environment variable. Never paste a key into a chat.

Which permissions to approve

The consent screen arrives with every permission the assistant asked for already ticked, except spending AI credits. Untick anything it should not have.

What you delegate, and how to take it back

Hub treats an assistant’s access as a delegation you give once, with limits: the permissions, the channels (the ones you select, or explicitly all), review or autopilot, a daily ceiling of 1 to 1,000 posts (50 by default) and an expiry of 1, 7 or 30 days (30 by default). Autopilot is the default: the assistant publishes on its own within those limits. Choose review and each post waits for you to approve it in Hub. A key or a connected app cannot approve its own post.

Hub records the posts an assistant creates or has refused, approvals, reschedules, cancellations and connection attempts in a journal you read in Agents. Revoking a key or a connected app takes effect on its next request. Publishing always needs an idempotency key, so a retried request cannot publish twice.

Facebook rules Hub checks before anything is sent

This table is generated from the registry that validate_post enforces, the same one behind the rules for every network. These are Hub’s input rules; Facebook still judges the media itself when it fetches it.

Choose where the post goes with options.facebook.placement: timeline for the feed, reels for one video, stories for exactly one item. Facebook’s own Reels publishing API accepts videos of 3 to 90 seconds, while the Facebook app now takes Reels of any length; Hub does not check duration, so a long Reel may still be refused when Facebook fetches it (Meta for Developers, read on 1 October 2026).

Meta publishes no character limit for Page posts. Hub checks 63,206, the figure reported elsewhere.

When validate_post refuses the post

Read ok, issues and notes in the result. The check publishes nothing and reports every problem at once, each with its field and, for a network rule, its channel. Fix them together and validate again.

Other refusals concern the request or the grant: schedule_in_past (use a future time with a UTC offset), insufficient_scope (approve a delegation with the missing permission), channel_out_of_scope (the channel is not in the grant), and at creation daily_limit_reached and idempotency_key_reused. A passing check is not proof of publication: Facebook can still refuse the media or the account. The free post checker runs the same input rules on a draft before you connect anything.

Prompts you can paste

Replace the bracketed parts. Each prompt names the tools to call, so the assistant does not have to guess the order.

Use only Mellow Hub. Call whoami, then list_channels, then list_platforms.
Tell me my Facebook Page's channel ID, whether this connection is in
review or autopilot mode, how many posts it may still create today, and
Facebook's rules. Do not create anything.

Use Mellow Hub. Post the video at [public https URL of an MP4] as a Reel
to my Facebook Page and my Instagram account, with this caption:
[caption]

Call register_media on the video. Set options.facebook.placement and
options.instagram.placement to "reels". Call validate_post and fix every
issue. Then call create_post once with idempotencyKey "reel-[short-name]-1"
and call get_post. Report each target's status and link separately.

Use Mellow Hub. Schedule the images at [public https URLs] as one feed
post on my Facebook Page for [time] on [date] in [your timezone], with this
text: [text]

Write scheduledAt with an explicit UTC offset. Validate first, then call
create_post once with idempotencyKey "fb-[date]-[time]", then get_post.

Media has to be reachable at a public https URL when Facebook fetches it. An agent that can make HTTP requests, such as Claude Code or a script of your own, can instead call request_upload_url, send a local file with PUT to the returned uploadUrl and use the returned mediaUrl. An assistant that only has Hub’s tools cannot send file bytes itself.

Publish once, then read the Facebook result

create_post is the step that publishes or schedules. It needs an idempotencyKey of 8 to 120 letters, digits or the characters . _ : -, stable for this post. If the response is lost or times out, send the same request with the same key: Hub returns the original post instead of making a second one. Reusing a key for different content is refused.

Under a review-mode grant the post comes back as pending_review and waits until you approve it, signed in, in Hub. Under autopilot it goes out at scheduledAt, or immediately without it. Always write scheduledAt with Z or an explicit UTC offset.

Then call get_post and read the Facebook entry in targets, not only the post’s status. publishing means Facebook has not reported a result yet; published comes with the post’s link; failed comes with the network’s message. In a post to several networks each target settles on its own and the post can end partial: republish only the failed channel, with a new key. Once Facebook has published a post, Hub cannot edit or delete it; cancel_post works only before it goes out.

Each destination counts once against your plan: one post to Facebook and two other networks is three publications. Validating, drafting and connecting work without a plan; publishing needs an active one. See plans.

What Mellow has tested with Facebook

Production records on 1 October 2026 show four Facebook publications through Hub between September 5 and October 1, each reaching published with a public link, all on one Page. Two came through Hub’s MCP endpoint from a Claude Code session using an owner-created key: a Reel on September 29, posted together with Instagram, Threads, LinkedIn, X and TikTok, and a Reel on September 30 that had been scheduled the evening before and went out at its set time, after Claude’s claude.ai connector had moved that time. On October 1 a Reel created with an owner-created key on September 30 at 15:59 UTC for 12:30 UTC went out at 12:32 UTC, together with Instagram, Threads, LinkedIn, Pinterest and X, with nothing changed in between.

Not tested yet: Facebook Stories through Hub, photo carousels on a Page, and connecting through ChatGPT or Cursor.

Questions

Related

• Instagram MCP guide: photos, carousels and Reels on the account linked to your Page.
• Threads MCP guide.
• Publish to social media with an MCP server: the workflow for every network.
• Before an AI agent posts: an MCP checklist.
• API and MCP reference and rules for every network.
• Plans: each destination counts once against the monthly publications.