Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Meet Live Assist

by krystiangwversion 0.7.3i★ 2iRuns on your computerRepository ↗
Registry nameio.github.krystiangw/meet-live-assist

How to install

What it does

Your own agent inside a live Google Meet or Zoom call. Local-first, no hosted service.

  • Connects Runs on your computer
  • Account or key Needs MLA_TOKEN
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity6/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness3/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score9/100

Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Meet Live Assist. Follow https://mcp.popnx.com/i/krystiangw-meet-live-assist.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Meet Live Assist for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "meet-live-assist": { "command": "npx", "args": [ "-y", "meet-live-assist-server" ], "env": { "MLA_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MLA_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Meet Live Assist tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Meet Live Assist key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "meet-live-assist": {
          "command": "npx",
          "args": [
            "-y",
            "meet-live-assist-server"
          ],
          "env": {
            "MLA_TOKEN": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Meet Live Assist and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Meet Live Assist or shows a Meet Live Assist tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MLA_URL Base URL of the bridge server on this machine. Defaults to http://127.0.0.1:8848, which is right unless you moved the port. · default http://127.0.0.1:8848
  • TRANSCRIPTS_DIR Where the bridge server writes. The adapter reads the access token from /.mla-token, and asks the running server for this path when it can, so it is normally unnecessary.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Meet Live Assist yet

Meet Live Assist runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Meet Live Assist

  • You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Meet Live Assist for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user meet-live-assist --env MLA_TOKEN=your-value -- npx -y meet-live-assist-server 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MLA_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Meet Live Assist tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Meet Live Assist key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user meet-live-assist --env MLA_TOKEN=your-value -- npx -y meet-live-assist-server

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Meet Live Assist listed as connected

  6. Try it

    Use Meet Live Assist and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Meet Live Assist or shows a Meet Live Assist tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MLA_URL Base URL of the bridge server on this machine. Defaults to http://127.0.0.1:8848, which is right unless you moved the port. · default http://127.0.0.1:8848
  • TRANSCRIPTS_DIR Where the bridge server writes. The adapter reads the access token from /.mla-token, and asks the running server for this path when it can, so it is normally unnecessary.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Meet Live Assist for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "meet-live-assist": { "command": "npx", "args": [ "-y", "meet-live-assist-server" ], "env": { "MLA_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MLA_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Meet Live Assist tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Meet Live Assist key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Meet Live Assist settings, MLA_TOKEN is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Meet Live Assist and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Meet Live Assist or shows a Meet Live Assist tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MLA_URL Base URL of the bridge server on this machine. Defaults to http://127.0.0.1:8848, which is right unless you moved the port. · default http://127.0.0.1:8848
  • TRANSCRIPTS_DIR Where the bridge server writes. The adapter reads the access token from /.mla-token, and asks the running server for this path when it can, so it is normally unnecessary.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Meet Live Assist key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Meet Live Assist for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "meet-live-assist": { "type": "stdio", "command": "npx", "args": [ "-y", "meet-live-assist-server" ], "env": { "MLA_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MLA_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Meet Live Assist tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Meet Live Assist key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Meet Live Assist settings, MLA_TOKEN is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Meet Live Assist and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Meet Live Assist or shows a Meet Live Assist tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MLA_URL Base URL of the bridge server on this machine. Defaults to http://127.0.0.1:8848, which is right unless you moved the port. · default http://127.0.0.1:8848
  • TRANSCRIPTS_DIR Where the bridge server writes. The adapter reads the access token from /.mla-token, and asks the running server for this path when it can, so it is normally unnecessary.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Meet Live Assist💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user meet-live-assist --env MLA_TOKEN=your-value -- npx -y meet-live-assist-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "meet-live-assist": {
      "command": "npx",
      "args": [
        "-y",
        "meet-live-assist-server"
      ],
      "env": {
        "MLA_TOKEN": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "meet-live-assist": {
      "command": "npx",
      "args": [
        "-y",
        "meet-live-assist-server"
      ],
      "env": {
        "MLA_TOKEN": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "meet-live-assist": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "meet-live-assist-server"
      ],
      "env": {
        "MLA_TOKEN": "your-value"
      }
    }
  }
}

Values you fill in

  • MLA_URL env
    Base URL of the bridge server on this machine. Defaults to http://127.0.0.1:8848, which is right unless you moved the port.
  • TRANSCRIPTS_DIR env
    Where the bridge server writes. The adapter reads the access token from /.mla-token, and asks the running server for this path when it can, so it is normally unnecessary.
  • MLA_TOKEN secret required env
    Access token for the bridge server. Only needed when the token file cannot be read; the adapter finds it by itself in the normal case.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
52/wk
Licencei
No licence stated
Connection
Runs on your computer
Latest versioni
0.7.3
Categoryi
Other
Published to registryi
Aug 12, 2026
Code last changedi
Aug 19, 2026
Maker
krystiangw
Packages
npm: meet-live-assist-server
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account krystiangw, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 months ago

  • ! Caution

    Has a licence

    GitHub could not identify the licence type; open the file to check

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for meet-live-assist-server@0.7.3

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/krystiangw-meet-live-assist.svg)](https://mcp.popnx.com/en/servers/krystiangw-meet-live-assist)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 91% of the other 20693 servers in this category
  • Published to the registry more recently than 17% of the other 20693 servers in this category
  • Basic checks equal to or better than 46% of the other 20693 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Meet Live Assist safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MLA_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 months ago, and the latest version (0.7.3) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Meet Live Assist
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks2/34/44/44/41/44/4
LicenseNOASSERTIONAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Meet Live Assist

Your own agent session, in the call with you. It reads the Meet or Zoom transcript as it happens and answers in a side panel while the call is still going: what was decided, who owns what, the risk you just agreed to, and the sentence to say next, in the meeting's language.

A release review, fourteen seconds, panel docked beside the call. The conversation is invented and the cameras are off, as they are on most working calls. The interface is the shipping one.

[Install from the Chrome Web Store](https://chromewebstore.google.com/detail/meet-live-assist/elhddnpchalnmgcgdicegfggifojbadk) · [the site](https://meet-live-assist.github.io/) · one command for the server: npx meet-live-assist-server

The store link is one click and updates itself; the repo works loaded unpacked and never does. Either way the server and the skill below are still yours to run, and without an agent attached the advice pane stays empty by design.

During a Google Meet or Zoom call this captures the transcript, shows it in a side panel, and hands it to an assistant running on your own computer. The assistant answers back in the panel while the call is still going: what to say, what was decided, who owns what, what you just agreed to that you should not have.

Transcripts, screenshots and chat are written to a folder on your disk and served by a server on 127.0.0.1 that only you can reach. There is no account, no telemetry, and no server of ours anywhere.

Where the words actually go, stated once and plainly. The brain is your own Claude Code session, so whatever you route to it - the transcript batches, your questions - leaves your machine for Anthropic under *your* account, exactly as any other Claude Code session does. What never leaves is the stored record: the files, the screenshots, the chat history. If a page tells you a live meeting assistant runs entirely on your machine, it is either using a local model or it is not telling you the truth; this one borrows a brain you already pay for, and that is the trade. See Data flow for the three-line version.

Read this before you install

You need an AI coding agent that speaks MCP - [Claude Code](https://claude.com/claude-code) is the one this is tested with. This ships the eyes, ears and hands - the capture, the panel, the local bridge - but not the brain. The brain is an agent session on your own machine, reading the call through MCP tools. Without one you get a working transcript recorder and an empty advice pane, which is not what the screenshots promise.

The adapter is plain JSON-RPC over stdio with nothing vendor-specific in it, so other MCP clients (Cursor, Cline, Continue, Zed, Codex) can drive it - Codex CLI was checked and completes tool calls against the bridge. One requirement is genuinely harder to meet elsewhere: the client has to hold a persistent background loop, because MCP is client-pull and nothing on the server can ever start a turn. MCP-CLIENTS.md explains what to check and what is unverified.

Your meeting is other people's conversation too. Turning on captions is invisible to everyone else, unlike recording, which Meet badges. So by default this posts one line into the meeting chat when capture starts, saying an assistant is transcribing locally. You can edit that line or turn it off in Options. Some jurisdictions require everyone's consent before a conversation may be recorded or transcribed; that is your call to make, and PRIVACY.md says so plainly.

Requirements: Node 20+, Chrome 116+, Claude Code. Speaking *into* the call is macOS-only (it uses say and afplay); elsewhere advice still appears in the panel and the server says why it cannot speak. Local speech-to-text works anywhere ffmpeg and whisper.cpp do, and the panel's setup row names which of the two is missing instead of failing quietly.

Install (three steps)

git clone https://github.com/krystiangw/meet-live-assist-extension.git

cd meet-live-assist-extension ./install.sh # installs the skill, registers the MCP tools, prepares the data dir

Then:

  1. Start the bridge server, leave it running: node server/transcript-server.js --pair
  2. Load the extension: chrome://extensions → Developer mode → *Load unpacked* → pick this folder. Pin it, click the icon. The panel collects its token from the pairing window on its own; there is nothing to copy. (Window expired? Run step 1's command again - it works against a running server too.)
  3. Open Claude Code and ask it to assist your meeting.

./install.sh takes MLA_USER, MLA_LANGUAGE, MLA_DOMAIN and MLA_TRANSCRIPTS_DIR so the assistant addresses you by name, in your language, and knows roughly what your meetings are about.

Pick a profile

MLA_PROFILE decides which meeting types the assistant knows about and what it leads with. Everything else - the markers, the modes, the board - is the same, because those turned out to be domain-neutral.

ProfileForIt leads with
engineering (default)standups, incidents, refinement, QAdecisions, scope creep, risk, action items
second-languageany meeting not in your first language🟢 SAY - the sentence, ready to speak, in the meeting's language
researchuser interviews, usability sessionssilence, leading-question warnings, guide coverage
genericanything elseresponding well in real time

They are plain files in skill/profiles/ - about a dozen lines each. Write your own and pass its name; the installer refuses a profile it cannot find; it never falls back to the default.

What it stores, and how to get rid of it

Everything lives in one folder - ./transcripts unless you set MLA_TRANSCRIPTS_DIR:

FileWhat it is
_ .txtthe transcript
<...>.chat.txt, <...>.summary.mdyour chat with the assistant, and the post-call summary
snapshots/ /*.jpgscreenshots taken during screen-share
.state/live meeting state, so restarting the server mid-call loses nothing
.mla-tokenthe shared secret the extension and the assistant authenticate with

Files are owner-only (0600), the directory is 0700, and anything older than 14 days is purged automatically (RETENTION_DAYS, 0 keeps everything forever). The 🗑 button in the panel wipes a single meeting - transcript, chat, summary, snapshots and state - immediately. To remove the whole thing: delete that folder, delete ~/.claude/skills/meet-live-assist, run claude mcp remove meet-live-assist, and remove the extension from Chrome.

Data flow

WhatWhere it goes
Transcript, screenshots, panel chat, summariesYour disk, nowhere else. Owner-only files, one folder, served by a process bound to 127.0.0.1.
The call content you route to the assistant, and your questionsAnthropic, via your own Claude Code session - same path as anything else you do in Claude Code, your account, your terms.
Anything elseNothing. There is no third party here.

On Free / Pro / Max, whether your sessions improve the model is a setting you control and it changes the retention period; Anthropic's consumer terms cover it and say explicitly that it includes Claude Code. Work and API accounts are on different terms. Worth knowing before you point this at a conversation that is not only yours.

What it does during a call

  • Live transcript - captions scraped, streamed to the panel instantly, de-duplicated + monologue forced-flush before hitting the file/brain, with a conservative ASR glossary.
  • Colour-coded advice from the brain (🟢SAY/🔵INFO/🟡SUMMARY/🟣EXPLAIN/🔴RISK/🟠ACTION), rich (links/images/diagrams/lists), each copyable; RISK fires an audible + notification cue.
  • Brain-liveness pill (is a Claude session actually attached?), capture watchdog (warns if captions break).
  • Decisions & action-items board with a one-click Draft (whatever you named in Options, or a plain note if you named nothing); recap quick-asks; two-way chat.
  • Autopilot - flip 🤖 Auto-create and it stops proposing and starts doing: the ticket or the note is created as the action item comes up, no per-item confirm. 📣 Post links to chat shares the link with the room. Both are off until you turn them on.
  • Snapshots (auto on screen-share + on demand), TTS into the call, local STT (whisper), meeting modes + type-awareness, live presentation edits + debug of the shared tab.
  • Talk-time, muted-mic + personal-mention alerts; post-call summary export.

Sprint planning with autopilot on. Nobody typed anything into the panel: the correction, the decision, the ticket and the note all arrive while the meeting carries on.

A note on trust. The assistant is your own Claude Code session with your own tools, and it reads a live, untrusted audio feed. It is instructed to let *only what you type* authorize an action - no spoken line, under any name, can make it act - but that is the model following its skill, not a wall. If you have connected destructive tools to Claude Code, set their trust accordingly. PRIVACY.md says this plainly too.

Landing page: docs/index.html, also hosted at https://meet-live-assist.github.io/.

Built by Krystian Gwizdała.

*Meet Live Assist is an independent project. It is not affiliated with, endorsed by or sponsored by Google or Zoom; "Google Meet" and "Zoom" are their owners' trademarks and are used here only to say which products this works with.*

Licence, in plain words

PolyForm Internal Use 1.0.0. Free, and yes, you may use it at work - "internal business operations of you and your company" is a permitted purpose, whether or not your company is for-profit. You may modify it for your own use.

What you may not do is redistribute it, fork it publicly, or sell it - as a product, a hosted service, or a part of either. This is source-available, not open source, and the difference is deliberate: it is free to use and stays owned.

If you want to do something the licence does not allow, ask. That is a conversation, not a refusal.

Architecture (why it's shaped this way)

  • Streaming + state live in the side panel, not the service worker. The SW is event-driven and gets torn down (~30s idle / 5-min cap); durable state is in chrome.storage.session, and the panel re-hydrates via a restore message on (re)connect.
  • Keep-alive: the side panel holds a runtime.connect port and pings it every 20s; a chrome.alarms heartbeat (30s) wakes the SW even after it was unloaded.
  • Server POST happens in the SW (has 127.0.0.1:8848 host permission), not the content script.

The bridge server

The extension talks to a small local Node server (127.0.0.1:8848) that is the "brain" bridge: transcript sink (/append), advice (/advice), board (/items), chat (/chat), snapshots (/snapshot, /snapshot-request), TTS (/speak, /voices), STT (/stt), meeting mode (/mode), presentat

Only the beginning is shown; read the rest in the repo