---
title: "Cue integration with Bolta"
description: "How to connect a Cue agent from Manus to Bolta with an API key so it drafts social posts you approve. What is confirmed, what is not, and what to try if Cue has no custom MCP field."
canonical_url: "https://bolta.ai/integrations/cue"
markdown_url: "https://bolta.ai/integrations/cue.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Cue integration with Bolta

Source: https://bolta.ai/integrations/cue
Last updated: 2026-11-21

How to connect a Cue agent from Manus to Bolta with an API key so it drafts social posts you approve. What is confirmed, what is not, and what to try if Cue has no custom MCP field.

## Summary

Give a Cue agent your weekly social drafting, and approve it in Bolta

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Hand one agent a weekly job: draft next week's LinkedIn and X posts and save them for your review
- Ask the agent each morning what is waiting for your approval in Bolta
- Let a writing agent in a group chat pass finished copy to your Bolta agent to save as a draft
- Have the agent read last month's account analytics and suggest what to post more of
- Set up a recurring routine in Bolta by describing it once to the agent, then approve the plan
- Check which brands and connected accounts the agent can reach before it drafts anything

## Limitations and boundaries

- Confirmed: Cue is a real Manus product, announced in the official Manus 2.0 post. Bolta's server address and API key are built for MCP clients that accept a remote server URL and a bearer token.
- Confirmed by Manus: Manus itself can add a custom MCP server by HTTPS URL with an API key or bearer token (Connectors, or Settings, Integrations, Custom MCP Servers).
- Not confirmed: that Cue has a field for your own MCP server at all. No official Manus page mentions Cue in its MCP docs, and Cue's public pages show a fixed list of connectors.
- Not confirmed: the exact Cue screen names, whether Cue takes a bearer token in an API key box, and whether Cue and Manus share one connector list. We have not run Bolta inside Cue ourselves.
- OAuth sign-in is not documented for custom MCP servers in Manus, so this page uses an API key only.
- A pasted API key acts as you directly and does not get the review hold that browser sign-in gets. Use a key with narrow permissions and tell the agent to save drafts only.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Get into Cue first

Cue is in early access and needs an invite code. Manus names MEETCUE as a starter code, so check it still works. Access can change, so check the live Cue site.

## Create a Bolta API key

In Bolta, open Settings, API Keys (bolta.ai/dashboard/settings?tab=api) and create a key for the brand this agent should post for. It starts with bolta\_sk\_ and is shown once. Tick only what the job needs: Read Posts, Read Accounts, Read Voice Profiles and Write Posts for drafts. Write Posts also lets a key schedule, so the draft-only rule comes from your brief to the agent plus Bolta's own checks. Leave Approve Reviews and Delete Posts off.

## Keep the key out of the chat

Copy the key somewhere safe. Do not paste it into a message to the agent. It belongs in the connector field only.

## Find where Cue lets you add your own server

Open Cue's connectors screen and look for a Custom MCP option or an MCP URL field. If you only see a fixed list, Bolta cannot be added in Cue yet. Use Manus custom MCP instead (Settings, Integrations, Custom MCP Servers, Add Server).

## Enter the Bolta server address

Use https://mcp.bolta.ai/mcp. Check there are no spaces before or after it. Name the connector Bolta so the agent can find it.

## Add the key as a bearer token

If the form has a bearer token field, paste the key there. If it is a plain API key box, type the word Bearer, a space, then the key. Postiz documents this format for Cue. Manus has not confirmed it.

## Run the connection test

A good test lists Bolta's tools. If it fails, recheck the address and that the key was copied in full.

## Hand the connector to one agent

Give Bolta to the agent that will handle your social media. Ask it to list your Bolta brands and connected accounts before anything else.

## Start with one small job

Ask for this week's posts as drafts and tell the agent not to approve or publish. Open Bolta, read them and approve there.

## What Cue is, and who it is for

Cue is a personal agent from Manus. It is not a coding tool and not a chat window you reopen each time. Manus describes each Cue agent as having its own email address, phone number, wallet and computer. It keeps working after you log off, and several agents can share a group chat. That makes it a fit for a standing job, such as owning your weekly social drafting. For Bolta, only one part matters: Bolta does not need your payment details, a phone number or access to the agent's wallet. The connection is a server address and one API key.

## Early access and the invite code

The Manus 2.0 announcement says Cue is in early access and free with an invite code. Manus names MEETCUE as a starter code, limited to a set number of early users, first come, first served. Cue runs on web, desktop and mobile, with iOS still pending in that post. We could not confirm whether Cue is still invite-only today. Check the live site before you plan around it.

## One agent, one job, one approval step

A standing agent does best with a narrow brief. 1. Name the job: For example: every Friday, draft next week's posts for one brand. 2. Let it save drafts only: Tell the agent to save each draft in Bolta and not to approve or publish anything. 3. Approve in Bolta: Open Bolta, read the exact text and approve the ones you want. Reject the rest.

## Group chat: a writer agent hands drafts to a Bolta agent

Cue lets several agents share a group chat. One pattern is a writing agent that produces copy and a second agent, the one with the Bolta connector, that saves it as a draft. Give the Bolta connector to only one agent. That keeps a single place that can touch your brands. Ask it to save drafts only, then review them in Bolta.

## Why an API key and not sign-in

