Draft Under Your Own Name With a Manus Cue Connector for LinkedIn Posting

Every LinkedIn post carries a real person's name or a real company's logo, which makes a Manus Cue connector for LinkedIn posting a different job from the same connector on a feed network. Cue is the personal-agent app Manus launched on 28 September 2026, and Manus gives each Cue agent "its own email, phone number, wallet, and computer." The agent has an identity of its own. The post it writes for LinkedIn does not. It goes out as you.

The short version: connect the AdaptlyPost MCP server with a Contributor-role adaptly_ token, have Cue read your LinkedIn connections by name, and let it save drafts that you schedule. The Manus Cue connector guide covers the setup itself.

What is a Manus Cue connector for LinkedIn posting?

A Manus Cue connector for LinkedIn posting is a custom MCP connector that gives a Cue agent the AdaptlyPost tools for drafting and scheduling posts to your LinkedIn profile or Company Page. The server lives at https://mcp.adaptlypost.com/mcp and accepts an Authorization: Bearer adaptly_... header.

Manus documents the path for Manus itself: Settings, then Integrations, then Custom MCP Servers, then Add Server, with a server URL and an API key or Bearer token. Cue is "built on the same infrastructure as Manus", but as of 29 September 2026 Manus has not documented a connector screen in Cue or whether a Manus connector appears there. The pillar guide covers both the Manus route and the ask-the-agent route. Everything below assumes the connector already answers.

Whose name goes on a LinkedIn post that Cue writes?

A LinkedIn post that Cue writes through AdaptlyPost publishes under the LinkedIn account you connected in the AdaptlyPost dashboard, which is your personal profile or your Company Page. The agent's own email address and phone number play no part in it.

That split is the useful part. The agent keeps its own inbox for its own errands, and AdaptlyPost holds the LinkedIn authorisation you granted once. The AdaptlyPost API has endpoints for posts, media, accounts, webhooks, analytics and AI captions, and none for LinkedIn messages or connection requests, so the connector cannot send a DM in your name. The risk that remains is the post itself: a Cue agent writing in your voice, to your colleagues, with no approval gate that Manus has documented as of 29 September 2026.

Why give Cue a Contributor key for LinkedIn?

A Contributor key lets Cue create and edit its own drafts and blocks it from scheduling or publishing, which is the approval step Cue does not ship with. AdaptlyPost marks Contributor as "Recommended for AI agents" in the token dialog.

When a Contributor key tries to schedule, AdaptlyPost answers with a 403 and code permission_denied, and the error message tells the agent to save a draft instead. You read the draft in AdaptlyPost and schedule it. Manus's own framing of Cue fits this: "You set the direction and make the final call." On LinkedIn the final call is whether a post sounds like you, and no token setting judges tone. Reading every draft does.

Does LinkedIn need any config fields now?

LinkedIn has a config object in the AdaptlyPost spec as of 29 September 2026: LinkedInPostConfig, with a required connectionId and an optional documentTitle of up to 100 characters. Earlier guides on this blog, written when LinkedIn had no config, predate it.

A text or image post still needs nothing platform-specific. Send platforms: ["LINKEDIN"], a contentType, a timezone, the text and linkedinConnectionIds, and the post is complete. The config only matters for the new DOCUMENT content type, where documentTitle sets the title LinkedIn shows on the document and defaults to the uploaded file name.

What do I paste into Cue for LinkedIn?

Paste one message that makes Cue read your accounts by name, then locks it to drafts with LinkedIn's own rules.

