Integration

Manus integration

Manus is an autonomous AI agent. Start a Manus task from a prompt, follow it through its event messages, answer its questions or confirm the actions it proposes, stop, rename, share or delete tasks, and read the generated files from the Manus Library. Also organize tasks in projects with shared instructions, list installed skills and connectors, message and update custom agents, read credit balance and usage, manage task webhooks, and inspect, publish or update websites Manus built. Not exposed: file upload (it hands back a presigned URL the file bytes must be PUT to, which these tools cannot do; attach a file to a message by public URL or base64 data instead) and the deprecated v1 API. Authentication is a Manus API key, created under Settings, Developers, sent in the x-manus-api-key header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Manus.Built from the 34 Manus tools below, on the connection you add once.

What you can do with Manus

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Task, 6 operations

  • create_taskCreate taskPOSTStarts a Manus agent task from a prompt. It runs in the background and consumes Manus credits. Returns task_id at once: poll get_task until status is stopped, waiting or error, then read the answer and files with list_task_messages.
  • delete_taskDelete taskPOSTPermanently deletes a task and its history. Stop a running task with stop_task first; agent-related tasks cannot be deleted.
  • get_taskGet taskGETReturns a task's status (running, stopped, waiting, error or deleted), title, credit usage, profile and URLs. Use list_task_messages for the agent's answers and files, or send_task_message to continue.
  • list_tasksList tasksGETLists tasks with optional filtering and cursor-based pagination. Use `scope` to filter by task type, e.g. `agent_subtask` with `agent_id` for agent subtasks. See get_task for full details on a specific task.
  • stop_taskStop taskPOSTStops a running task; its status becomes stopped. A stopped task can be resumed later with send_task_message.
  • update_taskUpdate taskPOSTChanges a task's title, who can view it (public lets anyone holding share_url read it) and whether it shows in the Manus task list. Leave a field out to keep it. Read the current values with get_task.

Project, 4 operations

  • create_projectCreate projectPOSTCreates a new project. Projects let you group related tasks and apply shared instructions. Pass the returned ID as `project_id` in create_task to create tasks within this project.
  • get_projectGet projectGETRetrieves a project's full configuration: name, instruction, default connectors, and default skills.
  • list_projectsList projectsGETLists all projects. Use the returned IDs as `project_id` in create_task or list_tasks.
  • update_projectUpdate projectPOSTUpdates a project's name, instruction, default connectors, or default skills. Omitted fields are unchanged; a request with no updatable field returns `400 invalid_argument`. `connector_ids` and `skill_ids` replace the entire list.

Agent, 3 operations

  • get_agentGet agentGETRetrieves an agent's details including its nickname, description, and associated task. Use update_agent to modify, or list_tasks with `scope=agent_subtask` to view this agent's subtasks.
  • list_agentsList agentsGETLists all custom agents in your account. Use the returned IDs in list_tasks with `scope=agent_subtask` to view subtasks, or in get_agent for full details.
  • update_agentUpdate agentPOSTUpdates an agent's nickname and description. Use get_agent to view current values before updating.

Webhook, 3 operations

  • create_webhookCreate webhookPOSTRegisters an HTTPS URL that Manus will POST task events to (task_created, task_stopped, task_deleted). Manus first sends a test request that must get HTTP 200 within 10 seconds. Verify deliveries with the key from get_webhook_public_key.
  • delete_webhookDelete webhookPOSTDeletes a webhook. The endpoint will stop receiving notifications immediately. Use list_webhooks to find the webhook ID.
  • list_webhooksList webhooksGETLists the webhooks of your account with their id, status and creation time; the URL is not returned, because a webhook URL can carry a token. Use the ids with delete_webhook.

Website, 3 operations

  • get_website_statusGet website statusGETRetrieves a website's current title, publish status, live URL, screenshot, and visibility. Use list_website_checkpoints to browse version history, or publish_website to deploy changes.
  • publish_websitePublish websitePOSTDeploys the latest checkpoint of a website built by Manus at the chosen visibility (public: reachable by anyone). Runs asynchronously: poll get_website_status until publish_status is published or failed.
  • update_websiteUpdate websitePOSTChanges a Manus website's title, visibility (public: reachable by anyone) or automatic publishing, without deploying. Leave a field out to keep it. Pass exactly one of task_id or website_id.

Skill, 2 operations

  • get_skillGet skillGETRetrieves one skill's details and a temporary download URL for its current archive.
  • list_skillsList skillsGETLists installed skills available for task selection.

Task message, 2 operations

  • list_task_messagesList task messagesGETLists event messages for a task with cursor-based pagination. Use this to poll for progress after create_task or send_task_message.
  • send_task_messageSend task messagePOSTSends a follow-up message to a task, which resumes the agent and consumes credits. Also answers its questions (messageAskUser, cascadeAskUser). A pending action confirmation is skipped by a message: use confirm_task_action to approve it.

Team usage, 2 operations

  • get_team_daily_usageGet team daily usageGETReturns daily credit consumption totals for the team over a date range. Owners and admins see the whole team; members see only their own consumption.
  • list_team_usage_by_memberList team usage by memberGETLists, per team member, the number of tasks created and credits consumed over a date range, with each member's name and email. Owners and admins see every member; members see only their own row.

Artifact, 1 operation

  • list_artifactsList artifactsGETLists files and sites generated by your tasks in the Manus Library (documents, slides, spreadsheets, images, videos, audio, websites, apps), newest first, with download or site URLs. Filter by type, name or favorites.

Browser, 1 operation

  • list_online_browsersList online browsersGETLists the user's online browser clients. Use the returned `client_id` with confirm_task_action when the agent triggers a `needConnectMyBrowser` waiting event.

Connector, 1 operation

  • list_connectorsList connectorsGETLists connectors installed in the current user's account. Use the returned IDs in the `connectors` array of create_task or send_task_message.

Credit balance, 1 operation

  • get_available_creditsGet available creditsGETReturns the credit balance, subscription period, and refresh information for the authenticated caller. For a team sub-account, the team's shared pool balance is returned; for a personal account, the personal balance is returned.

Credit usage, 1 operation

  • list_credit_usageList credit usageGETLists the current user's credit change history at session granularity, sorted by change time (newest first).

Task action, 1 operation

  • confirm_task_actionConfirm task actionPOSTApproves an action the agent is waiting on (for example sending a Gmail or Outlook email, a deploy, a terminal command, a calendar change), which then runs. Take event_id from status_update.status_detail.waiting_for_event_id in list_task_messages.

User, 1 operation

  • get_current_userGet current userGETReturns the Manus account behind the API key: user_id, and the display name, email and avatar URL of that user (personal data of the account owner).

Webhook public key, 1 operation

  • get_webhook_public_keyGet webhook public keyGETReturns the PEM-encoded RSA public key (algorithm RSA-SHA256) used to verify the signatures on Manus webhook deliveries.

Website checkpoint, 1 operation

  • list_website_checkpointsList website checkpointsGETReturns the website's current title and lists all of its checkpoints, newest first. Match `published_version_id` against `data[].version_id` to identify the live checkpoint, or call publish_website to deploy the latest.

Use Manus from Claude Code, Cursor or Codex

Connect Manus in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Manus operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Manus

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Manus once

    Add your Manus connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Manus integration FAQ

What can you do with the Manus integration?

LiveContext exposes 34 operations on Manus, covering task, project, agent and webhook.

Popular integrations

Browse the whole catalog