@silkweave/meet

Google Meet API client exposed as both an MCP server and a CLI. Built with silkweave.

Authentication is exclusively through a Google Workspace service account with domain-wide delegation (DWD). There is no OAuth flow, no per-user token registry, no interactive login. One service-account JSON on disk and a list of Workspace user emails in a config file is the entire setup.

Features

• List upcoming meetings from Google Calendar and past Google Meet conference records
• Retrieve conference details, participants, recordings, and transcripts (impersonating any Workspace user via DWD)
• Render transcripts as clean Markdown (consecutive utterances per speaker merged)
• Persistent transcript archive with full-text (and optional OpenAI-powered vector/hybrid) search — every saved transcript is enriched with its Calendar event (subject, description, attendees) and indexed into a local Orama database
• Two ways to consume new-transcript notifications:
  • eventPullTranscripts — on-demand polling with a persisted cursor (idempotent)
  • Built-in background watcher (transcriptWatch*) — streams from Pub/Sub and writes Markdown files, with optional per-save shell command
• transcriptBackfill — one-shot catch-up across all users for the past N days

Quick Start

1. Provision a service account with DWD

In Google Cloud Console:

1. Create or pick a project.
2. Enable the Google Calendar API, Google Meet API, Google Workspace Events API, and Cloud Pub/Sub API.
3. Create a service account; download its JSON key.

In your Google Workspace Admin Console:

1. Security → Access and data control → API controls → Domain-wide delegation → Add new.
2. Paste the service account's Client ID (the numeric one in the JSON key, field client_id).
3. Grant these OAuth scopes:
   • https://www.googleapis.com/auth/userinfo.email
   • https://www.googleapis.com/auth/calendar
   • https://www.googleapis.com/auth/drive.readonly
   • https://www.googleapis.com/auth/meetings.space.readonly
   • https://www.googleapis.com/auth/meetings.space.created

2. Install the key locally

mkdir -p ~/.silkweave-meet
cp /path/to/sa-key.json ~/.silkweave-meet/service-account.json
chmod 600 ~/.silkweave-meet/service-account.json

That's all the auth configuration. No env vars, no OAuth flow.

3. Register the MCP server (optional, for Claude Code)

{
  "mcpServers": {
    "meet": {
      "command": "npx",
      "args": ["-y", "-p", "@silkweave/meet", "meet-mcp"]
    }
  }
}

The package ships two bins: meet-mcp (stdio MCP server) and meet-cli (same action set as direct commands).

4. Try a call

npx -p @silkweave/meet meet-cli calendar-event-list --user-email=you@your-workspace.com

Configuration file

Everything non-secret lives in ~/.silkweave-meet/config.json:

{
  "users": ["alice@company.com", "bob@company.com"],
  "watcher": {
    "pubsubSubscriptions": ["projects/my-project/subscriptions/meet-transcripts-sub"],
    "transcriptDir": "/Users/alice/meet-transcripts",
    "onTranscriptCommand": "osascript -e 'display notification ...'",
    "autoStart": true
  },
  "cursors": {
    "alice@company.com": "2026-04-22T14:30:00Z"
  },
  "openai": {
    "apiKey": "sk-...",
    "embeddingModel": "text-embedding-3-small"
  }
}

• users — Workspace user emails the tool is allowed to impersonate. Populated by setupSubscribeAll --users=a,b,c or edited manually.
• watcher — persisted watcher config, written by transcriptWatchStart.
• cursors — per-user polling cursors for eventPullTranscripts.
• openai — optional. Enables vector/hybrid search over the persisted transcript archive. OPENAI_API_KEY and OPENAI_EMBEDDING_MODEL env vars are used as fallbacks.

Archive files & database

• Ingested transcripts are written to <transcriptDir>/<organizerEmail>/YYYY-MM-DD_{meetCodeOrConferenceId}_{transcriptId}.md. Because each saved file is fetched via the organizer's own subscription, the top-level folder makes it easy to browse "meetings I ran".
• A companion Orama index at ~/.silkweave-meet/transcripts.msp holds the searchable metadata (subject, description, attendees, date range, file path, embedding). It is the source of truth for transcriptList / transcriptGet / transcriptSearch.

Tools Reference

Every action that reads Google data takes a required userEmail — the Workspace user the service account impersonates for that call. Permissions match exactly what that user can see.

The MCP surface is intentionally narrow: only the read-only transcript tools plus transcriptBackfill and mcpStatus are exposed over MCP. Everything that manages configuration, subscriptions, or the background watcher is CLI-only (via meet-cli).

MCP-exposed tools:

• meetTranscriptList / meetTranscriptGet — live lookup against the Google Meet API.
• transcriptList / transcriptGet / transcriptSearch — read from the persisted local archive (no Google round-trip; works offline for previously-ingested transcripts).
• transcriptBackfill — catch-up ingest across all configured users (default: last 30 days). Dedupes by transcriptId.
• mcpStatus — health & status.

