Mnemocompany memory

New · Meeting Memory

Walk into every meeting already caught up.

Meeting Memory reads the calendar you already connected, recognises the attendees as people in your memory, and writes a short brief before you go in: what you know about them, what you last discussed, and what is still open — every line pointing at the memory it came from.

REST API: GET /v1/meetings/upcoming?days=&limit=&cursor=&containerTag= (scope meetings:read) returns upcoming Google Calendar events with attendees matched to People by email, plus the connections array — empty with connections: [] when nothing is linked, never a 404. GET /v1/meetings/{documentId}/brief (meetings:read + answer:read) returns the cited brief, matched people with open reminders and recent memories, and previous meetings sharing an attendee.

Connect, match, brief

  • Connect Google Calendar — the existing google_calendar connector syncs your primary calendar into a container hourly; Meeting Memory reads those documents and 'Sync now' is one button when you need it fresher.
  • Recognise the room — each attendee email is looked up against your People (exact, lowercased). Cancelled events are dropped; all-day events keep their day semantics.
  • Read the brief — one question over the meeting's container plus every matched person's container, cached for 15 minutes; a slow reader nulls the answer, never the drawer.

Reads the calendar you already trusted it with

  • No new Google scope — the connector already had read access; Meeting Memory stores attendees, organiser, location, and the event link that it was already fetching.
  • Matched by email, never by vibes — no fuzzy name matching.
  • Cited or abstained — the brief answers only from the meeting's and the attendees' containers.
  • API keys stay in their lane — a key reads one connection's container; MCP grants cannot reach meetings.
  • Old events still work — documents synced before this release fall back to parsing the invite text (attendeeSource: contentText) until a sync refreshes them.
  • Behind a flag — 503 FEATURE_DISABLED until Meeting Memory (and connectors) are enabled for your workspace.

Explore Mnemo