Please note that you must select at least 1 Asana Product tag in the section about. Without it, you will not be able to move forward. Not sure what to select? Pick “agentic-work-management”.
Tip: When posting a question in the Asana Forum, try to include:
Has anyone tried this?
Hi Tooba,
Going by Asana’s help docs, these are the native ways to build dashboards in Asana, assuming each migrated board came over as an Asana project:
A dashboard for one project: open the project, click the Dashboard tab, then + Add widget.
One dashboard across all 5 projects: open Reporting from the sidebar and add a new dashboard. When you add a custom chart that reports on tasks, you can choose to include tasks from specific projects, so you can pick your 5. Universal reporting is listed for Starter, Advanced, Enterprise and Enterprise+ (plus legacy Premium, Business and Legacy Enterprise).
On Advanced or above (or legacy Business / Legacy Enterprise), you can also add the 5 projects to a portfolio and use the portfolio’s Dashboard tab. Portfolio dashboards are prefiltered to that portfolio’s data, and you can click + Add chart there. Charts that report on project metadata (“Report on Projects”) are also listed for Advanced and above.
If you can share the exact error text and which Asana plan you’re on, that would help narrow it down.
Disclosure: I’m on the Duaer team; this was drafted with AI help and checked against Asana’s docs.
Hi @Tooba_Ahmed
Short answer: the connection works, but Claude can’t build an Asana dashboard through the MCP connector. So nothing is wrong with your setup.
The Asana API, and the MCP server that sits on top of it, has no endpoint for dashboards, charts or widgets. Claude can read your tasks and edit them, but it has no tool that creates a chart. Asana’s API team says this is deliberate: they expose the data and leave the visualising to you. So when you ask for a dashboard, Claude runs into a wall and you see errors.
I rebuilt your case today: 5 boards “migrated from monday” with monday’s status labels, 52 tasks. Two things worked.
1. Claude builds the dashboard itself, outside Asana
Claude reads the 5 projects through the connector and draws the report as an artifact. Prompt you can use:
Read all tasks from these 5 Asana projects: [names]. Include completed tasks, due dates and the Status and Owner fields. Build a one-page dashboard: totals, a status mix per project, open vs overdue work per owner, and a table of tasks that are Stuck or more than 7 days late.
Screenshot above is a snapshot rather than a live view, so you re-run the prompt when you want fresh numbers. In exchange you get things native charts don’t do, like that “stuck or a week late” list.
2. Claude builds the real Asana dashboard by driving the browser in the pane inside Claude.
If you want a native, live dashboard, give Claude a browser instead of the API. The Claude desktop app (Code tab) has a built-in browser that keeps your Asana login. I asked Claude to open Reporting, create a dashboard and add three charts for the 5 projects: tasks by status, open tasks per project, overdue tasks per owner. It did, and the numbers matched the API exactly. Screenshot below shows the chat on the left and Asana on the right.
It’s slower than you’d expect, because Claude clicks through Asana’s menus one by one. You also need a plan that includes reporting dashboards.
Two smaller things that might be a problem if you go the API route:
What does the error actually say, and are you using claude.ai or the desktop app? That decides which of the two fits.
Hi @Tooba_Ahmed
Putting in my two cents in here ! I came across this with the concept of wanting historical data from our dashboards, and given dashboards are dynamic, the manual workaround is to export a csv file on a regular basis, merge the data sets, clean and then analyze.
One extension worth sharing: I built a Python ETL script that reads Asana task data via the API on a schedule and pushes a computed digest to Slack. The key difference from a straight dashboard pull is the metrics layer — rather than raw status counts, it computes weighted workload scores, customized to your team’s needs , ex. (effort estimate × priority per assignee), tracks those metrics week-over-week for trend analysis, and surfaces things like workload concentration across the team. Native Asana dashboards and the artifact approach both give you a snapshot of task state; the ETL layer gives you derived signals that don’t exist in the raw data. Happy to share more on the setup if useful!
