Keep Your Page on Drafts With a Manus Cue Connector for Facebook Posting

Cue, the personal-agent app Manus launched on 28 September 2026, gives every agent its own email address, phone number, wallet and computer, and a Manus Cue connector for Facebook posting has to keep that agent identity well away from your Page. The Page is your brand in public, and the agent is a separate identity built to act on its own. The setup below lets the agent write Page posts without holding your Facebook login or the power to publish.

The short version: add the AdaptlyPost MCP server at https://mcp.adaptlypost.com/mcp with a Contributor-role adaptly_ token, ask Cue to list your Facebook Pages with their pageId before it writes anything, and let it save drafts only. You publish from AdaptlyPost. The Manus Cue connector guide covers the full setup.

What is a Manus Cue connector for Facebook posting?

A Manus Cue connector for Facebook posting is a custom MCP connector that points a Cue agent at the AdaptlyPost MCP server, so the agent drafts and schedules posts to the Facebook Pages you connected in AdaptlyPost. Manus's word is "connector", and its help centre says you "can create your own custom API connector or MCP connector."

Cue is "built on the same infrastructure as Manus", according to the Manus 2.0 launch post. The documented path to add a server is Manus's own: Settings, then Integrations, then Custom MCP Servers, then Add Server, with the server URL and an API key or Bearer token. As of 29 September 2026 Manus has not documented a connector screen inside Cue, or whether a server added in Manus shows up in Cue automatically. The pillar guide walks through both routes.

Why should a Cue agent never hold your Facebook login?

A Cue agent never needs your Facebook login, because AdaptlyPost publishes to the Page through the connection you already made in the AdaptlyPost dashboard. The post goes out under the Page name. The agent's own email and phone number never touch Facebook.

Manus says each agent has its own computer to "see a task through on its own machine", which invites letting it sign in to facebook.com. Don't. A password gives the agent everything your account can do, and you can only take it back by changing the password. An adaptly_ token covers one workspace, carries one role, and dies the moment you revoke it on the API Tokens page. Runtimewire noted on 28 September 2026 that the Cue announcement does not explain how users restrict what agents do with their email or phone identity. Keep your social logins out of that gap.

Which token role should Cue get for Facebook?

Cue should get a Contributor-role token, which AdaptlyPost labels "Recommended for AI agents" in the token dialog. A Contributor "creates and edits own drafts; cannot schedule or publish", so the worst a confused agent does is leave a bad draft in your queue.

Manus has published no approval gate for Cue as of 29 September 2026, and the launch post frames the human's part as "You set the direction and make the final call." The token role turns that sentence into an enforced rule. When a Contributor key tries to schedule, AdaptlyPost returns a 403 with code permission_denied, names the permission it lacked, and tells the agent to save a draft instead. The error is final for that key, and a retry returns the same 403.

Why does Facebook use pageId instead of a connection ID?

Facebook uses pageId because every connected Facebook account in AdaptlyPost is one Page, and the spec separates the account record from the Page Facebook knows. The account id "identifies the connected page and is not the Facebook page id", so facebookConfigs requires pageId, while nine of the ten networks take a connection ID.

The top-level pageIds array accepts either the account id or the pageId. The per-Page config does not. An agent that copies the pattern from the other nine networks sends connectionId inside facebookConfigs and fails on Facebook alone. Make the first call read-only so the agent reads the field instead of guessing it.

What do I paste into Cue for Facebook?

Paste an instruction that starts read-only and keeps the agent on drafts. Send it after the connector is in place, in the Cue chat with the agent that will handle your Pages.

