Asana MCP integration for AI agents.
Connect AI agents to Asana through 101 structured actions, including get attachment, add project custom field, delete attachment, and duplicate project. Revi…
- ACTION CONTRACTS
- 101
- AUTHENTICATION
- OAuth 2.0 + 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 Asana integration exposes
The Asana Agent App exposes 101 provider-backed actions for productivity work. Its current contract lets an authorized agent get an asana attachment by gid, add a custom field setting to an asana project, and delete an asana attachment. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and 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 Asana account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Asana capabilities.
Showing 12 of 101 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_attachmentREADGet an Asana attachment by gid.
INPUTS: attachmentId / includeFields
add_project_custom_fieldWRITEAdd a custom field setting to an Asana project.
INPUTS: projectId / customFieldId / isImportant / insertBefore / insertAfter
delete_attachmentHIGH IMPACTDelete an Asana attachment.
INPUTS: attachmentId
duplicate_projectREVIEWStart an asynchronous job to duplicate an Asana project.
INPUTS: projectId / name / include / scheduleDates / includeFields
add_project_followersWRITEAdd users as followers of an Asana project.
INPUTS: projectId / followers / includeFields
add_project_membersWRITEAdd users as members of an Asana project.
INPUTS: projectId / members / includeFields
add_section_taskWRITEMove a task into a section, optionally at a specific position.
INPUTS: sectionId / taskId / insertBefore / insertAfter
add_task_dependenciesWRITEAdd dependencies to an Asana task.
INPUTS: taskId / dependencyIds
add_task_dependentsWRITEAdd dependent tasks to an Asana task.
INPUTS: taskId / dependentIds
add_task_followersWRITEAdd followers to an Asana task.
INPUTS: taskId / followerIds / includeFields
add_task_projectWRITEAdd an Asana task to a project with optional section placement.
INPUTS: taskId / projectId / sectionId / insertBefore / insertAfter
add_task_tagWRITEAdd a tag to an Asana task.
INPUTS: taskId / tagId
INPUT CONTRACTS
Know what the action needs before it runs.
get_attachment
attachmentIdREQUIRED- The attachment gid.
includeFieldsOPTIONAL- Additional Asana fields to request via opt_fields.
add_project_custom_field
projectIdREQUIRED- The Asana project gid.
customFieldIdREQUIRED- The custom field gid to add.
isImportantOPTIONAL- Whether the custom field is important in this project.
insertBeforeOPTIONAL- The existing custom field setting before which to insert the resource.
insertAfterOPTIONAL- The existing custom field setting after which to insert the resource.
delete_attachment
attachmentIdREQUIRED- The attachment gid.
duplicate_project
projectIdREQUIRED- The source project gid.
nameREQUIRED- The name of the duplicated project.
includeOPTIONAL- Optional project elements to copy.
scheduleDatesOPTIONAL- Options for shifting copied task dates.
includeFieldsOPTIONAL- Additional Asana fields to request via opt_fields.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Attachment
Get an Asana attachment by gid. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_attachmentControl Add Project Custom Field
Add a custom field setting to an Asana project. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_project_custom_fieldVerify with Add Project Custom Field
Add a custom field setting to an Asana project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_project_custom_fieldSAFETY BOUNDARY
Operate Asana with explicit limits
- Authorize Asana with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 53 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_attachment`, `delete_custom_field`, and `delete_project` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `projects:write`, `tasks:write`, `attachments:write`, and `custom_fields:write`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Asana task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Asana personal access token used with the Authorization Bearer header. Get it from the Asana developer console at https://app.asana.com/0/my-apps.
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
- 44
- WRITE SIGNALS
- 36
- HIGH IMPACT
- 17
- REVIEW SIGNALS
- 4
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 Asana.