How do I set up the Asana MCP in Cursor?

How To
1

The server docs are here: Using Asana’s Model Control Protocol (MCP) Server

I have tried this:

"asana": {
  "type": "sse",
  "url": "https://mcp.asana.com/sse"
}
2

I get the below error, do I need to edit any other Cursor settings? My mcp.json is

{
“mcpServers”: {
“asana”: {
“type”: “sse”,
“url”: “https://mcp.asana.com/sse”
}
}
}

Error in Cursor Console:

2025-05-02 08:43:49.610 [info] sana: Handling ReloadClient action

2025-05-02 08:43:49.610 [info] sana: getOrCreateClient for sse server. process.platform: darwin isElectron: true

2025-05-02 08:43:49.610 [info] sana: Creating SSE transport

2025-05-02 08:43:49.756 [error] sana: Client error for command SSE error: Non-200 status code (401)

2025-05-02 08:43:49.756 [error] sana: Error in MCP: SSE error: Non-200 status code (401)

2025-05-02 08:43:49.756 [error] sana: Failed to reload client: SSE error: Non-200 status code (401)

2025-05-02 08:43:49.757 [info] sana: Handling ListOfferings action

2025-05-02 08:43:49.757 [error] sana: No server info found

3

Hey, we don’t currently have support for OAuth authentication directly, but you can use the community project mcp-remote to pre-authorize with that, then just forward the traffic to Cursor!

4

We (the greater cursor/agentic_users’ community)

are going to need a library of super succinct shorts on auth and op/sec as we spawn billions of mcp_lettes over the next months.

So - @cursor really has a duty to ensure that all cursor users know how to implement auth/sec in their MCPs ASAP.

Or there needs to be an intrinsic auth/security MCP that is just called and maintained by cursor else litigations will follow at somepoint. And you cant just throw it to the user “RTFMCP!!”

5 
    "asana": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.asana.com/sse"]
    }

This works