Facebook MCP Server: Post to a Facebook Page From Claude and ChatGPT

A Facebook MCP server is a small program that gives an AI assistant tools for Facebook. Claude, ChatGPT, Claude Code and Cursor all speak the Model Context Protocol, so once a server is connected the assistant can call a tool such as "publish a post to my Page" or "list last week's posts". You ask in plain words, the assistant picks the tool, and the server talks to Facebook on your behalf.

The search results for "facebook mcp" mix up three very different things. Some people want to run Facebook and Instagram ads from Claude. Some want to post to a Facebook Page they manage. A few want to post into a Facebook group or on their personal profile. Meta treats each of these differently, and the answer to "which Facebook MCP server should I use" depends on which of the three you mean.

This page sorts them out. It covers the official Meta ads MCP server and what it does not do, the Graph API rules that any Page posting server has to follow, why group posting is closed to every outside app, what the popular GitHub servers ask you to hand over, and how to post to a Facebook Page from Claude or ChatGPT step by step, with Spreadcast as the worked example.

If you mainly want help with what to post, the Facebook post generator page covers post sizes, captions and examples for an app's Page. Instagram has its own API and its own page: the Instagram MCP server guide. For every network side by side, see our roundup of the best social media MCP servers.

Yes, but only for ads. On October 17, 2026, the one MCP server Meta runs itself is its ads MCP server. Meta's Ads MCP server overview describes it as a server hosted by Meta at mcp.facebook.com/ads that works with any MCP compatible AI agent. It sorts its tools into seven groups: reporting, ad creation and management, catalogs, signals and datasets, help and troubleshooting, A/B tests and lift studies, and activity logs. None of those groups publishes an ordinary post to a Facebook Page.

The permissions confirm it. Meta's getting started page for the ads MCP server lists the permissions a user token needs: ads_mcp_management, ads_read, ads_management, catalog_management, business_management, pages_show_list and instagram_basic. Missing from that list is pages_manage_posts, the permission Meta's Pages API guide to posts requires before an app can publish to a Page. So the official Facebook MCP server can launch a paid ad that shows on Facebook, but it cannot put a free post on your Page's timeline.

Every Facebook MCP server for organic posting is therefore built by someone other than Meta. The careful ones call Meta's official Graph API with a token you approve on Facebook's own consent screen. The risky ones skip the API and drive a logged in browser. The sections below show how to tell them apart before you connect one.

Meta announced its ads AI connectors in its business news post on Meta ads AI connectors, dated April 29, 2026, and describes them as in open beta. The connectors are an MCP server and a command line tool. The post lists reporting, campaign management, catalog management and signal diagnostics, and says the MCP route needs no developer credentials, API setup or coding.

A July 16, 2026 update to the same post added two things. Developers can now connect any AI application to Meta ads through their own developer app, and business portfolio admins can set rules that limit what AI agents may do on an ad account, such as changing budgets or updating catalogs. Set those rules before you hand an assistant your ad account.

So if you searched for "facebook ads mcp claude" or "is there a meta ads mcp for claude", the answer is yes, and it comes from Meta. Third party ads servers exist too. Pipeboard's Meta Ads MCP guide describes a hosted, source available server on Meta's Marketing API with a free plan, for Claude, ChatGPT, Cursor and other clients. Like Meta's own server, it covers campaigns, ad sets, ads, creatives and insights, not organic Page posts.

Spreadcast does not run ads. It makes and publishes organic posts. If you also need ad pictures for a campaign you run yourself, the ad creative generator page covers that side.

The most useful thing to understand about a Facebook Page MCP server is the token. Facebook does not let an app post as a Page with your personal login. It wants a Page access token, which the Pages API overview describes as unique to each Page, app user and app. The usual flow is: you sign in with Facebook Login for Business, the app gets a user token, and then it asks Facebook for a token for each Page you allowed.

How long that token lasts decides how often your server breaks. Meta's page on long lived tokens says default user and Page tokens are short lived and expire in hours, a long lived user token generally lasts about 60 days, and long lived Page tokens have no expiration date, though they can still stop working when certain things happen, such as a password change. A server that copies a token out of the Graph API Explorer and never swaps it for a long lived one stops posting the same day.

Permissions are the second thing to check. For posting, a server needs pages_manage_posts plus its two dependencies. It does not need your ad accounts, your messages or your business settings. If a Page posting server asks for those on Facebook's consent screen, ask why.

There is a third detail that catches people who build their own app. While a Meta app is in development mode, the Pages API overview says it can request any permission from people who hold a role on the app. That is why a home made server works perfectly for its author. The moment someone without a role tries it, the Page permissions need App Review and Advanced Access, and Meta's permission reference says business verification is required for every app that requests Advanced Access.