You have an AdaptlyPost connector (MCP server https://mcp.adaptlypost.com/mcp).
Call list_accounts and show me every LinkedIn account with its displayName,
username and id. Tell me which one is the Company Page. Stop there.
 
Rules for every LinkedIn post after that:
- Always set saveAsDraft: true. Never schedule or publish.
- Put the first two lines to work. No hashtags unless I ask.
- For a PDF or slide deck, use contentType DOCUMENT with LinkedIn only,
  one file, and a documentTitle under 100 characters.
- Use platformTexts when the same post also goes to X or Threads.
- If a call returns permission_denied, save a draft and tell me.

The account names matter more on LinkedIn than anywhere else. A profile and a Company Page both appear as connections, and the ids do not say which is which. A draft aimed at the wrong one publishes cleanly to the wrong audience.

Can Cue turn a report into a LinkedIn document post?

Cue can draft a LinkedIn document post from a file, because AdaptlyPost's DOCUMENT content type publishes one PDF, PPT, PPTX, DOC or DOCX file of up to 100 MB and 300 pages. DOCUMENT is LinkedIn only: any other platform in the same request returns a 400.

The agent's own computer is the obvious place to build the deck. Manus describes it as where an agent sees "a task through on its own machine", but has not documented file handling on it or uploads from it as of 29 September 2026. The file reaches AdaptlyPost through upload_media, which takes a URL or base64 data, or a presigned URL from get_upload_urls. Test the upload with a small PDF before a real report. A finished draft looks like this.

{
  "platforms": ["LINKEDIN"],
  "contentType": "DOCUMENT",
  "text": "Our Q3 hiring numbers, slide by slide.",
  "linkedinConnectionIds": ["conn_..."],
  "linkedinConfigs": [
    { "connectionId": "conn_...", "documentTitle": "Q3 hiring report" }
  ],
  "mediaUrls": ["https://..."],
  "timezone": "Europe/Kyiv",
  "saveAsDraft": true
}

The LinkedIn document post guide covers what the format looks like in the feed.

Can Cue keep a weekly LinkedIn cadence?

Manus has documented no scheduling or triggers inside Cue as of 29 September 2026, so the LinkedIn schedule belongs in AdaptlyPost, where every draft Cue saves waits until someone gives it a date.

AdaptlyPost offers two ways to run a cadence, and they need different token roles. A recurring series repeats one post WEEKLY on the weekdays you pick, every 1 to 30 weeks, until an endsOn date or a maxOccurrences count between 2 and 365. A series cannot be combined with saveAsDraft, so a Contributor key cannot create one. The bulk endpoint schedules 1 to 100 different posts in one call, and it needs schedule permission too. It also rejects DOCUMENT posts, which go one at a time.

Cue's group chats fit the drafts route. Manus says agents in a group chat "hand work to each other" toward a shared goal, so one agent collects the week's changes and a second writes the LinkedIn draft from them. The LinkedIn post scheduler page shows the queue those drafts land in.

What breaks on LinkedIn specifically?

An expired LinkedIn authorisation breaks first. A connection whose token LinkedIn rejects shows in list_accounts with status set to unauthorized, and AdaptlyPost refuses posts to it with a 400 until you reconnect it in the dashboard. A connection that lapses after a post is scheduled fails at publish time instead, which the LinkedIn scheduled posts troubleshooting guide walks through.

The wrong account breaks second, and it breaks silently. A draft aimed at your profile when you meant the Company Page publishes without an error. list_post_results returns an accountName for each platform, and that name is the one place the mistake shows. Read it after every publish.

The third failure is DOCUMENT mixed with other networks. A deck sent to LinkedIn and X in one request returns a 400. Split it into a LinkedIn document post and a separate text post for X. For comparison, the Meta Muse connector for LinkedIn posting reaches the same API from a REST spec, and the Grok bot template for LinkedIn posting runs the cadence from a saved routine.

Frequently Asked Questions

Does Cue connect to LinkedIn by itself?

Manus has published no LinkedIn connector for Cue as of 29 September 2026, and the Cue launch material has no posting example. A custom MCP connector to a scheduler is the route in. AdaptlyPost holds the LinkedIn authorisation, so the agent never logs in to linkedin.com.

Can the connector post to a Company Page and a personal profile?

Both appear as separate connections in list_accounts, but a post takes one account per platform, so each needs its own draft. Ask Cue to read back each displayName before it saves anything. The ids alone do not say which account is the Company Page.

Can Cue send LinkedIn messages through AdaptlyPost?

AdaptlyPost publishes posts and has no endpoint for LinkedIn messages or connection requests. A Cue agent that wants to contact someone does it from its own email or phone number, which Manus gives every agent. Keep that separate from anything that speaks for your LinkedIn account.

Can Cue schedule a LinkedIn PDF carousel?

A PDF goes out as a DOCUMENT post: one file of up to 100 MB and 300 pages, to LinkedIn only. DOCUMENT posts cannot be bulk scheduled, so each one is its own create_post call. Under a Contributor key Cue saves it as a draft and you schedule it.

Why does my Contributor key fail when Cue sets up a weekly series?

A recurring series cannot be combined with saveAsDraft, and a Contributor key can only save drafts. AdaptlyPost returns a 403 permission_denied on the scheduling call. Create the series yourself in AdaptlyPost, or have Cue save each week's post as a draft.

What does Cue cost for LinkedIn posting?

Cue is free during early access with an invite code, and Manus's launch post gives 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.

Which token role should Cue use for LinkedIn posting?

Contributor. AdaptlyPost marks it "Recommended for AI agents", and it lets Cue create and edit its own drafts. If Cue tries to schedule or publish, AdaptlyPost returns a 403 with code permission_denied.

How do I check which LinkedIn account a post went to?

Call list_post_results after the publish. It returns an accountName for each platform, and that name shows whether the post went to your profile or the Company Page. A draft aimed at the wrong account publishes without an error, so read it every time.

What happens when my LinkedIn connection expires?

The connection shows in list_accounts with status set to unauthorized. AdaptlyPost refuses new posts to it with a 400 until you reconnect it in the dashboard. If the connection lapses after a post is scheduled, the post fails at publish time instead.

Can Cue send the same post to LinkedIn and X?

A text post can go to both. Ask Cue to use platformTexts so each network gets its own wording. A DOCUMENT post cannot, because it is LinkedIn only and any other platform in the same request returns a 400.

Create a Contributor-role API token and add the AdaptlyPost server to Manus, or read the Manus Cue connector guide first. For the ChatGPT version of this setup, 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; cue.im; the AdaptlyPost OpenAPI spec and MCP setup guide. Checked 29 September 2026.