Skip to main content

MANUS-MCP

Managed Manus MCP rollout for async agent tasks, projects, files, webhooks, usage, connectors, browsers, and website publishing.

Authentication​

  • Header: Authorization

  • Format: Bearer mad_live_***

  • This service reference is generated from the active immutable Portal catalog.

Catalog Coverage​

  • Raw provider tools: 38
  • Exposed compatibility tools: 38
  • Agent-ready tools: 38
  • Documented descriptors: 38
  • Public reference pages: 38
  • Source repository: https://github.com/MADPANDA3D/MANUS-MCP
  • Catalog version: manus-2026.07.12.2
  • Catalog verified: 2026-07-12T09:22:08.263693+00:00 (5 days old)
  • Guide verified: not manually verified (not verified)
  • Committed snapshot: catalog-5ec40de147b11c40
  • Docs generated: 2026-07-18T00:19:58.776Z

Read-only Tools​

  • Check Manus MCP configuration — Use this local read-only navigation tool to verify the Portal grant gate, request-scoped Manus BYOK mode, public endpoint, catalog identity, and provider-credential readiness. It does not contact Manus and returns only booleans and safe mode names; it never returns a Portal grant, Manus API key, or request header value.
  • Check Manus task progress — Use this read-only polling helper after creating or continuing a Manus task. It contacts the configured Manus task message endpoint with the request-scoped x-manus-api-key and returns a compact status, waiting-event guidance, latest result summary, and recommended check-back time. It does not modify the task and redacts provider secrets.
  • Find Manus tools — Use this local read-only navigation tool to rank Manus capabilities with punctuation-normalized, multi-token matching across native and canonical names, aliases, titles, descriptions, and categories. Optional category and risk filters narrow results; the default searches only agent-ready tools. It never contacts Manus or changes state.
  • Get a complete Manus tool reference — Use this local read-only navigation tool after discovery to resolve a native name, canonical name, or compatibility alias to one complete lossless descriptor. The result includes every parameter meaning, output contract, annotation, risk and confirmation rule without executing the target or contacting Manus.
  • Get Agent Detail — Use this Manus read tool when you need to read details for a manus custom agent. It contacts the configured Manus API v2 GET /v2/agent.detail endpoint and requires a request-scoped x-manus-api-key. Reads agent metadata. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Get File Detail — Use this Manus read tool when you need to read manus file upload status, size, content type, and expiration. It contacts the configured Manus API v2 GET /v2/file.detail endpoint and requires a request-scoped x-manus-api-key. Reads file status, size, and expiry. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Get Task Detail — Use this Manus read tool when you need to read a manus task's current status and metadata. It contacts the configured Manus API v2 GET /v2/task.detail endpoint and requires a request-scoped x-manus-api-key. Reads task status and metadata. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Get Team Usage Statistic — Use this Manus read tool when you need to read team daily credit totals if the byok account has team access. It contacts the configured Manus API v2 GET /v2/usage.teamStatistic endpoint and requires a request-scoped x-manus-api-key. Team-only daily credit totals. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Get Webhook Public Key — Use this Manus read tool when you need to get manus rsa public key for verifying webhook signatures. It contacts the configured Manus API v2 GET /v2/webhook.publicKey endpoint and requires a request-scoped x-manus-api-key. Reads RSA public key for webhook verification. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Get Website Status — Use this Manus read tool when you need to read publish status, live urls, visibility, and latest version for a website. It contacts the configured Manus API v2 GET /v2/website.status endpoint and requires a request-scoped x-manus-api-key. Reads publish status and site URLs. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Inspect Manus endpoint coverage — Use this local read-only navigation tool to map official Manus API v2 endpoints to native tools, methods, provider documentation, risk classes, and implementation status. Filter by capability area or status when auditing a workflow. It never contacts Manus, changes state, or returns credential values.
  • List Agents — Use this Manus read tool when you need to list custom manus agents and their main task ids. It contacts the configured Manus API v2 GET /v2/agent.list endpoint and requires a request-scoped x-manus-api-key. Lists custom agents and their main task IDs. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Connectors — Use this Manus read tool when you need to list installed manus connectors for use in task messages. It contacts the configured Manus API v2 GET /v2/connector.list endpoint and requires a request-scoped x-manus-api-key. Lists installed connector IDs for task creation. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Manus capabilities and descriptors — Use this local read-only navigation tool to inspect the deterministic Manus ToolManifest. The compact default returns immutable catalog identity and raw, agent-ready, legacy, and hidden counts; set include_descriptors=true for all 38 lossless descriptors, complete input and output schemas, aliases, risk annotations, confirmation rules, build SHA, and hashes. It never contacts Manus or reveals credential values.
  • List Online Browsers — Use this Manus read tool when you need to list online manus browser clients; user-agent is redacted by default. It contacts the configured Manus API v2 GET /v2/browser.onlineList endpoint and requires a request-scoped x-manus-api-key. Lists online browser clients; user-agent redacted by default. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Projects — Use this Manus read tool when you need to list manus projects for project_id selection. It contacts the configured Manus API v2 GET /v2/project.list endpoint and requires a request-scoped x-manus-api-key. Lists projects for project_id selection. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Skills — Use this Manus read tool when you need to list manus skills for enable_skills and force_skills. It contacts the configured Manus API v2 GET /v2/skill.list endpoint and requires a request-scoped x-manus-api-key. Lists skills, optionally including project skills. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Task Messages — Use this Manus read tool when you need to poll manus task events in compact form; use for async status and results. It contacts the configured Manus API v2 GET /v2/task.listMessages endpoint and requires a request-scoped x-manus-api-key. Polls event stream; check_task_progress wraps it for compact status. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Tasks — Use this Manus read tool when you need to list manus tasks with cursor pagination and optional worker/subtask scope. It contacts the configured Manus API v2 GET /v2/task.list endpoint and requires a request-scoped x-manus-api-key. Supports cursor pagination and task scope filters; project_id selects project scope. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Team Usage Log — Use this Manus read tool when you need to read team member usage; emails are redacted unless include_emails is true. It contacts the configured Manus API v2 GET /v2/usage.teamLog endpoint and requires a request-scoped x-manus-api-key. Team-only per-member usage; emails redacted by default. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Usage — Use this Manus read tool when you need to list current user's manus credit change history. It contacts the configured Manus API v2 GET /v2/usage.list endpoint and requires a request-scoped x-manus-api-key. Reads current user's credit history. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Webhooks — Use this Manus read tool when you need to list configured manus webhooks. It contacts the configured Manus API v2 GET /v2/webhook.list endpoint and requires a request-scoped x-manus-api-key. Lists configured webhooks. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • List Website Checkpoints — Use this Manus read tool when you need to list manus website checkpoint/version history. It contacts the configured Manus API v2 GET /v2/website.listCheckpoints endpoint and requires a request-scoped x-manus-api-key. Lists checkpoint history. This is read-only and does not change remote state. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Wait briefly for a Manus task — Use this bounded read-only polling helper only when waiting up to 60 seconds is appropriate. It repeatedly contacts the Manus task message endpoint using the request-scoped x-manus-api-key, stops when the task completes, fails, or needs input, and returns control with explicit next-action guidance. It never mutates or automatically retries the task itself.