It depends which Meta page you read, which is worth knowing before you plan a month of posts. Meta's Pages API guide to posts says the publish date must be between 10 minutes and 30 days from the time of the request. The Page feed reference gives the same field a window of 10 minutes to 75 days. For Reels, the Reels publishing guide asks for more than 10 minutes and within 29 days.

In practice, a server that hands scheduling to Facebook should stay inside the shortest of these windows, 10 minutes to 29 days, or expect some posts to be refused. A server that keeps the post on its own calendar and publishes it at the planned time is not bound by Facebook's window at all, because to Facebook it is simply a post published now.

Spreadcast works the second way. A Facebook post waits on your Spreadcast calendar until its time, then goes out. That is also why an approved draft can sit in Spreadcast for longer than a month without being rejected. How far ahead you can schedule in Meta Business Suite itself is covered on the Facebook post generator page.

No MCP server can post to a Facebook group through Meta's API today, and none has been able to since spring 2024. Meta's announcement of Graph API v19, dated January 23, 2024, says the Groups API is deprecated in v19 and would be removed from all versions 90 days later, which falls on April 22, 2024. The deprecation covers all of its permissions, including publish_to_groups and groups_access_member_info.

That change ended group posting for every scheduling tool, not only for small projects. If a Facebook group MCP server promises to post into your groups, there are only two ways it can do it: it drives a browser logged in as you, or it is out of date and fails. Either way, it is not using an API Meta still offers.

The browser route has a cost. Facebook's Terms of Service, effective January 1, 2025, say you may not access or collect data from Meta's products by automated means without Meta's prior permission, and ask you not to share your password or let others use your account. An MCP server that types into Facebook as you, or holds your session cookies, does both.

Spreadcast does not post to Facebook groups. If a group matters to your app, post there by hand, ideally with something written for that group rather than a copy of your Page post.

No, not through the API. Meta's developer post on platform product changes, dated April 24, 2018, deprecated the publish_actions permission, the one that let apps post to a person's own timeline. Apps already approved could use it until August 1, 2018, and no new apps were approved after that. Meta pointed developers to its Share dialogs instead, where the person presses the button themselves.

So a Facebook MCP server can post as a Page you manage, never as you. If your app has no Page yet, create one and give yourself admin access: it takes a few minutes and is the only route an assistant can publish to. Anything that claims to post to your profile from Claude is driving a browser.

Searches for a Facebook Marketplace MCP server or a Facebook Messenger MCP server come from different jobs again. Marketplace listings are not Page posts, and the Pages API pages listed on this page do not describe a way to publish them, so treat any Marketplace server with the same caution as a group server and ask how it reaches Facebook.

Messages are a separate part of Meta's platform with their own rules for when a Page may reply. Some open source Page servers include a tool for sending a direct message from the Page. Spreadcast does not read or send messages.

An open source Graph API server is honest about what it does, but look at the tool list before you connect it. A server with delete_post, bulk_delete_comments and send_dm_to_user gives the assistant real power over your Page. An assistant that misreads "clean up the comments on yesterday's post" can delete things you cannot get back. If you only want to post, prefer a server, or a configuration, that leaves those tools out.

The token is the second risk. A Page token in a .env file is a key that can post, edit and delete as your Page for as long as it lives, and a long lived Page token has no expiry date. The MCP security best practices warn that local servers run with the same privileges as the client and may be reachable by other processes on your machine, and they list broad, bundled scopes among the common mistakes. Keep the file out of version control, give the token only the Page permissions it needs, and revoke it in Facebook's business integrations settings when you stop using the server.

The third risk is drift. Meta retires Graph API versions on a schedule. Meta's versioning guide says each version works for at least two years, and that calls to a retired version are sent to the next oldest version still running, which can change behavior without warning. The latest version on that page today is v26.0. A server nobody has updated in a year may still run, just not the way its README says.

Browser servers add a fourth: the account itself. When Facebook restricts an account for automated activity, it is your Page and your profile that pay, not the project. For an app whose Page is a main way to reach users, that is a poor trade for saving a few minutes a week.

Spreadcast is a hosted Facebook MCP server for posting, built for people who make App Store apps. You connect your Facebook Page once in Spreadcast, and Spreadcast once in your assistant. The difference from a plain posting server is that Spreadcast also makes the post: it designs the picture or the carousel in your app's brand, writes the Facebook caption, and saves the result as a draft for you to approve.

