You finish a call at 11. Granola has the notes. By 3 you’ve had two more calls, and the thing you promised in the first one has slid out of your head.
The notes were never the problem. Seeing them again at the right moment is.
What the board shows
Your latest meeting notes: the notes from your most recent meeting, on a widget on the board you keep open all day.
Recent meetings: a list of your calls with their title, date and who was in them, so the week has a shape.
What came out of them: your to-do list, right beside the notes. If your agent has Granola connected too, ask it to turn today’s action items into tasks and it adds them for you.
What’s next: your calendar’s upcoming events from Google Calendar’s secret iCal address. The last call and the next one, side by side.
Where the notes come from
Granola runs its own MCP server, the one AI apps sign in to when they read your notes. The board signs in to it through Granola’s own sign-in page. That sign-in is sealed on the board’s server and never sent back to your browser.
Then the board runs the reads you chose, on a schedule, while the board is open. Only reads. It never edits a note, a folder or a transcript, and Granola decides what its server shares with your plan.
You pick what to show in Connect. Choose one of Granola’s reads, try it, and the form shows what the widget will say before anything lands on the board. Or ask your agent in a sentence. “Put my latest meeting notes from Granola on the board” works from Claude, Codex, Cursor or any app that speaks MCP.
If a read fails, the widget keeps the last notes it got and says what went wrong and when.