You have an AdaptlyPost connector (MCP server https://mcp.adaptlypost.com/mcp).
Before you write anything, call list_accounts and show me every Facebook Page
with its displayName, its account id and its pageId. Stop there.
 
Rules for every Facebook post after that:
- facebookConfigs takes pageId, never connectionId.
- postType REEL needs contentType VIDEO. STORY needs IMAGE or VIDEO.
- Always set saveAsDraft: true. Never schedule or publish.
- If a call returns permission_denied, save a draft and tell me.

A list of Pages and IDs proves the agent sees the connector and the token works. If Cue says it has no such tool, the connector did not reach the app, and the pillar guide covers the fallback.

What can the connector draft for a Facebook Page?

The connector drafts Feed posts, Reels and Stories for any connected Page through facebookConfigs[].postType, with an optional videoTitle of up to 255 characters on video posts. The spec rejects mismatches with a 400: REEL needs contentType: VIDEO, STORY needs IMAGE or VIDEO, and FEED works with every content type.

A post takes one account per platform, so each Page gets its own draft, and platformTexts gives Facebook its own caption when the same draft also goes to Instagram or LinkedIn. A Reel draft for one Page looks like this.

{
  "platforms": ["FACEBOOK"],
  "contentType": "VIDEO",
  "text": "Autumn menu is live.",
  "pageIds": ["1015..."],
  "facebookConfigs": [
    { "pageId": "1015...", "postType": "REEL", "videoTitle": "Autumn menu" }
  ],
  "mediaUrls": ["https://..."],
  "timezone": "Europe/Kyiv",
  "saveAsDraft": true
}

You then open the draft in AdaptlyPost, read it, and schedule it. With an Editor key the agent does that last step itself through publish_draft, which takes the draft id, a timezone and an optional scheduledAt. The Facebook post scheduler page shows the same queue from the dashboard side.

Can two Cue agents split drafting and publishing?

Cue puts multiple agents in one group chat with a shared goal, where "they hand work to each other", so a drafting agent and a reviewing agent is a natural split for a Page. Manus has not documented, as of 29 September 2026, whether each agent in a group can hold a different connector or token.

Treat the split as editorial until you have tested it. One agent drafts, a second checks the copy against your brand notes, and a person publishes. To test whether the connector is shared, ask the second agent to call list_accounts. An answer means it is, and a Contributor key is the only safe thing to share.

What breaks on Facebook specifically?

An expired Page token breaks first, and it breaks quietly. A Page whose token Facebook rejects stays in list_accounts with status set to unauthorized and unauthorizedReason carrying Facebook's own message, and posts to it return a 400 until you reconnect it in the dashboard. AdaptlyPost re-checks Facebook Pages automatically twice a day and fires an account.unauthorized webhook when one fails.

A Reel sent with an image fails at request time, which is the good kind of failure because no post exists yet. The multi-network post is the third trap. A post sent to Facebook, Instagram and LinkedIn at once publishes per platform, and list_post_results is the only place a Facebook failure shows. Retrying it through retry_failed_platforms takes the failed entry's id, or the name FACEBOOK to retry every failed Facebook entry. Retry needs publish permission, so under a Contributor key that step is yours.

One failure belongs to Cue. Manus 2.0 Automations list Webhook as a trigger source, but Manus has not documented Automations inside Cue as of 29 September 2026, so Cue will not react to an account.unauthorized event on its own. Read the account list yourself before a campaign. For the same pageId path in other agents, the Meta Muse connector for Facebook posting builds it from the REST spec, and the Grok bot template for Facebook posting ships it as a saved template.

Frequently Asked Questions

Can Cue post to my Facebook Page without a connector?

Manus has documented no social media connector for Cue as of 29 September 2026, and the Cue launch material contains no posting example. Without a connector the only route left is the agent driving facebook.com on its own computer with your password, which gives it your whole account. The AdaptlyPost connector reaches the Page with a revocable, role-limited token instead.

Where does the AdaptlyPost token go?

The token goes in the Manus custom MCP form, under Settings, Integrations, Custom MCP Servers, in the field for an API key or Bearer token. Manus says removing a connector clears "all login information and saved credentials", and that it redacts API keys in shared sessions. Create the token at the API Tokens page with the Contributor role.

Why did Cue's post fail on Facebook and nowhere else?

The call almost certainly put connectionId in facebookConfigs, which requires pageId. Ask Cue to call list_accounts, read back the pageId for the Page by name, and fix the draft. If the post already went out elsewhere, retry only the Facebook entry so the other networks do not post twice.

Does a Contributor key stop Cue from publishing by accident?

A Contributor key cannot schedule, publish, retry or bulk schedule, and AdaptlyPost answers those calls with a 403 permission_denied. The agent keeps creating and editing its own drafts, uploading media and reading posts. You or an Editor publishes the draft.

Can Cue post to a Facebook Group or a personal profile?

AdaptlyPost publishes to Pages, and Groups and personal profiles are not targets in the spec's Facebook surface. A Page is the only object that carries the pageId that facebookConfigs requires. Connect the Page in AdaptlyPost and it appears in list_accounts.

What does Cue cost to run for Facebook posting?

Cue is free during early access with an invite code, and Manus's launch post offers MEETCUE to a limited number of early users. Manus has not said what Cue costs after early access, as of 29 September 2026. On the AdaptlyPost side, the connector needs a plan that lists API/MCP/CLI access, and every plan starts with a 7-day free trial.

How do I find the pageId for a Facebook Page?

Ask Cue to call list_accounts before it writes anything. Each Facebook Page comes back with its displayName, its account id and its pageId. Use the pageId in facebookConfigs, because the account id is not the Facebook page id.

Can one Cue draft carry a different caption for Facebook?

The platformTexts field gives Facebook its own caption when the same draft also goes to Instagram or LinkedIn. Ask Cue to fill it in the same create_post call, still with saveAsDraft: true.

Can Cue draft for several Facebook Pages in one call?

No. A post takes one account per platform, so each Page needs its own draft, and a draft naming two Pages fails when it is published. Have Cue save one draft per Page, each with that Page's pageId in both pageIds and facebookConfigs.

How do I publish a draft Cue saved for Facebook?

Open the draft in AdaptlyPost, read it and schedule it yourself, which keeps the Contributor key in place. Or give the agent an Editor key, and it calls publish_draft with the draft id, a timezone and an optional scheduledAt. An Editor key leaves no gate between the agent and the public feed, so use it only once you trust the drafts.

Create a Contributor-role API token and add the AdaptlyPost server to Manus, or read the Manus Cue connector guide first. For the same job in ChatGPT, see the OpenAI dots plugin guide.

Sources: Manus, Introducing Manus 2.0 (28 September 2026); Manus Help Center, How can I use Manus Connectors?; Manus docs, custom MCP and automations; cue.im; Runtimewire (28 September 2026); the AdaptlyPost OpenAPI spec and MCP setup guide. Checked 29 September 2026.