Where it fits
Project managers and coordinators who want an assistant to report on and work with their Asana tasks.
- List tasks assigned to me this week
- Summarize project status before a standup
- Draft a weekly update from completed tasks
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Asana
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Keeps multi-step agent work on a file-based plan, holding task_plan.md, findings.md, and progress.md on disk while lifecycle hooks feed relevant planning context into the session. Recovery by itself only consults those project planning files. When explicitly asked, session-catchup.py with --metadata reads local agent session records from the same project and reports aggregate counts; --replay can add bounded excerpts wrapped in nonces. A gated mode may request continuation on hosts that support it, never executes commands written in Markdown, and nothing is uploaded over the network.
Syncs tasks and refreshes memory from current activity. Covers pulling new assignments from a project tracker into TASKS.md, triaging stale or overdue items, filling gaps about unfamiliar people or projects, and scanning chat and email broadly for buried todos.
Runs the month-end close, sequencing tasks, tracking dependencies, and keeping status current. It fits planning the close calendar, following progress, spotting blockers, and ordering close work day by day.
No skills found
Try a different search term or clear the filters.
Claude Code with a pre-registered Asana app
Asana's V2 server needs a pre-registered OAuth app. Create it in the Asana developer console, export ASANA_CLIENT_ID and ASANA_CLIENT_SECRET, and register the exact redirect URL for your client.
- Create an Asana MCP app
In the Asana developer console create an app for MCP, then copy its client ID and client secret.
- Register the redirect URL
Register the exact callback for your client: localhost:8080/callback (Claude Code), cursor://anysphere.cursor-mcp/oauth/callback (Cursor), 127.0.0.1:33418/ (VS Code) or localhost:3334/oauth/callback (other local clients).
- Run the pre-registered command
Export ASANA_CLIENT_ID and ASANA_CLIENT_SECRET, then run the command with --client-id, --client-secret and --callback-port 8080. Authorize when the browser opens; authorization is required.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name asana. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
asanaappears and that the tools match the provider documentation. - 2Run one small request.
Start with: List tasks assigned to me this week. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Asana documentationhttps://developers.asana.com/docs/connecting-mcp-clients-to-asanas-v2-server