@roychri/mcp-server-asana

What it does

This MCP server bridges Claude and other MCP clients to the Asana API. It exposes eight tools for reading and writing workspace data: list workspaces, search projects with regex patterns, search tasks with advanced filters (assignee, status, custom fields, blockers), retrieve full task details and histories, create tasks, update task metadata, and retrieve project information. You can ask Claude natural-language questions about your backlog, have it generate tasks, or pull task summaries directly into your conversation.

Who it's for

Teams using Asana who want Claude integrated into their workflow for quick lookups, bulk task generation, and workload analysis without context-switching to the web interface. Useful for project leads, engineering managers, or individual contributors who need Claude to help reason about project state or draft task updates.

Common use cases

• Query all unfinished tasks in a sprint or project and have Claude summarize workload and identify blockers.
• Create multiple tasks at once by describing them in natural language, with Claude setting projects, assignees, and due dates.
• Search across projects to find all tasks blocked by a dependency or tasks waiting on specific team members.
• Retrieve task histories and comments to have Claude generate status summaries or highlight progress.
• Have Claude suggest task reassignments or highlight overloaded team members based on current assignments.

Setup pitfalls

• Requires ASANA_ACCESS_TOKEN environment variable set before the server starts; without it the server will not function.
• The token grants full API access to your workspace—store it securely and never commit it to version control.
• To restrict operations to read-only, set READ_ONLY_MODE=true to disable create, update, and delete tools.
• Token permissions must include scopes for your intended operations; missing scopes may cause silent failures.