---
title: "Manus integration with Bolta"
description: "Add Bolta to Manus as a custom MCP connector with an API key. Manus drafts per-platform posts, Bolta holds them for your approval. Setup steps, scoped keys and an honest list of what is unconfirmed."
canonical_url: "https://bolta.ai/integrations/manus"
markdown_url: "https://bolta.ai/integrations/manus.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Manus integration with Bolta

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

Add Bolta to Manus as a custom MCP connector with an API key. Manus drafts per-platform posts, Bolta holds them for your approval. Setup steps, scoped keys and an honest list of what is unconfirmed.

## Summary

Let Manus research, write and save posts to Bolta for your review

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- 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

## Limitations and boundaries

- 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.
- 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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: Read brands, accounts and the review list; What the key needs: Read permissions only | Job: Draft posts and save them; What the key needs: Read permissions plus the permission to write posts | Job: Anything beyond drafting; What the key needs: 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. 1. 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. 2. Let it run in Manus: Manus starts the task by itself. Bolta only receives the draft requests, and each one lands as a draft. 3. 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. 1. 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. 2. 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. 3. 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.

## 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.

## 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.

## 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.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/claude](https://bolta.ai/integrations/claude)
- [Related page: /integrations/chatgpt](https://bolta.ai/integrations/chatgpt)
- [Related page: /integrations/perplexity-computer](https://bolta.ai/integrations/perplexity-computer)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

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