@silkweave/meet

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

Features

• List upcoming meetings from Google Calendar and past Google Meet conference records
• Retrieve conference details, participants, recordings, and transcripts
• Render transcripts as clean Markdown (consecutive utterances per speaker merged)
• Three ways to consume new-transcript notifications:
  • eventPullTranscripts — MCP-native polling with a persisted cursor (idempotent)
  • Workspace Events subscriptions (eventSubscription*) — space-level or user-level → your Pub/Sub topic
  • Built-in background watcher (transcriptWatch*) — consumes Pub/Sub, writes Markdown files, runs a per-save shell command

Quick Start

1. Add the MCP Server

No installation required -- npx downloads and runs the package automatically.

Claude Code -- add to .mcp.json in your project root:

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

Other MCP clients -- use the command npx -y -p @silkweave/meet meet-mcp with stdio transport.

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

2. Create Google OAuth2 Credentials

In Google Cloud Console:

1. Create or pick a project.
2. Enable these APIs:
   • Google Calendar API
   • Google Meet API
   • Google Workspace Events API (only required if you plan to use eventSubscription*)
3. OAuth consent screen → add your email as a test user (while the app is in testing).
4. Credentials → Create Credentials → OAuth client ID → Web application.
5. Add http://localhost:3000/callback (or whatever redirectUri you'll pass) as an authorized redirect URI.
6. Download the Client ID and Client Secret.

3. Authenticate

Run the CLI (or call the MCP tool googleAuthorize):

npx -p @silkweave/meet meet-cli googleAuthorize --clientId=<id> --clientSecret=<secret>

Open the returned authorizeUrl, grant consent, and copy the code query parameter from the redirect. Then:

npx -p @silkweave/meet meet-cli googleGetToken <code>
npx -p @silkweave/meet meet-cli googleGetUser

Tokens are persisted to ~/.silkweave-meet.json. Refresh is automatic; re-authenticate only if the refresh token is revoked.

Required Scopes

Listed in src/lib/scopes.ts:

Usage

As a Library

pnpm add @silkweave/meet

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

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

As a CLI

npx -p @silkweave/meet meet-cli <actionName> [flags]

Tools Reference

Auth — Google*

Upcoming meetings — Calendar*

Past meetings & transcripts — Meet*

Notifications — Event*

Background watcher — TranscriptWatch*

Long-running consumer that pulls events from one or more Pub/Sub subscriptions, saves each transcript as a Markdown file under a configurable directory, and optionally runs a shell command after each save.

When autoStart: true is persisted, the MCP server resumes the watcher on every boot.

Each saved file is named YYYY-MM-DD_{meetCodeOrConferenceId}_{transcriptId}.md so files sort chronologically in the directory.

Operational — Mcp*

Notifications for new transcripts

Three complementary paths:

1. eventPullTranscripts — on-demand polling. The MCP stdio process cannot receive HTTP webhooks, so polling-with-a-cursor is the right primitive for ad-hoc queries. Idempotent: repeat calls return no duplicates.
2. transcriptWatch* (built-in watcher) — recommended for always-on setups. Create a Workspace Events subscription that publishes to a Pub/Sub topic (see below), create a Pub/Sub subscription on that topic, then call transcriptWatchStart with the subscription name. The watcher pulls messages continuously while the MCP server is running, saves Markdown to your configured directory, and can trigger a shell command per save.
3. eventSubscriptionCreate / eventSubscriptionCreateForUser → your own consumer — when you want events consumed by an external system instead of the MCP watcher, create the Workspace Events subscription and consume from Pub/Sub yourself.

End-to-end setup for the built-in watcher

# 1. Authorise (make sure pubsub scope is granted by re-running if upgrading).
npx -p @silkweave/meet meet-cli googleAuthorize --clientId=... --clientSecret=...
npx -p @silkweave/meet meet-cli googleGetToken <code>

# 2. Create a Pub/Sub topic in your GCP project and grant Meet permission to publish.
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

# 3. Create a Workspace Events subscription -- user-level captures all meetings.
npx -p @silkweave/meet meet-cli eventSubscriptionCreateForUser \
  --userEmail=you@example.com \
  --pubsubTopic=projects/<project>/topics/meet-transcripts

# 4. Create a Pub/Sub subscription to consume from (pull).
gcloud pubsub subscriptions create meet-transcripts-sub \
  --topic=meet-transcripts

# 5. Start the watcher.
npx -p @silkweave/meet meet-cli transcriptWatchStart \
  --pubsubSubscriptions=projects/<project>/subscriptions/meet-transcripts-sub \
  --transcriptDir=~/meet-transcripts \
  --onTranscriptCommand='osascript -e "display notification \"$MEET_CODE\" with title \"New transcript\""' \
  --autoStart=true

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).

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, call mcp__meet__mcpRestart after code changes to reload. Newly added tools require a full MCP reconnect (Claude Code caches the tool list at connection time).

License

MIT