Asana

The Asana connector allows AI agents to manage tasks, track project progress, and collaborate on work items — all through the Asana REST API using OAuth 2.0. Your credentials are stored encrypted in MCPGate's vault and are never exposed to the AI client.

Tool reference#

The Asana connector exposes 8 tools: 4 read and 4 write.

Tool	Category	Description
asana_list_projects	read	List projects in a workspace
asana_list_tasks	read	List tasks in a project
asana_get_task	read	Get task details
asana_search_tasks	read	Search tasks across a workspace
asana_create_task	write	Create a new task
asana_update_task	write	Update task (status, assignee, due date)
asana_add_comment	write	Add a comment to a task
asana_complete_task	write	Mark a task as complete

Common guardrail recipes#

Read-only access#

Enable only the four read tools and deny all write tools. Useful for reporting agents that monitor task completion rates or summarise project status without modifying anything.

Restrict to specific projects#

Apply the allow_values template to asana_create_task and target the project_id field. Provide a list of allowed project IDs. The AI will be denied if it attempts to create tasks in other projects.

Allow task completion only#

Enable only asana_complete_task and asana_add_comment from write tools, while denying asana_create_task and asana_update_task. This lets an AI assistant close out tasks and leave notes without creating new work items.

Troubleshooting#

Workspace ID required for search — asana_search_tasks operates across a workspace. If the AI does not provide a workspace ID, the call may fail. Use asana_list_projects first to retrieve the workspace ID.
Task already complete — Calling asana_complete_task on an already-completed task is a no-op. Check task state with asana_get_task before attempting to complete it.
Assignee not found — Asana assignees must be members of the workspace. Passing an email address that is not a workspace member will result in an error fromasana_create_task or asana_update_task.