Skip to content
BuzzTake
Sign inGet started
MenuClose

Cue by Manus

Cue and BuzzTake: the route that works

Cue gives each agent its own email address, phone number and computer. It documents no way to add an MCP server or a custom API, so the posting goes through Manus, from the same team.

Get startedSet up Cue
Custom MCP
Not documented
Custom API or shell
Not documented
Messengers
iMessage, Telegram, LINE, Slack
Route that works
Manus, with the BuzzTake connector
Cue, sample run. Manus, the route that works for Cue users, plans five Instagram drafts with the BuzzTake connector and submits them for review. Two drafts show as waiting for review.

What Cue can do in your social accounts

A Cue agent works through the connectors Cue supports, such as email, calendar and messaging, and talks to you on iMessage, Telegram, LINE and Slack. None of its documents mention a custom MCP server or an API connector.

Manus, from the same team, has both. Add BuzzTake to Manus as a connector, and Manus can post, answer and plan drafts in your social accounts while Cue keeps your errands.

If your Cue agent ever shows a custom MCP option, BuzzTake needs only its URL, and the sign-in is the same OAuth flow as in Manus. Until it does, this page does not claim that it works.

Cue documents no custom MCP connector, no custom API and no shell. It cannot call BuzzTake. Manus, made by the same team, has custom MCP connectors, and the steps below use it.

It works on Instagram, Facebook, X and LinkedIn, and on every other platform BuzzTake connects. Each action is one tool, named as in the actions reference.

Jobs for Cue

Say it in plain words. These are prompts that work, and the calls they make.

  1. Plan the week in Manus

    Manus plans the posts for next week on the BuzzTake calendar and sends them for review, while Cue handles the rest of your week.

    With BuzzTake, plan 5 Instagram posts for next week as drafts and submit them for review.

    5 × create_content10 credits for each draft that goes out

  2. Read this morning's messages in Manus

    Manus lists the new Instagram conversations and drafts answers that you send from Manus.

    With BuzzTake, list my new Instagram conversations and draft an answer for each.

    1 × list_conversations, 3 × read_conversation16 credits ($0.16)

  3. Approve posts from your phone

    BuzzTake approvals work in the BuzzTake app and through review links, so a person approves posts without Cue or Manus.

    Submit the five drafts for review under the Brand review policy.

    5 × create_content10 credits for each draft that goes out

Set up Cue

Connect BuzzTake to Manus. Cue needs no change.

  1. Open Connectors in Manus

    In Manus, open Connectors, select Create, then Add MCP by URL.

  2. Enter the server

    Server name: BuzzTake. Server URL: the URL below. Manus detects the OAuth sign-in.

    Server URL
    https://mcp.buzztake.com/mcp

  3. Sign in

    Sign in on BuzzTake and select Allow.

  4. Give the social work to Manus

    Keep errands with Cue, and name BuzzTake in Manus tasks that touch your accounts.

Ways to connect Cue

The routes that reach BuzzTake from Cue, and how well each one fits.

Remote MCP, OAuth sign-inNot tested

A custom MCP connector in Cue. Cue does not document one.

REST APINot tested

A custom API connector in Cue. Cue does not document one either.

Through another agentBest fit

Through Manus: Add MCP by URL with OAuth, or Custom MCP with a key header. The Manus page has both.

What it costs

BuzzTake charges in prepaid credits for the actions it runs. One credit is one US cent.

Credits for each job on this page
JobCreditsUSD
Plan the week in Manus10 per post$0.10 per post
Read this morning's messages in Manus16$0.16
Approve posts from your phone10 per post$0.10 per post

A post, a quote or a message is 10 credits, a reply 8, a like or a follow 3, and a read or a search 4. A planned post costs nothing until it goes out. Reads are charged when they succeed, and a write that fails before the page changes is refunded.

Cue's model use is billed by Manus, not by BuzzTake. Every price is on the pricing page, and the rules are in Credits.

Approvals and safety

A person can approve before anything goes out, and every action is recorded.

Cue asks for your approval before purchases. For posts, approvals live in BuzzTake: a reviewer approves each draft in the app or through a review link, whichever agent planned it.

  • Ask for drafts when a person must check first. create_content puts the post on the calendar, submit_for_review sends it to a reviewer, and it goes out only after the approval.
  • Give the agent an API key without the content_publish permission. It can then plan drafts and send them for review, and it cannot post by itself.
  • BuzzTake records every action: who asked, through which key, on which account, what the page returned and what it cost.
  • A sign-in step that BuzzTake cannot finish, such as a 2FA code, becomes a challenge. The agent asks you for the code, or gives you a link to a live browser where you answer it.
  • Only an owner or an administrator can allow an OAuth client. Disconnect it under Developers in the app, and its token stops working.

More in Approvals and Reports and audit.

Limits

  • Cue is by invitation. A code comes from the Agents tab in the Manus sidebar or by email. Apps exist for iOS, Mac and Android.
  • An action tool waits up to 120 seconds for its result. A longer action comes back with its id, and get_action follows it to the end.
  • The MCP server runs up to 8 requests at a time for one key or sign-in. Above that it answers 429 with Retry-After, and the client tries again.
  • One organization connects up to 200 accounts.
  • The platforms set their own pace. When one asks an account to slow down, the action ends with rate_limited, and a write that failed before the page changed is refunded.

Troubleshooting

Every error code and its fix is in Errors and challenges.

Cue says it cannot reach BuzzTake
That is expected: Cue has no documented way to call an MCP server or an API. Use Manus for the social work.
The client says the server refused the token (401)
The sign-in expired or was revoked, or the API key is wrong. Sign in again from the client, or make a new key under Developers.
An action stops at needs_input
The platform asked for a code. Give the code to the agent so it calls answer_challenge, or open the challenge's sign_in_url and answer in the live browser.
The answer is insufficient_credits
The balance is lower than the price, and nothing was queued. A post needs 10 credits. Top up, then ask again.
The answer is unsupported
The platform has no such action. The error lists the actions it has, and the generic browser action can do the rest step by step.
An account shows signed_out
Its session ended and no stored password could sign it in again. Ask the agent for a sign-in link with get_sign_in_link and open it, or reconnect the account in the app.

Cue questions

Can Cue post to my social media accounts?
Not through BuzzTake. Cue documents no custom MCP connector, custom API or shell. Manus, from the same team, connects to BuzzTake as a custom MCP connector.
Why does this page point to Manus?
Manus is made by the same team and documents custom MCP connectors. It is the route that works today for the work Cue cannot do in your social accounts.
Will BuzzTake work if Cue adds MCP connectors?
BuzzTake needs only an MCP client that speaks streamable HTTP with OAuth or an API key. Any client that does can connect with the server URL.

Related agents

All AI agents, the MCP server docs, the quickstart, and the platforms: Instagram Facebook X LinkedIn

Cue is a trademark of Manus. Platform names belong to their owners. BuzzTake is not affiliated with or endorsed by Manus or any platform.

Give Cue your social accounts.

Add an account with a password, cookies or a sign-in link, then connect the MCP server and ask.

Get startedRead the MCP docs