Asana

Search and manage tasks, projects, portfolios, users, teams, attachments, comments, status updates, and AI Teammates through Asana’s official MCP server.

See Asana’s MCP server guide, integration guide, and tool reference for current setup requirements and capabilities.

What you’ll need to connect

Ask your Obot administrator to create an MCP app in the Asana developer console and:

1. Add Obot’s OAuth callback URL exactly as shown by Obot.
2. Configure the app under Manage distribution for either the specific workspaces that may use it or Any workspace.
3. Configure the app’s client ID and client secret for this catalog entry in Obot. Asana V2 does not support dynamic client registration.
4. Ensure the app is allowed by your Asana workspace’s app-management policy.

When you connect, Asana asks you to select and authorize one workspace. Tool calls use your Asana identity and cannot access data beyond your existing permissions. Access tokens expire after one hour; Obot uses the refresh token to maintain the connection.

Important differences

V2 uses Streamable HTTP at https://mcp.asana.com/v2/mcp. Its OAuth tokens are workspace-scoped and valid only for the MCP server, not Asana’s REST API. MCP apps do not request individual OAuth scopes; an authorization can use all MCP tools made available by Asana, subject to the user’s existing permissions.

V2 preserves the main task, project, user, team, portfolio, attachment, comment, and project-status workflows. It does not provide direct replacements for V1’s goal creation and update tools, time-period tools, workspace enumeration, task follower helpers, or standalone dependency and parent helpers. Bulk task updates cover many follower, dependency, parent, and project-membership changes.

⚠️ Upgrade notice

If you’re upgrading this server, note that this replaces Asana’s deprecated V1 beta server with the generally available Asana V2 MCP server.

• Reconnect required: An Obot administrator must configure a statically registered Asana MCP OAuth client. Existing V1 connections and tokens cannot be reused.
• Workspace selection: Each connection is authorized for one workspace. Connect the server separately to work with additional workspaces.
• Tool changes: Tool names and parameters change. Dedicated goal mutation, time-period lookup, workspace listing, and several granular task helper tools are no longer available; some task operations are consolidated into bulk create and update tools.
• New capabilities: V2 adds bulk task operations, status overviews, comments, and AI Teammate discovery.