Day 27 — AI Engineering
The meeting ended 5 minutes ago. Everyone already forgot what was decided.
An MCP server that turns meeting chaos into clarity — searchable notes, tracked action items with owners and deadlines, a decision log you can actually find things in, and follow-up reports that write themselves.
Example Queries
Tools
| Tool | What It Does |
|---|---|
| search_meetings | Search past meetings by keyword, type, date range, or participant — returns summaries, attendees, and action item counts. |
| meeting_summary | Full summary of a specific meeting — attendees, notes, decisions, and action items in one view. |
| action_items | List and filter action items across all meetings — by status, owner, priority, or due date. Find overdue items instantly. |
| decision_log | Browse decisions across all meetings — search by keyword, filter by impact level, and see context and rationale. |
| owner_workload | See action item workload by person — open items, overdue counts, completion rates, and who is overloaded. |
| follow_ups | Generate a follow-up report — overdue items, upcoming deadlines, in-progress work, and recent key decisions. |
The System
Every meeting generates notes, decisions, and action items. This server connects them so nothing falls through the cracks:
Meeting notes stored with speaker attribution, timestamps, and topics. Summaries link to the full discussion so context is never lost.
Action items pulled from each meeting with owner, priority, and due date. Decisions recorded with context and impact level.
Every action item has an owner and a deadline. Filter by status, priority, or person. Overdue items surface automatically.
Generate weekly follow-up reports — overdue items, upcoming deadlines, workload distribution, and key decisions that need attention.
Why This Build
The average professional spends 31 hours per month in meetings. And the number one complaint isn't that there are too many meetings — it's that nothing happens after them. Decisions get forgotten. Action items live in someone's head. Follow-ups don't happen.
The problem isn't note-taking — it's that notes sit in a doc nobody reads again. What teams actually need is a system that connects what was decided to who owns what and when it's due. One question: “What's overdue from last week?” and you have your standup agenda.
This tool turns meetings into accountability. Search any past meeting, track every action item, and generate follow-ups that actually get things done. Fourth AI Engineering build of the challenge.
Demo Data
15
Meetings
12
Participants
38
Action Items
15
Decisions
22
Meeting Notes
8
Meeting Types
15 realistic meetings across 8 types — sprint planning, retros, architecture reviews, postmortems, 1:1s, standups, cross-functional syncs, and all-hands. 12 team members across Engineering, Product, Design, Marketing, QA, and Sales. 38 action items with owners, priorities, due dates, and status tracking. 15 key decisions with context and impact levels.
Setup
cd day27-meeting-notes
npm install && npm run seed && npm run buildThen add the config to Claude Desktop and restart.
If your team's decisions keep getting lost between meetings, let's build a system that makes accountability automatic.