Meet-live-assist MCP Server

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

Local serverstdio

What is the Meet-live-assist MCP Server?

Meet-live-assist is an MCP integration. Your own agent inside a live Google Meet or Zoom call. Local-first, no hosted service.

Packages and local setup

The published npm package is meet-live-assist-server, version 0.7.3. Its declared MCP transport is stdio.

The package declares 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.; 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.; MLA_TOKEN: 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..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.7.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
MLA_URLBase URL of the bridge server on this machine. Defaults to http://127.0.0.1:8848, which is right unless you moved the port.Optional
TRANSCRIPTS_DIRWhere 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.Optional
MLA_TOKENAccess token for the bridge server. Only needed when the token file cannot be read; the adapter finds it by itself in the normal case.Optional