A lot more languages with MCP

Let Codex or Claude follow the meeting while it happens.

Give your chosen AI client read-only access to finalized captions as the active Timeline changes, then translate the same conversation into multiple languages at once, maintain a live brief, or track decisions. Saved meetings, Meeting Analytics, and Voice Notes remain available when you enable them. Turn access off and it stops. MCP is included with NotchLive Pro.

A lot more languages with MCP Codex or Claude can follow finalized captions from the active Timeline and translate the same conversation into multiple requested languages at once. Read the complete walkthrough.
Saved access, plus optional live captions

Nothing is shared until you turn it on.

AI Connections is off by default. Enable saved meetings and notes first, then choose whether the active Timeline is also available. Connecting a client does not grant access while the main control is off.

  1. Search the record you already kept

    Let the client find reviewed meetings and transcripts, Meeting Analytics, and Voice Notes. Use it to retrieve a decision, compare meetings, or draft a follow-up from saved work.

  2. Optionally include the current conversation

    Once AI Connections is on, a second off-by-default control makes the Timeline currently visible in NotchLive available. Leaving it off limits access to saved content.

You stay in control

Ask NotchLive locally.

NotchLive does not push a meeting into an AI service or start a conversation on its own. The connection to NotchLive is local, but Codex or Claude may send requested content to its model provider according to that client's settings and policy.

  1. Turn on AI Connections

    Nothing is exposed before you enable the local server in NotchLive Settings.

  2. Choose whether to include live captions

    Saved meetings and notes become available with AI Connections. If you also need the active Timeline, turn on its separate caption control.

  3. Use NotchLive from Codex or Claude

    When a configured client requests NotchLive context, it can call only read-only tools. Turn access off and the configured client is refused.

NotchLive participant review workspace with speaker labels and meeting analytics
Review the speaker map before reuse Confirm participant names and corrections before analytics, exports, saved output, or MCP use the meeting record.

The model can separate voices. You decide who people are.

NotchLive treats automatic speaker attribution as evidence, not identity. Rename, merge, reassign, split, or leave speech unresolved. Your reviewed participant map, rather than an automatic acoustic guess, is the meeting structure used by analytics, exports, saved output, and MCP results.

See how speaker diarization works
Read-only by design

Useful meeting context without remote control.

The server exposes narrow retrieval tools, not control over NotchLive or your Mac.

Search the reviewed record

List and search saved meetings, then read one meeting with participant labels, analytics, and an optional reviewed transcript.

Retrieve Voice Notes

List saved Voice Notes and read the note you ask for without granting access to unrelated files.

Read enabled Timeline context

Retrieve the active Timeline only when its separate setting is on. No setting means no live-meeting result.

Never exposed No write, delete, rename, recording, microphone, network, or model tools. MCP cannot start captions, change a participant, or alter a transcript.

Connect the desktop app, not a command line.

Open NotchLive Settings, go to AI Connections, and use Set Up… for Codex or Claude Desktop. NotchLive writes the local connection for the installed desktop client, so a separate CLI install is not required.

Turn on “Allow AI apps to access NotchLive” to share saved meetings and notes. If needed, separately turn on “Include active meeting captions.” Setup alone does not grant access while the main switch is off.

NotchLive MCP FAQ

Does NotchLive send meetings to Codex or Claude automatically?

No. AI Connections starts off, NotchLive never initiates a request, and configured clients are refused until you enable access. Once enabled, the AI app may send requested content to its model provider.

What happens if MCP is configured but the setting is off?

The client still has its local configuration, but NotchLive refuses the connection and returns no meeting data until you enable AI Connections again.

Can MCP change or delete NotchLive data?

No. The NotchLive MCP server is read-only and exposes no write, delete, rename, recording, microphone, network, or model tools.

Does enabling saved meetings also expose my current meeting?

No. Active Timeline access has its own separate, off-by-default control.

Can Codex or Claude translate live NotchLive captions into more languages?

Yes. When active Timeline access is enabled, Codex or Claude can request each finalized caption and translate the same stream into multiple requested languages. This AI-client workflow is separate from the 20 languages built into NotchLive through Apple Translation.

Do I need the Codex or Claude command-line tool?

No. NotchLive can configure the installed Codex or Claude Desktop app directly from Settings.

Keep the meeting local. Bring it into more languages when you choose.

Use NotchLive for live captions, then explicitly connect Codex or Claude when you want parallel translations, a live brief, or reviewed meeting context.