Meeting Intelligence

Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with supplemental research.

Quick start

Confirm meeting goal, attendees, date/time, and decisions needed.
Gather context: search with Notion:search, then fetch with Notion:fetch (prior notes, specs, OKRs, decisions).
Pick the right template via reference/template-selection-guide.md (status, decision, planning, retro, 1:1, brainstorming).
Draft agenda/pre-read in Notion with Notion:notion-create-pages, embedding source links and owner/timeboxes.
Enrich with supplemental research (industry insights, benchmarks, risks) and update the page with Notion:notion-update-page as plans change.

Notion tool availability can vary by workspace. If a Notion MCP call returns Tool <name> not found, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use Notion:search and Notion:fetch where sufficient.
Use one literal search query per Notion:search call and include filters: {} when no narrower filter is needed.
Only fetch Notion page, database, or data-source URLs/IDs; external connected-source search results are not valid Notion:fetch inputs.
Create meeting pages with an explicit parent and a pages array.
Query databases with Notion:notion-query-data-sources under a top-level data object, using fetched collection://... URLs as table names.
When editing a page, fetch its current content first and use Notion:notion-update-page with supported commands such as update_content or update_properties; on the current deployed surface, use properties: {} for update_content and content_updates: [] for update_properties. Do not invent insertion-only commands.