Asana MCP Server

Asana

Asana is a project management platform for organizing team work. This bundle provides access to workspaces, projects, tasks, goals, resource allocations, and user profiles.

Entity Hierarchy

• Workspace is the top-level organizational boundary. Users can belong to multiple workspaces.
• Teams are groups within a workspace that own projects.
• Projects are collections of tasks, organized as lists or boards. A project belongs to a team.
• Sections divide a project into logical groups (e.g., "To Do", "In Progress", "Done").
• Tasks are individual work items with assignees, due dates, descriptions, attachments, and subtasks.
• Goals are high-level objectives tracked across projects and teams.
• Allocations represent resource capacity planning for team members.

Capabilities

Read operations:

• List workspaces the authenticated user belongs to
• Get user profile information
• List and search projects within a workspace
• List tasks within a project or assigned to a user
• Get task details including custom fields, attachments, and subtasks
• List goals and their progress metrics
• View resource allocations for team members

Write operations:

• Create, update, and complete tasks
• Assign tasks to team members
• Set due dates and priorities
• Add comments and attachments to tasks
• Create and update projects
• Move tasks between sections

Workflows

Review workload: List workspaces to find your organization, then list projects to see active work. Drill into a project to view tasks by section. Check allocations to assess team capacity.

Task management: Search or list tasks assigned to a user. Update task status, assignee, or due date. Add comments for status updates. Create subtasks to break down complex work.

Track goals: List organizational goals to see strategic objectives. Check progress metrics and linked projects. Identify blockers by reviewing tasks associated with behind-schedule goals.

Plan resources: View allocations across team members for a time period. Identify over-allocated team members and redistribute work by reassigning tasks.

Gotchas

• Workspace GID required: Most operations need a workspace GID. List workspaces first to get it.
• Task GIDs: Tasks are identified by GID, not name. Search or list to get the GID before updating.
• Custom fields: Projects may have custom fields that appear in task details. These are workspace-specific.
• Pagination: Large task lists are paginated. Use the offset/cursor returned to fetch subsequent pages.
• Opt-in fields: Some fields (like custom_fields, memberships) must be explicitly requested via opt_fields to be included in responses.