On the Facebook side, Spreadcast signs you in through Facebook Login for Business, where you choose which Pages to allow. It asks for three permissions: pages_show_list to see your Pages, pages_read_engagement to read them, and pages_manage_posts to publish. It does not ask for ads, messages or business settings, and it never sees your Facebook password. If you allow several Pages, the first is used and you can switch to another in Accounts. If the account manages no Pages, Spreadcast says so and asks you to create one or to be added as an admin.

Spreadcast keeps the long lived Page token that Facebook issues, so there is no 60 day sign in cycle. If you change your Facebook password or remove the app, Spreadcast notices that the account has signed out and asks you to connect again.

A Spreadcast Facebook post can be text alone, text with one photo, text with 2 to 10 photos in one post, or text with one video you upload. Several photos go up to the Page unpublished first and are then attached to a single post, so followers see one post rather than a burst of separate photos. A video goes to the Page's videos edge, and Facebook shows the post once it has finished processing.

The pictures come from the same design code as the Spreadcast app. A single post comes in one of 11 kinds, such as feature, launch, stat or tutorial, in your app's colors, fonts and logo, with a real screenshot of your app in an iPhone frame. A carousel is 3 to 8 slides at 1080 by 1350 pixels in one look, and on Facebook those slides go out as one post with several photos. Spreadcast makes no AI photos and no video, so a video post uses a file you already have.

The caption is written for Facebook rather than copied from Instagram. Spreadcast's instructions for Facebook ask for one to three short, conversational paragraphs under 600 characters, at most two hashtags, and allow a closing question to the reader. It never invents numbers, quotes or features that are not in your notes or your app's listing.

Then it stops. Every new connection saves drafts. A draft waits on your Spreadcast calendar until you approve it, and only then does Spreadcast publish it at the planned time. If you choose to let the connection publish as well, the assistant is told to show you the post, the network and the time and ask before it schedules anything. Scheduling and publishing need the Pro plan.

Facebook is one of the networks Spreadcast posts to. The same draft can also go to Instagram, LinkedIn, Threads, Pinterest, TikTok, YouTube, Bluesky, Telegram channels, Discord channels and Mastodon, each with its own caption.

Searches for a Facebook MCP for Claude Code usually come from developers who want posts to go out from where they work. Claude Code's MCP documentation shows one command to add a remote server over http, and says that for servers that sign in with OAuth you then run /mcp inside Claude Code and finish in the browser. A server added that way stays private to one project unless you choose the project scope, which writes it to a .mcp.json file your team shares, or the user scope, which loads it in every project.

For Spreadcast, add a remote http server named spreadcast with the address spreadcast.app/api/mcp and run /mcp to sign in. Cursor takes the same address. If you prefer a key, create one in Settings, AI Assistants and send it as a Bearer header. A key saves drafts only unless you switch on Can Publish Posts for it. Keep keys and Page tokens out of the shared .mcp.json file.

An open source server from GitHub fits here too, because it runs as a local program. The full commands for both editors are on the social media MCP server page.

People search for a Facebook MCP server URL because Claude's Add custom connector form asks for one address and nothing else. There are two honest answers. For ads, Meta's own address is mcp.facebook.com/ads, starting with https. For posting to a Page, there is no Meta address, so the URL you paste belongs to whoever runs that server, and that company or person will hold a working token for your Page.

For Spreadcast, the address is spreadcast.app/api/mcp, starting with https. You do not need to type it: Settings, AI Assistants in Spreadcast shows it with a copy button. When Claude first reaches it without a sign in, Spreadcast answers that a sign in is needed, and that answer is what makes Claude show the Connect step and open the Spreadcast consent page.

If you run an open source server from GitHub, there is usually no URL at all. Those servers run on your computer and talk to Claude Desktop or Claude Code through a config entry, not an address.

Be careful with addresses copied from forum posts, videos or AI answers. Anthropic's guide says custom connectors are not verified by Anthropic, tells you to connect only to servers you trust and to review the permissions asked for during sign in, and warns that a server's developer can change what its tools do without notice. The URL decides who sits between your assistant and your Page.

It does not post to groups or to personal profiles. Meta closed both to outside apps, and Spreadcast uses only Meta's API.

It does not run ads, boost posts or touch your ad account. For that, Meta's own ads MCP server is the better tool.

It does not post Reels or Stories to Facebook. Videos go to the Page as regular video posts, and Spreadcast makes no video itself, so a video post uses a clip you supply.

It does not read Facebook likes, comments or reach for each post. On Facebook it reads your Page's follower count. Post by post results are best checked in Meta Business Suite.

It does not reply to comments or messages. For Instagram, which Spreadcast can also connect through your Facebook Page, see the Instagram MCP server guide.