Manus documents custom MCP servers with an HTTPS URL plus an API key, bearer token or similar. It does not describe OAuth or custom headers for them, so a Bolta browser sign-in inside Cue is unconfirmed. A Bolta API key is made for one brand and carries only the permissions you tick. It acts as you, so it does not get the review hold that browser sign-in gets, and Cue could schedule or publish if asked and if the key allows it. Safe Mode and required client sign-off in Bolta still apply. Create a separate key for each agent, so you can delete one without touching the others.

## What to do if Cue only shows a fixed connector list

This is the most likely snag, and it is yours to test in your own account. Cue's public pages show a set list of connectors, and Manus's official custom MCP pages do not mention Cue. So there may be no box for your own server today. Check Cue's connectors screen for a Custom MCP option or an MCP URL field. If there is none, use the same Bolta address and key in Manus instead, where custom servers are documented. Then check Cue again after its next update.

## Cue or Manus for a social media job

Both columns are limited to what Manus has published. Neither has been run against Bolta by us, so treat the first drafting job as a test. Question: Custom MCP server documented; Cue: Not found in Manus docs; Manus: Yes, with a URL and a key or bearer token | Question: Described as a standing agent; Cue: Yes, by Manus; Manus: Not stated | Question: Tested with Bolta by us; Cue: Not tested; Manus: Not tested

## Keep the key narrow because Cue works unattended

A standing agent may act while you are away, so the key matters more here than in a chat you watch. Tick only the read permissions and Write Posts, leave Approve Reviews and Delete Posts off, and create one key per agent so you can delete it alone. Write Posts also lets a key schedule, so say draft only in the brief. Safe Mode and required client sign-off still apply. Do your approving in Bolta.

## What is Cue and how is it different from Manus?

Cue is a personal agent from Manus with its own email, phone number, wallet and computer, built for standing jobs. Manus is the general agent product. They share infrastructure according to Manus, but their docs treat them separately.

## Can Cue connect to Bolta?

We cannot confirm it. Bolta's server and key are built for clients that take a remote MCP URL and a bearer token, and Manus supports that. But no official page says Cue has a field for your own server, and we have not tested it inside Cue.

## Do I need an invite code to use Cue?

The Manus 2.0 post says Cue is in early access with an invite code, and names MEETCUE as a starter code. Check the live site, because access may have changed.

## Do I paste the Bolta API key with the word Bearer in front?

Only if the field is a plain API key box. Postiz documents that format for Cue, but Manus has not confirmed it. If there is a bearer token field, paste the key alone.

## Will Cue publish without my approval?

It should not, if you tell it to save drafts only. A pasted API key acts as you and does not get the review hold that browser sign-in gets, so keep the key's permissions narrow and keep the draft-only instruction in the brief. Safe Mode, role checks and required client sign-off in Bolta still apply.

## Why does my Cue agent not see Bolta tools?

Usually the connector is not assigned to that agent, or the test failed. Re-run the connection test, give the connector to the agent, and ask it to list your Bolta brands.

## Can one Cue connection reach several brands?

A Bolta key is made for one brand, so use one key per brand. We have not confirmed how Cue handles several connectors for one agent.

## Does Cue support Bolta sign-in instead of a key?

Unconfirmed. Manus does not describe OAuth for custom MCP servers, so this page uses an API key only. If Cue shows a sign-in button for your own server, that would be new to us.

## Is Cue free?

Manus says early access is free with an invite code. Pricing after that is not something we can confirm. Bolta has its own plans, shown on the Bolta pricing page.

## Can a Cue agent use Bolta skills?

Unconfirmed. Nothing official says Cue agents read skill files. The MCP connection alone gives the agent Bolta's tools.

## Which networks can a Cue agent post to through Bolta?

Whatever you have connected in Bolta, such as LinkedIn, X, Instagram, Facebook, Threads and Bluesky. The agent can ask for a connect link if a network is missing. Posting still needs your yes.

## Can two Cue agents share one Bolta connector?

We have not confirmed how Cue shares connectors between agents. We suggest giving Bolta to one agent only, so a single place can touch your brands.

## Cue only shows a fixed list of connectors

Then Bolta cannot be added inside Cue yet. Use Manus custom MCP (Settings, Integrations, Custom MCP Servers, Add Server) with the same address and key, or check Cue again after an update.

## The connection test fails

Check the address is exactly https://mcp.bolta.ai/mcp with no spaces. Then check the key was copied in full and starts with bolta\_sk\_. A key without a needed permission gets a 403 for that action.

## The agent does not see any Bolta tools

The connector may not be assigned to that agent. Give it to the agent that handles social media, then ask it to list your Bolta brands.

## It says unauthorized after I pasted the key

If the field is a plain API key box, try the word Bearer, a space, then the key. That format comes from Postiz and is unconfirmed by Manus. If the field is a bearer token field, paste the key alone.

## The agent can only see one brand

A Bolta key is made for one brand. Create another key for the other brand and add it as a second connector, or ask the agent to name the brand it is working on.

## I have no invite code

Cue is in early access. Without access you cannot test this. The Manus route above is the documented alternative.

## Is Cue the same as Manus?

Both come from Manus and Manus says they share infrastructure, but the documented custom MCP steps are for Manus. Cue's connector screen is not covered by those docs.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/manus](https://bolta.ai/integrations/manus)
- [Related page: /integrations/claude-duet](https://bolta.ai/integrations/claude-duet)
- [Related page: /integrations/dots](https://bolta.ai/integrations/dots)
- [Related page: /integrations/mcp](https://bolta.ai/integrations/mcp)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Cue official website](https://manus.im/)