Upcoming meetings — Calendar* (CLI-only)

Past meetings & transcripts — Meet* (live Google API)

meetTranscriptList and meetTranscriptGet are available on both MCP and CLI. The rest are CLI-only.

Persisted transcript archive — Transcript* (local Orama DB)

Reads from ~/.silkweave-meet/transcripts.msp; populated by the background watcher (live) and transcriptBackfill (historical). Every record is enriched with its Calendar event (subject, description, attendees) — matching is deterministic via conferenceData.conferenceId → Meet space meetingCode, never time-guessing.

Notifications — Event* (CLI-only)

Background watcher — TranscriptWatch* (CLI-only)

Singleton consumer that streams events from a Pub/Sub subscription (Pub/Sub auth from the same service-account key), and for each message impersonates (via DWD) the user whose Workspace Events subscription produced it — identified by the message's ce-source attribute — to fetch the transcript via the Meet API. One watcher covers every user listed in the config.

When autoStart: true is persisted, the MCP server resumes the watcher on every boot. Each saved file is written to <transcriptDir>/<organizerEmail>/YYYY-MM-DD_{meetCodeOrConferenceId}_{transcriptId}.md and simultaneously inserted into the local search index.

Multi-user setup — Setup* (CLI-only)

These are registered only in src/cli.ts (not the MCP action list), because they orchestrate the whole config rather than a single user.

Operational — Mcp*

Multi-user setup walkthrough

# 1. Create the shared Pub/Sub topic and let Meet publish to it.
gcloud pubsub topics create meet-transcripts
gcloud pubsub topics add-iam-policy-binding meet-transcripts \
  --member=serviceAccount:meet-api-event-push@system.gserviceaccount.com \
  --role=roles/pubsub.publisher

# 2. Register the users and create one user-level subscription per person
#    (idempotent). The --users flag appends to ~/.silkweave-meet/config.json.
npx -p @silkweave/meet meet-cli setup-subscribe-all \
  --pubsub-topic=projects/<project>/topics/meet-transcripts \
  --users=alice@company.com,bob@company.com,carol@company.com,dave@company.com

# 3. Confirm every user is subscribed.
npx -p @silkweave/meet meet-cli setup-status \
  --pubsub-topic=projects/<project>/topics/meet-transcripts

# 4. Create the pull subscription the watcher will stream from, and grant the
#    service account Subscriber on it.
gcloud pubsub subscriptions create meet-transcripts-sub --topic=meet-transcripts
SA_EMAIL=$(jq -r .client_email ~/.silkweave-meet/service-account.json)
gcloud pubsub subscriptions add-iam-policy-binding meet-transcripts-sub \
  --member="serviceAccount:${SA_EMAIL}" --role=roles/pubsub.subscriber

# 5. Start the watcher. Routes each incoming event to the right user's
#    impersonation context based on the message's ce-source.
npx -p @silkweave/meet meet-cli transcript-watch-start \
  --pubsub-subscriptions=projects/<project>/subscriptions/meet-transcripts-sub \
  --transcript-dir=~/meet-transcripts \
  --auto-start=true

User-level subscriptions expire (Google's max TTL applies). Re-run setup-subscribe-all on a schedule (cron / launchd) to refresh any that have expired; existing valid ones are skipped.

User-level subscriptions capture transcript.v2.fileGenerated events for meetings the user owns or is merely invited to — that is the only non-owner event the Workspace Events API delivers, and it's exactly the one we want. Expect duplicates when multiple team members are in the same meeting; the watcher dedupes by transcriptId in memory per run.

Shell command env vars

The onTranscriptCommand runs via spawn(..., { shell: true }) with these environment variables exposed:

For very long transcripts, prefer reading from $TRANSCRIPT_PATH — environment size is bounded (~256KB on macOS).

Library usage

pnpm add @silkweave/meet

import { MeetClient } from '@silkweave/meet'
import { google } from 'googleapis'

const conferences = await MeetClient.withAuth('alice@company.com', async (auth) => {
  const { data } = await google.meet({ version: 'v2', auth }).conferenceRecords.list()
  return data.conferenceRecords ?? []
})

MeetClient.withAuth creates a DWD-impersonating JWT for that user using the key at ~/.silkweave-meet/service-account.json.

Development

pnpm install
pnpm tsx src/mcp.ts     # MCP server in dev
pnpm tsx src/cli.ts     # CLI in dev
pnpm build              # build to build/
pnpm lint               # eslint
pnpm typecheck          # tsc --noEmit
pnpm clean              # rm -rf build/

When iterating through the MCP in Claude Code, the server is a child process — after code changes, restart the MCP connection (or kill the process) so changes are picked up. Claude Code caches the tool list at connection time, so any change to the MCP action set also requires a full reconnect.

License

MIT