Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Root Cause Analysis
The CORS error occurs because the MCP SDK's auth() function in
/client/src/lib/mcp-oauth.ts:130-133 attempts to fetch OAuth metadata
directly from
https://mcp.asana.com/.well-known/oauth-authorization-server/sse from the
browser.
Problem: Browser security policies prevent direct cross-origin requests
to external OAuth metadata endpoints without proper CORS headers. The
Asana MCP server doesn't include CORS headers allowing requests from your
localhost origins.
Current server CORS config (/server/index.ts:14-17):
app.use('*', cors({
origin: ['http://localhost:8080', 'http://localhost:3000'],
credentials: true,
}))
This only configures CORS for your own server, not for proxying external
requests.
Proposed Fix
Add a server-side proxy endpoint to handle OAuth metadata discovery,
bypassing browser CORS restrictions:
server-side
requests
This approach:
have CORS)