Asana MCP V1 shutdown on May 11, 2026: migrate to V2 or remove current Asana entry

[kgprs]

Problem

Asana has deprecated its V1 MCP server and says it will shut down on May 11, 2026. Their V2 server lives at https://mcp.asana.com/v2/mcp, no longer uses /sse, and no longer supports OAuth Dynamic Client Registration (DCR). V2 requires a pre-registered MCP app with a client_id and client_secret.

That creates a time-bound break for the gateway's current Asana support story. This repo still has Asana-specific examples/tests that assume a V1-style endpoint and the existing asana provider shape, for example:

• pkg/catalog_next/create_test.go uses provider: asana with https://asana.com/api/mcp/v1/sse
• pkg/workingset/server_test.go uses an Asana remote server snapshot with a V1-style SSE endpoint

Even if those are only tests/examples, they point at the old integration model. Once V1 is shut down, the current Asana entry/support path will either stop working or point users toward a broken setup.

Why this should be tracked separately from #474

Issue #474 is the general feature request for supporting pre-registered OAuth clients for remote servers that do not support DCR.

This issue is narrower and time-bound: we need an explicit product decision for the existing Asana integration before May 11, 2026.

Decision needed

We should decide one of these paths:

1. Support Asana V2 in the gateway/catalog by using a pre-registered OAuth client, likely built on top of the work proposed in Feature request: Support pre-registered OAuth2 clients (client_id + client_secret) for remote servers that don't support DCR (e.g. official Slack MCP server) #474.
2. If a Docker-managed shared Asana app is not viable, support user-supplied Asana client credentials for remote servers.
3. If neither path is acceptable before the deadline, remove or hide the current Asana entry so users are not offered a broken integration.

Things to validate

• Asana's docs say MCP apps can be distributed to either Specific workspaces or Any workspace. We should confirm whether a Docker-managed app configured for "Any workspace" is actually acceptable for the product and for customer admin controls.
• Asana V2 is workspace-scoped and uses a different transport and auth model than V1, so migration is more than just swapping the URL.

Acceptance criteria

• Decide the Asana support strategy before May 11, 2026.
• If we support Asana V2:
  • switch to https://mcp.asana.com/v2/mcp
  • stop depending on DCR for Asana
  • update catalog/docs/tests/examples away from the V1 /sse flow
  • account for V2 auth/behavior differences such as workspace-scoped authorization
• If we do not support Asana V2 in time:
  • remove, disable, or clearly mark the current Asana entry unsupported before the shutdown date
  • document the reason and any supported workaround

References

• Asana integration guide: https://developers.asana.com/docs/integrating-with-asanas-mcp-server
• Asana V2 announcement / deprecation timeline: https://forum.asana.com/t/new-v2-mcp-server-now-generally-available/1122647