Manus MCP integration for AI agents.
Connect AI agents to Manus through 17 structured actions, including get agent, create project, delete task, and confirm task action. Review authentication, i…
- ACTION CONTRACTS
- 17
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Manus integration exposes
The Manus Agent App exposes 17 provider-backed actions for ai and productivity work. Its current contract lets an authorized agent retrieve a manus custom agent by id, create a manus project for grouping tasks under shared instructions, and permanently delete a stopped manus task. stop a running task before deleting it. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Manus account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Manus capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_agentREADRetrieve a Manus custom agent by ID.
INPUTS: agent_id
create_projectWRITECreate a Manus project for grouping tasks under shared instructions.
INPUTS: name / instruction
delete_taskHIGH IMPACTPermanently delete a stopped Manus task. Stop a running task before deleting it.
INPUTS: task_id
confirm_task_actionREVIEWConfirm a pending Manus task action from a waiting status event. Use send_message instead for messageAskUser events.
INPUTS: task_id / event_id / input
create_taskWRITECreate a new asynchronous Manus task from a message and optional project, connector, skill, sharing, or structured-output settings.
INPUTS: content / connectors / enable_skills / force_skills / message
get_taskREADRetrieve a Manus task's current status and metadata.
INPUTS: task_id
list_agentsREADList Manus custom agents in the current account.
list_connectorsREADList Manus connectors installed in the current account.
list_online_browser_clientsREADList online Manus browser clients that can be selected when confirming browser connection events.
list_projectsREADList Manus projects available to the current account.
list_skillsREADList Manus skills available to the current account or project.
INPUTS: project_id
list_task_messagesREADList Manus task event messages with cursor pagination.
INPUTS: task_id / limit / cursor / order / verbose
INPUT CONTRACTS
Know what the action needs before it runs.
get_agent
agent_idOPTIONAL- The agent ID to retrieve.
create_project
nameREQUIRED- Display name for the project.
instructionOPTIONAL- Default instruction applied to tasks in this project.
delete_task
task_idOPTIONAL- The task ID to delete.
confirm_task_action
task_idREQUIRED- The task ID with a pending action.
event_idREQUIRED- The waiting_for_event_id value from the status update event.
inputOPTIONAL- Optional input for the pending action, matching the event confirm_input_schema.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Agent
Retrieve a Manus custom agent by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_agentControl Create Project
Create a Manus project for grouping tasks under shared instructions. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_projectVerify with Get Task
Retrieve a Manus task's current status and metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_taskSAFETY BOUNDARY
Operate Manus with explicit limits
- Authorize Manus with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_task` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Manus rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Manus task completed successfully.
CONNECTION MODEL
API key
Manus API key sent with the x-manus-api-key header. Create and copy a key from Manus API Integration settings: https://manus.im/app?show_settings=integrations&app_name=api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Manus.