Hosted MCP server/Productivity Official

Official Asana MCP server

Hosted at mcp.asana.com·Streamable HTTP

Asana is a collaborative work management platform for planning, assigning, and tracking tasks across projects. Its official remote MCP server gives assistants account-backed project context over HTTP with OAuth, including task status, ownership, and workspace activity. The V2 server needs a pre-registered Asana MCP app: create it in the developer console, export ASANA_CLIENT_ID and ASANA_CLIENT_SECRET, and register the exact redirect URL for your client before connecting.

mcp.asana.com Streamable HTTP OAuth Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

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.

Install

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.

  1. Create an Asana MCP app

    In the Asana developer console create an app for MCP, then copy its client ID and client secret.

  2. 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).

  3. 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.

Connection

Endpoint and configuration

Endpoint
https://mcp.asana.com/v2/mcp
Host
mcp.asana.com · /v2/mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
asana
Listing type
Official provider listing

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.

Verification

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.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that asana appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List tasks assigned to me this week. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

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.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

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.
Safety

Before you connect

Remote means provider access
  • 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.
Review path

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.

Reference

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