Write and Destructive Tools​

  • Confirm Task Action — Use this Manus destructive tool when you need to confirm a manus waiting action. use only after user approval. It contacts the configured Manus API v2 POST /v2/task.confirmAction endpoint and requires a request-scoped x-manus-api-key. Confirms waiting send/deploy/terminal/spend actions; confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Create an asynchronous Manus task — Use this Manus spend tool when you need to create, start, or run asynchronous AI agent work from a user-approved instruction. It contacts the configured Manus API v2 POST /v2/task.create endpoint with the request-scoped x-manus-api-key and can consume credits. The call is dry-run by default and requires confirm=true after explicit approval; the Agent Contract destructive executor also enforces the exact manifest confirmation phrase. The result contains a stable task ID, URLs when provided by Manus, a recommended check-back interval, and next-action guidance without any credential value.
  • Create File Upload — Use this Manus write tool when you need to create a manus file record and presigned upload url. requires confirmation. It contacts the configured Manus API v2 POST /v2/file.upload endpoint and requires a request-scoped x-manus-api-key. Creates file record and presigned upload URL; confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Create Project — Use this Manus write tool when you need to create a manus project with shared instructions. requires confirmation. It contacts the configured Manus API v2 POST /v2/project.create endpoint and requires a request-scoped x-manus-api-key. Creates shared instructions container; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Create Webhook — Use this Manus write tool when you need to register a manus webhook callback url. requires confirmation. It contacts the configured Manus API v2 POST /v2/webhook.create endpoint and requires a request-scoped x-manus-api-key. Registers callback URL; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Delete File — Use this Manus destructive tool when you need to delete a manus file early. requires explicit confirmation. It contacts the configured Manus API v2 POST /v2/file.delete endpoint and requires a request-scoped x-manus-api-key. Deletes uploaded file early; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Delete Task — Use this Manus destructive tool when you need to permanently delete a manus task. requires explicit confirmation. It contacts the configured Manus API v2 POST /v2/task.delete endpoint and requires a request-scoped x-manus-api-key. Permanent task deletion; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Delete Webhook — Use this Manus destructive tool when you need to delete a manus webhook subscription. requires confirmation. It contacts the configured Manus API v2 POST /v2/webhook.delete endpoint and requires a request-scoped x-manus-api-key. Deletes webhook subscription; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Publish Website — Use this Manus publish tool when you need to publish latest manus website checkpoint. requires explicit visibility and confirm. It contacts the configured Manus API v2 POST /v2/website.publish endpoint and requires a request-scoped x-manus-api-key. Deploys latest checkpoint; explicit visibility, dry-run, and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Send Task Message — Use this Manus spend tool when you need to send a follow-up or answer a manus messageaskuser waiting event. It contacts the configured Manus API v2 POST /v2/task.sendMessage endpoint and requires a request-scoped x-manus-api-key. Resumes/continues a task; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Stop Task — Use this Manus destructive tool when you need to stop a running manus task. the task can be resumed with send_task_message. It contacts the configured Manus API v2 POST /v2/task.stop endpoint and requires a request-scoped x-manus-api-key. Stops running task; resumable by send_task_message; confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Update Agent — Use this Manus write tool when you need to update a manus agent nickname/about fields. requires confirmation. It contacts the configured Manus API v2 POST /v2/agent.update endpoint and requires a request-scoped x-manus-api-key. Updates agent nickname/about; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Update Task — Use this Manus write tool when you need to update task metadata/share visibility. requires dry-run review and confirmation. It contacts the configured Manus API v2 POST /v2/task.update endpoint and requires a request-scoped x-manus-api-key. Metadata/share visibility write; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.
  • Update Website — Use this Manus write tool when you need to update manus website metadata/visibility without redeploying. requires confirm. It contacts the configured Manus API v2 POST /v2/website.update endpoint and requires a request-scoped x-manus-api-key. Updates website title/visibility; dry-run and confirm required. It is dry-run by default and requires confirm=true after approval before the provider write executes. The result is a compact, secret-redacted object and never includes the Portal grant or provider credential.