OutstandOutstand
Engineering

Facebook MCP server: posting to Pages from an AI agent

Facebook is the network where picking the wrong MCP server costs the most - the popular ones automate the website with a cookie. Here's the compliant Graph API path.

Facebook MCP server: posting to Pages from an AI agent

Facebook is the network where picking the wrong Facebook MCP server has the highest cost, because the most-starred options on GitHub are the ones most likely to get your account restricted.

Worth understanding the split before you install anything.

Does Facebook have an official MCP server?

No. Meta has not published one, so everything available is third-party, and the options divide along a line that matters more here than on most networks.

Session-based servers drive the Facebook website with a login or a cookie copied out of your browser. They are quick to set up, they can post to a personal profile, and they are against Meta's terms. Meta is unusually aggressive about detecting session automation, and the account carrying that risk is yours. These are the ones that surface first when you search.

Graph API servers use a Page access token, which is the supported path. The friction is real: you register a Meta developer app, request the Page permissions, and go through App Review before the integration works for anyone but you. That review is why there are fewer of them.

Pages only, and why that is not a limitation anyone can fix

Meta's Graph API has no supported way to publish to a personal timeline. It was removed years ago and has not come back.

So if a tool claims it can post to your personal Facebook profile, it is automating the website. There is no compliant implementation of that feature, from anyone, at any price. Any serious Facebook integration is Page-scoped, and a tool being honest about that is a good sign rather than a missing feature.

Setting it up

Outstand's Facebook MCP server runs on the Graph API and carries the developer app and App Review, so connecting a Page is a consent screen.

1. Connect the Page. Create an Outstand account, connect Facebook through the hosted OAuth link, and pick the Page you want the agent to publish to. The connection is Page-scoped, which is why you choose one at consent time.

2. Add the server. In Claude Code:

claude mcp add -t http -H "Authorization: Bearer ost_your_key" outstand https://mcp.outstand.so/mcp

For Claude Desktop, Cursor, or ChatGPT, add https://mcp.outstand.so/mcp as a custom connector. Exact configs for each client are on the Facebook MCP page.

3. Post. Give the agent the copy and any media. It picks the right Graph API endpoint based on what you attached - you do not have to tell it which one.

What the agent can do

  • Publish and schedule - text, a single photo, a multi-photo post, or a video.
  • Chain a first comment - extra content on the post becomes a threaded comment underneath, which is the usual way to put links out of the post body.
  • Read and reply to comments - get_replies reads the thread on a post published through Outstand, and create_reply responds. An agent can run a review-and-respond loop over your Page without anyone opening Meta Business Suite.
  • Measure - reactions, comments, shares, and reach per post, plus Page-level follower and insight metrics.

The Facebook-specific quirks

Three of these catch people out regularly:

  • Photos and video cannot be mixed in one post. Attach only images or only a video. Outstand rejects the mix up front rather than publishing something half-formed.
  • Media count picks the endpoint. No media posts as text, one image as a photo post, several as a multi-photo post, a video as a video upload. Four different Graph API calls behind one tool.
  • Page mentions only resolve in comments. Meta's Graph API does not expand an inline page tag in a feed post - it renders as literal text. Outstand applies mentions at the comment level, where they actually work. This one surprises almost everyone who has tried it by hand.

Also worth knowing: Facebook has no API repost or share for Pages, so that tool reports a clear failure rather than pretending. And Page insights come back thin on low-activity Pages, which is Meta withholding data below its own thresholds rather than a missing metric.

What it does not cover

This publishes organic Page content and handles comments on posts it published. It is not a Facebook Ads integration - campaigns, Ads Manager reporting, and audiences all live behind the Marketing API. It does not touch Messenger, Groups, or Marketplace, and it does not scrape other Pages for competitor research.

The part that makes it worth wiring up

One connection reaches eleven networks. The agent that posts to your Facebook Page can post the same announcement to LinkedIn, Instagram, and Threads in the same pass, and then read and answer the comments on all of them.

Meta's own tooling cannot do that across networks it does not own. That is most of the argument for a unified layer rather than four separate integrations.

The MCP server is included on every plan at $19/month with 3,000 posts. Connect a Page or browse the other networks.