Hello Friends!
Hoping somebody can help me out with the below:
Issue Summary: I am experiencing a persistent failure when trying to connect the Asana MCP Server to Cursor. The primary error involves a conflict with the local npm environment, where npx repeatedly triggers an “Access token expired or revoked” notice and a “404 Not Found” error for the @modelcontextprotocol/server-asana package. Despite the package being public, my system seems locked into a loop of attempting to use stale, non-existent credentials, preventing the server from initializing.
Troubleshooting Attempted:
-
Protocol Swaps: Switched between
stdio(local command) andSSE(remote URL) connection types. -
Environmental Cleans: Deleted local
~/.npmrcfiles, cleared npm caches, and attemptednpm logoutto bypass ghost credentials. -
Bypass Methods: Attempted to install/run the server using direct GitHub paths,
pip(Python), anduvx(to bypass npm entirely). -
Network Checks: Restarted hardware and cleared browser caches to rule out IP-based rate limiting (429 errors).
Ideal Outcome: I am looking for a stable way to authenticate and run the Asana MCP server within Cursor that does not rely on a local npm registry check. The goal is to achieve a consistent “Green” connection status that allows Cursor to list and execute Asana tasks directly via the API.
I am not a technical person by nature, so please be kind and explain in layman’s terms, thank you!