Schedule social media posts with Manus
Manus is an autonomous agent that runs multi-step tasks, and you can add Bolta to it as a custom MCP connector. Manus does the research and writing, Bolta saves the posts as drafts in your brand voice and holds them until you say yes.
- Manus researches, writes the versions, then saves drafts in Bolta
- Connects with a scoped Bolta API key, not a sign-in screen
- Tell it to draft only: nothing publishes until you say yes
Nothing is approved, scheduled or published until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
Manus uses a Bolta API key, so you create a key first. Takes about five minutes.
Research three recent trends in our industry, then use Bolta to save one LinkedIn draft and one Bluesky draft. Do not publish.
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
Two steps to a first draft
- 01
Create a Bolta key and add the connector
Make a key in Bolta under Settings, API Keys. In Manus, add an MCP server by URL named Bolta with https://mcp.bolta.ai/mcp and your key as the Bearer credential.
- 02
Ask for a draft, not a post
Tell Manus: use Bolta to list my brands, draft one LinkedIn post, show me the exact text, and do not publish. Read it in Bolta and say yes when you like it.
What is and is not confirmed
Read this before you set up Manus
- Confirmed from Manus's own docs: you can add a remote MCP server by HTTPS URL with an API key or Bearer token, and Manus tests the server and lists its tools. Skills can be uploaded too.
- Not confirmed: whether Manus supports OAuth sign-in for a custom MCP server. Manus documents keys and tokens, so this page uses a Bolta API key and does not promise sign-in.
- Not confirmed: which menu path your account shows (Manus docs describe two), which transport types it accepts, and whether any plan or region limits apply to custom connectors.
- Not confirmed: exactly how the Manus form takes the credential. Its docs say "API key, Bearer token, or other credentials" without naming fields or custom headers, and we have not run a full draft-and-review loop in Manus.
- Bolta is not listed in a Manus connector directory, so you add it by hand as a custom connector.
What Manus does and what Bolta does
Manus is the worker and Bolta is the place drafts land. Each step below names the Bolta tool Manus calls.
- 01
Manus checks which brand it is writing for
It asks Bolta for your workspaces so it knows the brand and does not guess. With several brands, name the one you mean in the task.
list-workspaces - 02
Manus looks at your connected accounts
It lists the accounts on that brand, so the drafts are aimed at networks you really have.
list-accounts - 03
Manus pulls your voice
Before writing, it reads the brand voice saved in Bolta, so a LinkedIn draft sounds like you and not like a generic assistant.
get-voice-context - 04
Manus does the research and the writing
The browsing, reading and drafting happen inside Manus. Bolta is not involved in this part.
- 05
Manus saves each version as a draft
One call per network. The draft appears in Bolta with the text exactly as Manus wrote it.
save-post - 06
You approve in Bolta
Open the draft, edit it, and say yes. Nothing is scheduled or published before that, and Bolta's own rules still apply when you do.
publish-post
Set up Manus
Connect once. Everything below works from Manus afterwards.
- 01
Create a Bolta API key
In Bolta, open Settings, API Keys (bolta.ai/dashboard/settings?tab=api) and create a key. Pick the brand it is for and tick only the permissions Manus needs. The key starts with bolta_sk_. Bolta shows it once, so copy it now.
- 02
Connect at least one social account
Drafts work without one, but publishing needs a connected account. If you have none yet, Manus can ask Bolta for a connect link later.
- 03
Open Manus's connector screen
Manus docs describe Connectors, then Create, then Add MCP by URL. Some accounts instead show Settings, Integrations, Custom MCP Servers, then Add Server. Use whichever your account shows, and update the app if you see neither.
- 04
Name it and paste the server address
Name the connector Bolta and paste https://mcp.bolta.ai/mcp as the server URL. Manus documents HTTPS URLs for custom servers.
- 05
Add the key as a Bearer header
Manus's docs list "API key, Bearer token, or other credentials" and do not name the fields. Pick the Bearer token or API key option and paste your bolta_sk_ key. If the form instead asks for a header, enter the name Authorization and the value Bearer bolta_sk_yourkey: the word Bearer, one space, then your key.
- 06
Save and check the tool list
Manus tests the server and should list Bolta's tools. An empty list or an error usually means the key or the Bearer prefix is wrong. See Troubleshooting below.
- 07
Optional: add the Bolta skill
In Manus, open Skills, then + Add, then Upload a skill. Manus accepts a .zip, a .skill file or a folder. Upload the skills/bolta folder from github.com/boltaai/bolta-skills. Manus also has Import from GitHub, but we have not tried it, and Bolta keeps its skill in a skills/ folder rather than at the repo root, so upload the folder instead.
- 08
Run a draft-only first task
Start a task: Use Bolta to list my brands, then draft one post and show me the exact text. Do not publish. Manus calls list-workspaces and save-post, and the draft appears in Bolta.
- 09
Approve it yourself
Open the draft in Bolta, edit it if you like, and approve it there, or tell Manus yes for that one post. You can delete the key in Settings, API Keys at any time to cut Manus off.
Connect Manus to Bolta
Manus uses a Bolta API key, so you create a key first. Takes about five minutes.
Which ways to connect Manus to Bolta are confirmed
Based on Manus's own documentation and what we have tried. We mark anything we could not confirm.
| Method | With Manus | How |
|---|---|---|
| Custom MCP connector with an API key | Not confirmed | Documented by Manus, not run with Bolta. Manus documents adding a remote MCP server by HTTPS URL with an API key or Bearer token. Use https://mcp.bolta.ai/mcp and a bolta_sk_ key. |
| Custom MCP connector with OAuth sign-in | Not confirmed | Manus's custom MCP docs describe keys and tokens only. We cannot promise a Bolta sign-in screen here. |
| Bolta skill upload | Not confirmed | Manus accepts a skill as a .zip, a .skill file or a folder. Upload the skills/bolta folder. We have not run a full task with it. |
| Import the skill from GitHub | Not confirmed | Manus's help center says a repo needs SKILL.md at its root, and Bolta keeps its skill inside a skills/ folder, so upload the folder instead. Manus's main skills page does not state the requirement. |
| Listed in a Manus connector directory | Not available | Bolta is not in one. You add it by hand as a custom connector. |
| Command line setup | Not available | We found no Manus command line route in its docs, so setup is done in the app. |
What you can run in Bolta from Manus
Each row is an area of Bolta, with the real tools behind it.
Draft a post per network from one task
Manus writes a different version for each account instead of one text pasted everywhere, then saves each as a draft.
save-postget-voice-contextRead your approval queue
Ask what is waiting and Manus lists posts and reply drafts so you can clear them in one sitting.
list-inbox-itemsWrite many drafts in one pass
For a content week, Manus can send a batch of drafts instead of one call each. Every item arrives as a draft, and Bolta finishes the batch in the background, so Manus checks again until it is done. Keep batches small.
bulk-create-postsCheck the posting rules before drafting
Manus can read the limits and rules for a connected account first, so drafts are not too long for the network.
get-posting-ruleslist-accountsLearn from how posts did
Manus reads account results from Bolta and suggests what to write next, based on the numbers it was given.
get-account-analyticslist-account-insightsPlan a routine you confirm
Manus can propose a repeating plan in Bolta. Nothing is saved until you confirm, and it is saved switched off.
planconfirm-plan
A Manus task that ends in a draft
An example of the shape of one task. Manus words things its own way.
- You
Read our last three blog posts and write a LinkedIn post and a Bluesky post about the shared theme. Use Bolta, save drafts only, and show me the text.
- Manus
I will start by checking which brand and accounts Bolta has for you.
- Tool call
list-workspacesReturns the brands you can reach.
- Tool call
list-accountsReturns the LinkedIn and Bluesky accounts connected to that brand.
- Tool call
get-voice-contextReturns the saved brand voice for the drafts.
- Manus
I read the three posts. The theme is that small teams skip documentation until it hurts. Here are the two versions. LinkedIn: a short story and a question. Bluesky: one tighter line plus the link. Want me to save these as drafts?
- You
Yes, save both as drafts. Do not schedule them.
- Tool call
save-postSaves each version as a draft on its own account.
- Manus
Both are saved as drafts in Bolta. Nothing is approved, scheduled or published. Open them in Bolta to edit, or tell me yes for one specific post.
Why Manus uses a Bolta API key
Bolta has two ways in. Manus's documented path fits only one of them.
API key (what this page uses)
Choose this for Manus, because its custom MCP form takes an API key or Bearer token.
The key acts as you directly. A post made through it is not held on your review list the way a signed-in post is, so Manus could schedule or publish if you ask it to. Safe Mode and required client sign-off in Bolta still apply. Use a scoped key and tell Manus to save drafts.
Sign-in (OAuth)
Choose this in apps that show a connect button, such as the Claude and ChatGPT setups.
Bolta shows a sign-in page and asks which brands the app may reach, and posts made this way wait on your list until you approve them. Manus's docs do not describe a sign-in flow for custom servers, so we do not promise it here.
What can Manus do with Bolta?
- Hand Manus a topic, let it research sources, then have it save one draft per network in Bolta
- Run a Manus Automation each Monday that drafts the week's posts into your Bolta review list
- Turn a long report or webinar recording Manus has already summarised into a LinkedIn post and a thread
- Have Manus read how last month's posts did, then draft next month's around the winners
- Ask Manus to check what is waiting for approval and list it so you can clear the queue in one sitting
- Give Manus a competitor's launch page to read, then draft a differently angled post in your voice
What is the Bolta MCP?
The server Manus talks to when it works with Bolta.
MCP, the Model Context Protocol, is the open standard that lets an AI app call tools in another product. Bolta runs a hosted MCP server at https://mcp.bolta.ai/mcp. Your AI app discovers its 67 tools and calls them for you: list your brands, save a draft, plan a routine, read results.
One connection is one organization. You tick the brands the app may reach, and every call is checked against your role, so the app can never do more in Bolta than you can. Approving, scheduling and publishing need your yes.
Brands & accounts6 tools
The brands this connection reaches, who works on them and who can approve, their approval settings, connected social accounts, and each platform's posting rules.
list-workspaces, list-workspace-members, set-brand-approval, list-accounts, get-connect-link, get-posting-rules
Posts9 tools
Save a draft or edit a post with save-post, then publish it now or at a time with publish-post after the user says yes.
list-workspace-posts, get-post, save-post, publish-post, delete-post, bulk-create-posts, create-wordpress-blog-post, list-recently-deleted, restore-deleted
Review4 tools
Everything waiting for a yes: submit drafts to the team or send them to a named person for approval, approve one or many, reject with a reason, and work the inbox of routine and campaign drafts.
list-inbox-items, submit-for-review, approve-many-posts, reject-post
Plans6 tools
Have Bolta plan a routine or a campaign the way its own chat does, change it, then save it on the user's yes.
plan, plan-routine, plan-campaign, recommend-routines, revise-plan, confirm-plan
Routines10 tools
Work that repeats and runs in Bolta even with the app closed.
list-routine-templates, list-routines, get-routine, create-routine, update-routine, activate-routine, pause-routine, archive-routine, run-routine-now, list-routine-runs
Campaigns6 tools
One to four weeks of posts about one thing: a launch, an event, a season.
list-content-campaigns, get-content-campaign, create-content-campaign, update-content-campaign, analyze-content-campaign-source, set-content-campaign-status
Team versions4 tools
One idea written as one post per person on the team, each in their own voice.
plan-team-posts, update-team-post-plan, generate-team-post-drafts, get-team-post-plan
Voice & business8 tools
The brand's voice and business facts, and writing in that voice.
get-voice-context, get-voice-profile, create-voice-profile, update-voice-profile, list-business-dna, extract-business-dna, update-business-dna, voice-generate
Suggestions2 tools
What Bolta suggests changing, for a routine or the whole brand, from what people approved, edited and rejected.
list-suggestions, decide-suggestion
Replies10 tools
Find conversations worth joining, draft replies in the brand voice, and send them once the user says yes.
search-engagement-opportunities, list-engagements, get-social-content, draft-engagement-reply, draft-inbound-reply, publish-engagement-reply, reply-to-social-content, react-to-social-content, send-outreach-reply, update-outreach-reply
Results2 tools
How posts and accounts are performing.
list-account-insights, get-account-analytics
Six things to ask Manus
Replies are illustrative. Manus decides how it words them.
Research what people are saying about remote onboarding this week, then draft one LinkedIn post and one X post in our voice. Save as drafts only.
I read four recent articles and saved two drafts in Bolta, one for LinkedIn and one for X, both in your brand voice. I did not publish or schedule either. Open them in Bolta to edit, or tell me yes for one.
get-voice-context, save-post, list-accounts
What is waiting for my approval in Bolta?
You have 6 items waiting: 4 posts and 2 reply drafts. I have not approved any of them. Tell me which to approve or reject, or review them in Bolta.
list-inbox-items
Plan a weekly routine that drafts three posts every Monday from our latest blog articles, and show me the plan before saving.
Here is the plan: Mondays at 8am, three drafts from new blog articles, sent to your review list. It is not saved yet. Say yes and I will save it switched off, then you can turn it on separately.
plan, confirm-plan
How did our LinkedIn account do over the last 30 days? Then suggest the next three post topics.
Here is the summary Bolta returned for the last 30 days. Based on it, I suggest three topics. I can save each as a draft if you want them.
get-account-analytics, list-accounts
Before drafting for Bluesky, check Bolta's posting rules for that account, then write one post that fits.
I read the rules for your Bluesky account and wrote one post inside the length limit. It is not saved yet. Say yes and I will save it as a draft.
get-posting-rules, list-accounts
Turn the summary of last week's webinar into five drafts for LinkedIn, spread across the week. Save them as drafts.
I wrote five drafts from the summary and saved them in Bolta as drafts for LinkedIn. None are scheduled. Check the order in Bolta and tell me which to move or drop.
bulk-create-posts, get-voice-context
List the posts I deleted in the last week and tell me if any are worth bringing back.
Bolta lists three posts deleted in the last 7 days. One looks reusable. I have not restored anything. Tell me which one and I will bring it back.
list-recently-deleted, restore-deleted
Networks Manus can draft for through Bolta
- X
- Threads
- Bluesky
Drafts can target any account you have connected in Bolta. Publishing needs the account connected first.
What runs without you watching
Manus is a hosted agent, so a task can keep going after you close the tab. What continues depends on which side holds the schedule.
- A Manus Automation can start a task on a schedule or from an event. We have not run one unattended with Bolta, so test it once by hand.
- A Bolta routine runs on Bolta's side even when Manus is closed. Manus can plan it, but you confirm and switch it on yourself.
- A draft already saved in Bolta stays there until you act on it. Nothing publishes because a Manus task finished.
- A key that was deleted or lacks a permission makes a scheduled Manus task fail on its Bolta step, so check the key before you rely on it.
Unattended runs should save drafts or ask for review, not publish.
Which Bolta key to use, and why Manus needs one
Bolta's hosted server accepts a sign-in or an API key. Manus's custom MCP docs list an API key or Bearer token, so a key is the route this page describes.
A key looks like bolta_sk_ followed by random characters. You make it under Settings, API Keys in Bolta, and Bolta shows it once. Treat it like a password: do not paste it into a shared document or a screenshot.
If Manus later adds sign-in for custom servers, that is the safer option. We have not confirmed that it exists.
Give Manus a scoped key
When you create a key you pick a brand and tick permissions. Tick only what the job needs.
A key without a permission gets a 403 when Manus tries that action. If one is missing, make a new key with it ticked and swap it into Manus.
| Job | What the key needs |
|---|---|
| Read brands, accounts and the review list | Read permissions only |
| Draft posts and save them | Read permissions plus the permission to write posts |
| Anything beyond drafting | Leave it off until you trust the setup. Which permissions exist is listed when you create the key |
Tell Manus to save drafts, not publish
A key acts as you, and it skips the hold that sign-in gives. So the safest habit is to say it in every prompt or in a saved instruction: save drafts only, show me the exact text, do not approve or publish.
Bolta's own rules still apply on top. Safe Mode, role checks and required client sign-off are enforced on the Bolta side, and a refusal from Bolta is final. Manus is not able to work around one.
- Ask for the exact text before anything is approved.
- Keep the key's permissions narrow while you test.
- Check the first few drafts in Bolta before you trust a whole routine.
Manus Automations that draft into Bolta
Manus has Automations that start a task on a schedule or from an event. Pair one with Bolta and you get a weekly content run that ends in your review list.
We have not tested an unattended Manus Automation with Bolta end to end, so run it once by hand first. If you want the schedule to live in Bolta instead, ask Manus to plan a routine with Bolta's plan tool and confirm it yourself.
- 01
Write the task once
For example: every Monday, read last week's blog posts, then use Bolta to save five drafts for LinkedIn and Bluesky. Do not publish.
- 02
Let it run in Manus
Manus starts the task by itself. Bolta only receives the draft requests, and each one lands as a draft.
- 03
Review in Bolta
Open your review list, edit what you want, and approve. Nothing goes out because a Manus task ran.
Research, write, then save: one task
Manus is built for tasks with several steps. Give it the whole chain at once: read these three pages, write a version for each network, then save them through Bolta. Manus does the reading and writing, and Bolta handles the voice, the accounts and the review list.
Manus tool calls can time out when a call runs long. Bolta calls are short, but we have not tested long tasks, so ask for a few drafts at a time rather than fifty.
Using the Bolta skill next to the connector
The connector gives Manus the tools. The skill is a text file of instructions about when to use them and what to ask you first. You can run the connector alone and add the skill later.
Manus lists three ways to add a skill: upload a .zip, upload a .skill file, or upload a folder. Bolta's skill lives in the skills/bolta folder of boltaai/bolta-skills, so upload that folder. Manus can also import a public GitHub repo, but Manus's help center says the repo needs SKILL.md at its root, so we point you at the upload route.
We have not measured whether the skill changes Manus's behavior. Judge it by the first few drafts.
Let Manus read results before it writes the next batch
Manus is good at reading a lot and summarising it, which fits post results.
Results can lag after a post goes out, so a very recent post may show low numbers that will rise.
- 01
Ask for the numbers first
Tell Manus to pull account results from Bolta for a period you choose and name the top and bottom posts.
- 02
Ask for reasons, not just a list
Have it say what the better posts had in common. Treat that as a guess from the numbers it received, not proof.
- 03
Draft from the findings
Then ask for a few drafts that follow the pattern, saved as drafts for your review.
Where Manus stops and your review starts
Manus can browse, read files and write. It cannot decide what is on brand for you, and with a key it does not wait for a hold. The handoff is your review in Bolta.
A clear habit is one sentence at the end of every task: save drafts, show me the exact text, do not approve or publish. Put it in a saved instruction in Manus if it offers one, so you do not have to retype it.
- Manus owns research and first drafts.
- Bolta owns accounts, voice and the review list.
- You own the yes.
What Manus cannot do without you
Manus connects as: Custom MCP connector (add by URL).
Drafts are free, finals need your yes
Manus can write, edit and save drafts at any time. Approving, scheduling, publishing, sending a reply, activating a routine or campaign and deleting each wait for your yes, shown against the exact text.
One connection, one organization
When you connect Manus you tick the brands it may reach. It reaches only those, and when that is more than one brand, every call names the brand it is for.
Your role is the ceiling
Each call Manus makes is checked like a normal request from you. Owners and admins can act on any post, creators on Bolta's drafts and on posts they are a named reviewer on, and viewers never approve or publish.
Where Manus can publish through Bolta
11 social networks, plus WordPress for articles. Bolta holds the connected accounts. Each card opens the Manus guide for that network.
- Threadstext posts, image posts, polls
- LinkedIntext posts, articles, carousels
- X (Twitter)tweets, threads, polls
- Instagramposts, stories, reels
- Facebookposts, stories, reels
- Blueskyposts, threads, quote posts
- Mastodontoots, polls, threads
- Reddittext posts, link posts, image posts
- TikTokvideos, stories, photo posts
- YouTubevideos, Shorts, community postsTeam plan, beta
- Pinterestpins, idea pins, video pinsTeam plan, beta
The words behind Manus and Bolta
For Manus: Custom MCP connector (add by URL), signing in with API key (Bearer token).
- MCP
- The Model Context Protocol, an open standard that lets an AI app call tools in another product. Bolta's hosted server is at https://mcp.bolta.ai/mcp, and Manus reaches Bolta through a connection like it.
- Skill
- A folder of instructions an AI app reads so it knows how to use Bolta well. It does not connect by itself: install it with
npx skills add boltaai/bolta-skills --skill boltanext to the connection. - Plugin
- A bundle that brings the connection and the skill in one install, where the app supports plugins. Claude Code has one, added with its plugin marketplace commands.
- API key
- A
bolta_sk_key you create in Settings, sent as a Bearer header. It carries the permissions you choose, which suits apps you configure by hand or anything that runs unattended.
Setup for Manus is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.
Manus connector or Bolta skill?
The connector gives Manus Bolta's tools. The Bolta skill is a set of instructions that tells an agent how to use them well. Manus can take both, and the connector is the part that does the work. The skill is optional.
Other AI agents that post through Bolta
Every agent below connects to the same Bolta workspace and follows the same approval rules.
- ChatGPTOpen Bolta in ChatGPT, sign in
- OpenAI dotsAlways-on ChatGPT agents
- ClaudeCustom connector, one sign-in
- Claude DuetCarries your Claude connectors over
- Claude CoworkPlugin and connector on your desktop
- Claude CodeTwo plugin commands
- Codexcodex mcp add, then sign in
- CursorOne mcp.json entry
- GeminiGemini CLI extension
- OpenClawSkills and MCP for your gateway
- Hermes AgentMCP server in the Hermes config
- Grok BotCustom connector in xAI's agent
- Grok Buildgrok mcp add
- DeepSeekThrough the Bolta MCP link
- Kimi K3Kimi Code with the Bolta MCP server
- MuseMeta's agent, Muse Code and connectors
- CueA personal agent that posts for you
- PerplexityResearch there, draft in Bolta
- Perplexity ComputerRemote MCP connector
- nanoclawRun it from WhatsApp or Telegram
- PaperclipConnector for your agent company
- MCP ServerOne link for any MCP client
Related
What Manus can do through Bolta
The jobs Bolta's agents cover, each with its own page. Your AI app can ask for drafts, plans and reports in the same areas. Every post still waits for your yes.
Frequently asked questions
Short answers about using Manus with Bolta.
- Does Manus need an API key to connect to Bolta?
- On the route we describe, yes. Manus's docs list an API key or Bearer token for custom MCP servers, so you create a bolta_sk_ key in Bolta and send it as a Bearer header. Whether Manus can do a sign-in flow for custom servers is not confirmed.
- Can Manus publish posts without my approval?
- It should not, if you tell it to save drafts, but a key acts as you and skips the hold that sign-in gives. So Manus could schedule or publish if you ask it to. Safe Mode and required client sign-off in Bolta still apply, and a scoped key limits what is possible.
- Where do I add a custom MCP server in Manus?
- Manus's docs describe Connectors, then Create, then Add MCP by URL. Another Manus page describes Settings, Integrations, Custom MCP Servers, then Add Server. Your account may show either.
- Can I use the Bolta skill in Manus too?
- Possibly, but it is optional and untested. Manus accepts skills uploaded as a .zip, a .skill file or a folder, so upload the skills/bolta folder from boltaai/bolta-skills. We have not tried Manus's GitHub import, and the skill is not at the repo root.
- Can Manus run Bolta tasks on a schedule?
- Manus has Automations that start tasks on a schedule or from events, so a weekly drafting task is possible. We have not tested one unattended with Bolta. You can also keep the schedule in Bolta by having Manus plan a routine that you confirm.
- How do I revoke Manus access to Bolta?
- Delete the key in Bolta under Settings, API Keys. Manus stops working with Bolta at once. You can also remove the connector inside Manus.
- Does Manus work with more than one brand?
- Yes, Bolta supports several brands. You pick a brand when you create a key, so use one key per brand and name the brand in your prompt. Manus can list your brands with Bolta's list-workspaces tool.
- Is Bolta in the Manus connector directory?
- No. Some tools are listed there, but Bolta is not, so you add it yourself as a custom connector. That is the manual route on this page.
- Does it cost extra to use Bolta with Manus?
- Manus's own plans and any limits on custom connectors are set by Manus, and we have not confirmed them. For what Bolta includes on each plan, see the Bolta pricing page.
- Is Manus still available?
- Its docs are live as we write this. We have not confirmed Manus's current ownership or plans, so check manus.im before you build a routine on it.
- Which Bolta tools does Manus use for a first draft?
- Usually list-workspaces to find the brand, list-accounts to see the networks, get-voice-context to read your voice, and save-post for each draft. Manus decides the order, so you may see slightly different calls.
- Why does my Manus task say it cannot publish?
- Most likely the post needs your approval first, or the key lacks a permission the action uses. Both are intended. Approve the draft yourself in Bolta, or make a new key with the permission you want.
If something does not work
Quick fixes for the common snags.
- The Bolta connector shows no tools after saving.
- Check the Authorization value first. It must be the word Bearer, one space, then the full bolta_sk_ key. Check the URL is exactly https://mcp.bolta.ai/mcp. If both look right, remove the connector and add it again.
- Bolta says Invalid or expired API key.
- The key was typed wrong, revoked or deleted. Create a new key in Settings, API Keys, and replace the old one in Manus. Retrying with the same key will not help.
- A tool answers 403 or says permission is missing.
- The key does not have that permission, for example writing posts. Create a new key with the right boxes ticked and swap it into the connector.
- I cannot find Add MCP by URL in Manus.
- Manus's docs describe two paths: Connectors, Create, Add MCP by URL, and Settings, Integrations, Custom MCP Servers, Add Server. Manus says availability can depend on your account. Update the app, and check Manus's own docs if neither shows.
- A long task times out partway through.
- Manus requests can time out if a tool call runs long. Split the work: ask for three or four drafts per task, then repeat. Check Bolta first, because some drafts may already be saved.
- Manus picked the wrong brand or asked which one.
- Name the brand in your prompt, for example for Acme Coffee. If you have several brands, create a key for the one you want and use that key.
Ready to schedule social media posts with Manus?
Connect Manus and ask for your first draft. Nothing goes out until you say yes.