How to connect Manus to OpenClaw
Connect Manus to OpenClaw with ClawLink: paste your Manus key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
ManusAPI KEYMCPAI-powered task automation and workflow management platform.. Once connected, OpenClaw can read and act on Manus from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Manus access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Manus setup: install one ClawHub skill, connect Manus in the browser, and OpenClaw can call real Manus actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Manus.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Manus
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Manus?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Manus in the ClawLink dashboard — paste your Manus API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Manus, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Manus is connected in the dashboard, that agent calls the same 14 Manus tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Manus MCP for OpenClaw
Looking for a Manus MCP server for OpenClaw? ClawLink connects Manus to OpenClaw and exposes 14 Manus tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Manus integration works the same way.
What the OpenClaw Manus integration can do
14 Manus tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 14.
11 of 14 Manus tools for OpenClaw
| Tool | What it does |
|---|---|
Get file manus_get_file | Retrieves details of a specific file by ID, including its status and metadata |
Get task manus_get_task | Retrieves details of a specific task by ID, including status, output messages, credit usage |
Get webhook public key manus_get_webhook_public_key | Retrieves the RSA public key used for verifying webhook signatures |
List files manus_list_files | Retrieves a list of the 10 most recently uploaded files |
List projects manus_list_projects | Retrieve a list of all projects in your account with optional pagination |
List tasks manus_list_tasks | Retrieves a list of tasks with optional filtering and pagination |
Create file manus_create_file | Create a file record and obtain a presigned URL for uploading file content to S3 |
Create project manus_create_project | Create a new project with default instructions |
Create task manus_create_task | Creates a new AI task with custom parameters, attachments, and optional connectors |
Create webhook manus_create_webhook | Register a webhook to receive real-time task notifications |
Update task manus_update_task | Updates a task's metadata such as title, sharing settings, and visibility in the task list |
Try it: find the Manus tool you need
Browse the 11 Manus tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Manus, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Manus, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Manus, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Manus, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Manus working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Manus API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Manus account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Manus. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Manus actions to the runtime in a format your agent can reliably use. | 14 tools for Manus are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Manus to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Manus in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Manus key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Manus skill but can't call the tools
The ClawHub skill teaches OpenClaw about Manus, but the calls run through the ClawLink plugin and your connected account. Make sure Manus is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Manus from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Manus tools
Manus tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Manus call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Manus returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Manus has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Manus integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Manus: link your Manus account once in the browser and OpenClaw can call the Manus API through 14 ready-made tools — no custom code or token handling.
How do I add Manus to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Manus skill from ClawHub, then you click Connect in the dashboard to authorize Manus. OpenClaw calls the tools from the next message — no config files, and the Manus key you paste is stored server-side instead of in your environment.
How long does it take to connect Manus to OpenClaw?
About two minutes. Sign in, click Connect next to Manus in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Manus up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Manus working from chat.
OpenClaw installed the Manus skill but can't call the tools
The ClawHub skill teaches OpenClaw about Manus, but the calls run through the ClawLink plugin and your connected account. Make sure Manus is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
