When cloud agents are kicked off from linear, the cloud agent reports that it does not have access to Linear with this message:
"Not right now. Linear is configured as an MCP server for me, but it currently shows a needsAuth status, meaning it requires authentication before I can use any of its tools.
Since I’m running as a cloud agent, I can’t complete the OAuth/login flow myself. To enable it, you’d need to authenticate the…"
I confirmed that linear is connected and I disconnected and reconnected and tried again, but still failing
Steps to Reproduce
Attach and image or doc in linear, assign task to cursor cloud agent. Cloud agent cannot fetch files from linear because it does not have access even though linear is conencted.
It’s a known issue on our side that we’re working on, and here’s how to get unblocked in the meantime.
There are actually two separate authorizations at play. The Linear integration (what lets you assign an issue to Cursor and kick off a cloud agent from Linear) is authenticated separately from the Linear MCP server (the tools your agent calls to read Linear data). Cloud agents also authorize their MCP servers independently from your desktop app. So reconnecting the Linear integration, or having Linear authorized in the IDE, doesn’t re-authorize the Linear MCP server the cloud agent uses, which is why it still comes up as needsAuth.
Two things that should help:
Re-authorize the Linear MCP server for cloud agents specifically. From your cloud agents area at cursor.com/agents, open the MCP/integrations settings and authorize Linear there (rather than just the Linear integration, or just in the IDE). One heads-up: because of the underlying issue, that authorization can sometimes drop again after a while. That repeating “connected but still needs auth” loop is exactly what we’re working to fix.
If your goal is to have the agent read an image attached to the Linear issue, that already works without the MCP. When a cloud agent is launched from a Linear issue, images attached to that issue are pulled into the agent’s context automatically. Only non-image files (PDFs, docs, and so on) rely on the MCP server, so those are the ones affected here.
If the re-authorization doesn’t hold, drop the agent’s link here (the cursor.com/agents/bc-… URL for the run) and I’ll dig into that specific run.