A Facebook MCP server gives an AI agent tools for your Page, so a model can publish and respond rather than just draft copy for you to paste. Point Claude, Cursor, or any MCP client at Outstand's server and the agent can post text, photos, and video to a Page you manage, chain a first comment onto the post, read and reply to comments, and pull Page and post insights. Everything runs on Meta's official Graph API over an OAuth connection you approve once.
https://mcp.outstand.so/mcpclaude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any MCP client.
The server URL is https://mcp.outstand.so/mcp. Paste it into your client and connect Facebook.
claude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
// claude_desktop_config.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}// .cursor/mcp.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}# Add a custom connector in your client's settings and paste # this URL, then sign in once in the browser. No API key to copy. https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any other MCP client. Full client setup guide.
The tools that apply to Facebook, out of 27 on the server.
create_postPublish or schedule a Facebook Page post: text, a single photo, a multi-photo post, or a video.get_post_analyticsFetch reactions, comments, shares, and reach for a published Page post.create_replyReply to a comment on a Page post published through Outstand.get_repliesRead comments and replies on a Page post published through Outstand.list_postsList posts, filterable by account, status, and date range.get_postFetch a single post and its per-platform publish status.delete_postDelete a post record in Outstand, cancelling it if it is still scheduled.delete_remote_postDelete the published post on Facebook itself.upload_mediaStart a media upload and get a signed URL for an image or video.confirm_media_uploadConfirm an upload once the bytes are transferred and get the public URL to attach.list_social_accountsList connected social accounts, so the agent can find your Facebook Page.get_account_metricsFetch follower and Page-level insight metrics for a connected Page.get_auth_urlGenerate an OAuth URL to connect a new Facebook Page.get_account_usageRead current billing-period post usage.No. Meta does not publish an MCP server for Facebook, and the third-party options divide sharply along a line that matters more here than on most networks.
One group automates the Facebook website with a browser session or a copied cookie. These are the ones that show up first on GitHub, and they are the ones most likely to get an account restricted. Meta is unusually aggressive about session-based automation, and the account carrying the risk is yours.
The other group uses the Graph API with a Page access token, which is the supported path. The friction there is real: you register a Meta developer app, request the Page permissions, and go through App Review before anything works outside your own test Page. Outstand is in this group and carries that overhead for you, so connecting a Page is a consent screen rather than a review cycle.
Three realistic ways to give an agent Facebook access, and what each one actually costs you.
| Approach | Setup time | Auth | Reliability | Compliance |
|---|---|---|---|---|
| Self-hosted browser automation or scraper | Hours: clone, install, supply a login or cookie | Session cookie or account login | Breaks often. Meta actively detects and blocks it | Against Meta terms. Account and Page risk is yours |
| Self-hosted with your own Meta developer app | Days to weeks: register the app, request Page permissions, pass App Review | Your own app credentials and Page token refresh | Solid once approved, if you keep tokens fresh | Official Graph API, once App Review clears |
| Hosted API-based (Outstand) | A few minutes: sign in, approve OAuth, paste the URL | Hosted OAuth link flow. Managed Keys included, no developer app | Maintained against the Graph API, token refresh handled | Official Meta Graph API. No scraping or session automation |
Connecting Facebook is an OAuth link flow: Outstand opens Meta's consent screen, you approve the Page permissions and choose which Page to connect, and the connection is done. Outstand then works with that Page's access token, which is why the connection is Page-scoped rather than profile-scoped.
The part this removes is App Review. Publishing to a Page through the Graph API normally means registering a Meta developer app, requesting the Page management permissions, and submitting for review before the integration works for anyone but you. Managed Keys are included on every plan and cover Facebook. Your agent can start the connection itself by calling get_auth_url and handing you the link.
This server publishes organic Page content and handles comments on posts it published. It is not a Facebook Ads integration: it does not create campaigns, read Ads Manager reporting, or manage audiences, all of which sit behind the Marketing API. It does not touch Messenger, Groups, Marketplace, or personal profiles, and it does not scrape other Pages or run competitor research. What it does is publish, schedule, respond, and measure on Pages you connected.
No. Meta has not shipped one, so every option today is third-party. Check carefully how a given server authenticates: many popular ones drive the Facebook website with a session cookie, which puts your account at risk of restriction.
Yes. Add https://mcp.outstand.so/mcp to Claude, connect a Page, and Claude can publish text, photo, multi-photo, and video posts to it, then reply to the comments that come in. The same connector works in Cursor, Windsurf, ChatGPT, and any other MCP client.
No, and no compliant tool can. Meta's Graph API only supports publishing to Pages, so personal-profile posting is only possible by automating the website, which violates Meta's terms and risks the account. Connect a Page instead.
No. That is the main thing this removes. Publishing to a Page through the Graph API normally requires your own Meta app, the Page permissions, and an App Review submission. Managed Keys cover Facebook on every plan, so you approve a consent screen and you are done.
Yes. get_replies reads the comments on a post published through Outstand and create_reply responds to them, so an agent can run a review-and-respond loop over your Page without you opening Meta Business Suite.
Yes. create_post takes a scheduled time, so an agent can queue a Page post ahead of time. Scheduling runs in Outstand rather than on Facebook, and a scheduled post can be cancelled with delete_post before it goes out.
The MCP server is included with every Outstand account at no extra cost. Pricing is $19/month, 3,000 posts included, and posts published by an agent draw on the same quota as posts published through the REST API.
Every claim on this page is restated, dated, and citable on the facts page.
Sign in, approve the Page once, paste the server URL into your client. Then let your agent post and handle the comments.
https://mcp.outstand.so/mcp