Meet Live Assist MCP Server

What the code does

We read the source, 1 d ago · rules ccca72095570

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

  execFile('say', ['-v', v, '-o', tmp, '--', clean], (err) => {

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    ws.proc = spawn(WHISPER_SERVER_BIN, ['-m', WHISPER_MODEL, '--port', String(WHISPER_SERVER_PORT), '-t', '4'],

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    return user === LOCAL_USER ? path.join(snapDir, session) : path.join(snapDir, safeUser(user), session);

    ws.proc = spawn(WHISPER_SERVER_BIN, ['-m', WHISPER_MODEL, '--port', String(WHISPER_SERVER_PORT), '-t', '4'],

    for (const f of fs.readdirSync(TRANSCRIPTS_DIR)) {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add meet-live-assist -- npx -y meet-live-assist-server

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

[mcp_servers.meet-live-assist]
command = "npx"
args = ["-y", "meet-live-assist-server"]

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

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

This one needs environment variables set before it will start: 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 <dir>/.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.). The author declared them in the registry entry; get the values from the project itself.