0
Fork 0
mirror of https://github.com/mastra-ai/mastra.git synced 2026-11-17 08:44:46 +00:00
mastra/templates/template-meeting-notes
Damien Schneider dce50dc9a1
chore: unify built-in Gateway naming (#18691)
## Summary

Rename Mastra’s first-party built-in gateway from **“Memory Gateway”**
to **“Gateway”** across live product surfaces, docs, templates, and
Mastra Code.

This is primarily a naming change. Gateway still handles model routing,
while Observational Memory remains a separate capability available
through the hosted service.

## What changed

- **Core:** `MastraGateway.name` and its provider-catalog display name
now use **Gateway**.
- **Playground:** the remote-memory panel uses **Gateway** as the
product name and **Remote** as the status label.
- **Mastra Code:** setup messages, internal symbol names, tests, and
filenames use the current Gateway terminology.
- **Docs and templates:** current product prose uses **Gateway**
consistently.
- **Tests and changesets:** assertions and release notes match the final
naming.

## Compatibility

The rename preserves existing identifiers and contracts:

- `MastraGateway`, gateway id `mastra`, the `mastra/` model prefix, and
`MASTRA_GATEWAY_*` environment variables are unchanged.
- The `X-Memory-Gateway-Authorization` header remains unchanged because
it is a wire contract.
- Persisted `settings.memoryGateway` remains unchanged to avoid a
settings migration.
- Auth-storage keys and default URL string values are unchanged.
- `MEMORY_GATEWAY_PROVIDER` and `MEMORY_GATEWAY_DEFAULT_URL` remain
exported as deprecated aliases of the new `MASTRA_GATEWAY_*` constants.
- `MastraCodeGateway.getMemoryGatewayApiKey()` remains a deprecated
alias and is covered for both normal and detached static calls.
- `/gateway` is the current hidden setup command; legacy
`/memory-gateway` remains accepted as an alias.

This lets current code adopt the Gateway name without breaking existing
consumers, stored configuration, commands, or network integrations.

## Deliberately out of scope

This PR does not change Gateway memory behavior or infer new
capabilities from its display name. It also does not include unrelated
CI hardening or review fixes.

The following accidental branch changes were restored exactly to `main`:

- client-js observability/memory E2E reset and seeding changes
- MongoDB vector metadata validation and its changeset
- generated Temporal fixture formatting drift

## Changesets

- `@mastra/core` — patch: display-name rename
- `mastracode` — patch: setup naming and `/gateway` alias
- `@mastra/code-sdk` — minor: new canonical exports/accessor with
deprecated compatibility aliases

## Validation

Synced normally with `main` through `2d5c85612f`; no force-push was
used.

- `@mastra/core`: dependency graph build passed; 3 focused files / 38
tests passed; typecheck passed.
- `@mastra/code-sdk`: 4 focused files / 83 tests passed; compatibility
accessor regression test passed; typecheck passed.
- `mastracode`: 2 focused files / 31 tests passed; `/gateway` and
legacy-command routing test passed; exact MCP HTTP and hooks-reload E2E
scenarios passed locally; typecheck passed.
- `@mastra/playground-ui`: typecheck passed.
- Scoped ESLint, Prettier, and `git diff --check` passed.
- Fresh GitHub CI ran on head `1e8e307c6c`: 70 successful, 3 skipped, 1
neutral, 0 failed, and 0 pending checks.
- `Mastra Code E2E` passed on retry. The remaining cancelled MongoDB
store job is a pre-existing circular-metadata/Vitest shutdown hang
reproduced on unrelated PRs with the identical MongoDB tree; this PR has
no MongoDB diff. The fix belongs in a separate MongoDB PR.
History 2026-07-13 17:26:20 +02:00
..
src/mastra feat(templates): New templates showcasing latest Mastra features (#17425) 2026-06-16 12:26:14 -04:00
.env.example chore: unify built-in Gateway naming (#18691) 2026-07-13 17:26:20 +02:00
.gitignore feat(templates): New templates showcasing latest Mastra features (#17425) 2026-06-16 12:26:14 -04:00
package.json chore: unify built-in Gateway naming (#18691) 2026-07-13 17:26:20 +02:00
README.md chore: unify built-in Gateway naming (#18691) 2026-07-13 17:26:20 +02:00
tsconfig.json feat(templates): New templates showcasing latest Mastra features (#17425) 2026-06-16 12:26:14 -04:00

Meeting Notes (with Zoom)

Turns a Zoom cloud recording into structured meeting notes — attendees, decisions, action items, topics — and optionally ships them to Notion or Linear via MCP.

  • Zoom Server-to-Server OAuth — one-time setup, no per-user OAuth dance.
  • ingest-meeting workflow — pulls the Zoom-generated VTT transcript, summarizes it with gpt-5.4 via Mastra's Gateway, returns structured JSON.
  • Optional exports to Notion and Linear via MCP, gated on env vars.
  • POST /meetings/upload — API route for non-Zoom sources (Google Meet, Riverside, Loom, plain text).

Demo

This demo runs in Mastra Studio. Open the meetingNotesAgent and ask it to summarize a transcript, or run the ingest-meeting workflow with a Zoom meeting id.

Prerequisites

  • A Gateway API key.
  • A Turso database URL + auth token.
  • A Zoom Server-to-Server OAuth app. See setup below.
  • (Optional) A Linear API key to create issues from action items.
  • (Optional) A Notion integration token to push notes via the Notion MCP server.

Quickstart 🚀

  1. Set up a Zoom Server-to-Server OAuth app
    • At https://marketplace.zoom.us → "Develop" → "Build App" → choose "Server-to-Server OAuth".
    • Add these scopes:
      • cloud_recording:read:list_user_recordings:admin
      • cloud_recording:read:recording:admin
      • user:read:user:admin
    • Activate the app and copy the Account ID, Client ID, and Client Secret into .env.
  2. Add your API keys
    • Copy .env.example to .env and fill it in.
  3. Start the dev server

Then try:

  • In Studio, run the ingest-meeting workflow with a Zoom meetingId.
  • Or chat with the meetingNotesAgent: "List my recent Zoom recordings", then "Summarize the one from Tuesday".

Zoom transcripts

This template uses Zoom's built-in transcript (generated by Zoom AI Companion). Make sure the cloud-recording setting "Audio transcript" is enabled for the user whose meetings you're ingesting. If a meeting has no Zoom transcript, fetchZoomTranscript will throw — wire in your own STT service (e.g. Whisper, Deepgram, AssemblyAI) as a fallback.

Manual upload endpoint

POST /meetings/upload
Content-Type: application/json

{
  "title": "Q3 planning sync",
  "transcript": "Alice: Let's start with..."
}

Returns the structured notes JSON. Useful for Google Meet / Riverside / Loom / plain text sources.

Making it yours

  • Add Whisper fallback. Drop a transcribeAudio tool that downloads the recording's audio file and runs it through Whisper, so meetings without Zoom AI still work.
  • Tighten the output schema. Edit meetingNotesOutputSchema to capture the fields your team actually uses (e.g. risks, blockers, follow-up meetings).
  • Auto-create Linear issues. Add a workflow step that loops over actionItems and uses the Linear MCP tools to create issues for each one.
  • Trigger on Zoom webhooks. Add an API route at /zoom/webhook that listens for the recording.completed event and kicks off the ingest-meeting workflow automatically.

Agent Editor

This template enables the code-backed Agent Editor with new MastraEditor({ source: 'code', codePath: 'mastra/editor' }). Edits made in Studio are written as deterministic JSON overrides under mastra/editor/agents/, so Mastra Platform can open GitHub pull requests for agent changes instead of only saving them to the database.

About Mastra templates

Mastra templates are ready-to-use projects that show what you can build. Use the platform-created repository as your starting point, then customize it for your app.

Want to contribute? See the Mastra contributing guide.