Create managed Asana roadmap projects, publish Pulse and Fundamentals status updates, and use Cooperly context when external MCP context is supported inside Asana.
Why teams connect Asana
Asana is where teams manage projects, tasks, goals, portfolios, and status updates. Cooperly helps those workflows reflect the real team context behind ownership, risk, pressure, and follow-up.
The integration supports Asana sync from Cooperly today, with MCP-ready context available when Asana supports external MCP context inside the product.
What the integration does
Cooperly can create and update managed Asana roadmap projects, sections, and tasks from the Cooperly roadmap, using the mapped Asana Team for each Cooperly team.
Cooperly can also publish Pulse and Fundamentals summaries as Asana project status updates. Cooperly has MCP support, so teams can use external Cooperly context inside Asana when Asana supports that path.
- Choose one Asana workspace and one Asana Team per mapped Cooperly team.
- Enable roadmap sync, status updates, and evidence only for teams where those outputs should appear.
Why it matters
Asana work becomes less generic when plans and status updates can reference the team context Cooperly already holds, while Asana remains the project system that owns the actual work.
Configure
- 01
Enable Asana in Cooperly
Turn on Asana for the account so workspace access, team mappings, roadmap sync, and status updates can be configured.
- 02
Connect an Asana workspace
Complete Asana OAuth, choose the workspace when more than one is available, and refresh metadata so Cooperly can read active Asana Teams.
- 03
Map Cooperly teams to Asana Teams
Choose one Asana Team per Cooperly team, then decide whether roadmap sync, Pulse status updates, Fundamentals status updates, and evidence in task descriptions are enabled.
- 04
Review MCP context support
Cooperly has MCP support. Once external MCP context is supported inside Asana, Cooperly context can be used there.