Build a Notion roadmap rollup dashboard with Claude

This is an end-to-end example: connect a data source over MCP, generate a dashboard from live numbers, and close the review loop on one link. Total time, start to shared link, is under fifteen minutes. The same shape works for any of the other examples — only the connection step changes.

Here's the finished dashboard, published to a canvas — click any tile or status bar to leave a comment, exactly as your team would:

The three moving parts

1. The Notion MCP server gives Claude read access to your workspace — pages, databases, and the rows inside them — through a controlled set of tools. You authorize which workspace it can see.
2. Claude queries your roadmap and project databases and writes a single self-contained HTML dashboard. You iterate on it in the artifact panel until it's right.
3. Drafty turns that HTML into a stable link your team reviews. Comments pin to the exact element; Claude ships the fix to the same URL.

The generation step is fast now. The part this example is really about is the third one — getting the rollup in front of people without losing their feedback to a screenshot circled in Preview.

Step 1 — Connect the Notion MCP server

Notion runs an official remote MCP server at https://mcp.notion.com/mcp. You connect once; it authenticates over OAuth, so no key is pasted into a config file.

In Claude Code:

Then run /mcp inside Claude Code and follow the OAuth prompt to authorize the workspace. When you authorize, grant access to only the pages and databases this dashboard needs — Notion's OAuth consent screen lets you pick exactly what the connection can read.

In Claude Desktop: open Settings → Connectors → Add custom connector, paste https://mcp.notion.com/mcp, and authorize with OAuth the same way.

Step 2 — Pull the numbers

Ask Claude in plain language. It uses the MCP server's read tools (notion-search, notion-fetch, notion-query-data-sources) to find your databases and pull the rows:

Claude queries Notion, returns the figures, and you sanity-check them against the database views you already trust before going further. This is the moment to catch a wrong assumption — a stale status, an archived page still counted, a "Done" that means QA rather than shipped — while it's cheap.

Step 3 — Build the dashboard

Once the numbers look right, ask for the artifact:

Claude renders it live in the artifact panel. Iterate in place — you're not regenerating from scratch:

• "Sort the at-risk table by target date, soonest first."
• "Add a per-owner workload bar so we can see who's overloaded."
• "Make the 'shipped this quarter' count the hero number."

Step 4 — Publish to Drafty for review

A Claude artifact link is a preview, not a stable URL — iterate the artifact and the link you already sent now shows the old version. Ask Claude to publish it to a Drafty canvas instead, so the link you share always stays current:

Claude pushes the dashboard and hands back a drafty.im/canvas/… link that renders on any device. Send it — your team opens it in a browser, no login and no Claude account needed.

Step 5 — The review loop

This is the part that's not obvious until you've done it once.

A reviewer clicks the specific status bar, initiative, or owner row they want to discuss and leaves a pinned comment — "this 'At risk' count looks low, isn't the billing rewrite slipping too?" The comment is anchored to that element, not floating in a Slack thread. Claude reads the comments through the CLI, reruns the relevant Notion query if needed, and pushes a revised dashboard to the same URL. The reviewer refreshes and sees the change; the thread stays attached to the element.

The mechanic matters because of what it removes. A Slack message about a chart produces "the number on the left looks wrong." A pinned comment on the actual tile produces "this — count the billing rewrite as At risk, its target date already passed." One of those produces a correct revision; the other produces a guess.

Keeping it fresh

An MCP-generated dashboard is a snapshot — it holds the numbers Claude pulled when it built it; it doesn't re-query Notion when someone opens the link. For a weekly standup or a board-ready rollup, that's fine.

To make it a live canvas that always shows today's roadmap, copy this prompt — Claude sets up the refresh for you and schedules it to run on its own:

The link stays stable while the content updates underneath it — see keeping a canvas updated automatically.

What to watch for

• Read-only, always. A roadmap rollup needs read access and nothing more. Share only the databases it reports on, and don't grant write access for a reporting task.
• Check the figures before you share. The MCP returns exactly what you ask for — if your "Shipped" count includes pages still in review, or your status rollup double-counts a row that lives in two databases, the dashboard will confidently show the wrong number. Reconcile against the Notion view you trust once.
• The link is the deliverable, not the artifact. Share the Drafty URL, not the Claude artifact preview — that's the one you can update in place.