Locus MCP
Your meetings.
In your AI app.
MCP, the Model Context Protocol, is the open standard AI apps use to reach tools and data in other apps. Locus runs a local MCP server on your Mac, so Claude, Claude Code, Codex or Cursor can search and read your meeting notes and transcripts. Read-only, off until you turn it on, one connection per app.
Jump to steps ↓
Your meetings, read by the app you choose.
Locus speaks MCP on your Mac: three read-only tools, search, list and read, over a local connection that the AI app starts. No cloud server, no upload. The app gets the text it asks for, nothing more.
What an app can read
Your meeting notes and transcripts, now and in the future, with their titles, dates and people.
What it cannot read
Your audio, the notes you type during a recording, and meetings in the Trash. MCP cannot change or write anything in Locus.
Where the text goes
The AI app sends what it reads to its own AI service, under that company’s terms. Locus does not run a server for this. The app talks to Locus on this Mac, so Locus must be open.
Turn on MCP.
One switch for every connection. Locus asks you to read what you share before it turns on.
- Open Locus on your Mac. Go to Settings → MCP.
- The page says Off · no AI app can read your meetings. Open What can connected apps read? to see what you share.
- Turn on the Turn on MCP switch.
- Read Share your meetings with AI apps?, then choose Turn on MCP. The page now says On · add a connection to use MCP in an AI app.
Share your meetings with AI apps?
Connected apps can read your current and future meeting notes and transcripts. Every connection has the same read-only access.
Audio and the notes you type during a recording are not shared.
Source-based interface illustration · the dialog shown on the first turn-on
The switch is greyed out.
Read the line under the switch. Locus’s background service is not running means Base is not running: keep Locus open and give it a moment. Locus is still starting clears by itself. MCP settings could not be read needs Reset MCP, which turns MCP off and removes every connection.
Add a connection for each app.
Each app gets its own name and its own key, so you can pause or disconnect it alone.
Add connection
Locus makes a key for this app. Each app gets its own, so you can pause or disconnect it alone.
Source-based interface illustration · choose the app, keep or change the name
- Choose Add connection.
- Under Which app?, choose Claude, Claude Code, Codex, Cursor or Other app. Keep the suggested name or type your own, then choose Create.
- Locus shows “Your app” is ready to connect, with the steps for that app and the text to copy. Choose Copy command or Copy. For Cursor, you can choose Add to Cursor instead.
- Follow the steps in your AI app, then choose Done. The connection shows Waiting for first use.
The steps for each app.
Claude: open Settings → Developer, choose Edit Config, add the “locus” entry inside “mcpServers”, save the file, then quit Claude and open it again.
Claude Code and Codex: paste the command in Terminal and press Return. Start a new session and ask about your meetings.
Cursor: choose Add to Cursor and confirm in Cursor, or add the block to Cursor’s MCP settings file.
Other app: add the server to the app’s MCP settings. The app must be able to start a program on this Mac (a “stdio” server). Apps that only reach servers on the internet, such as ChatGPT, cannot connect.
Ask, and let the app read.
Your AI app searches, lists and reads your meetings through Locus. You read its answer with the note beside you.
- In your AI app, start a new session. Ask about a meeting, for example: What did we decide about the opening checklist?
- The app searches your meetings, reads the ones it needs and answers. Locus asks it to cite meeting titles and dates.
- Back in Settings → MCP, the connection’s line changes from Waiting for first use to Used just now, later Used 5 minutes ago.
- Check an important detail against the meeting note before you act on it.
Used just now · Claude Code · reported as claude-code
Waiting for first use · Cursor
All connections share the same read-only access to your meetings.
Source-based interface illustration · one row per connected app
The app says it cannot reach Locus.
Read the app’s message. Locus is not open on this Mac: open Locus and keep it open; Base must be running. MCP is turned off in Locus or This connection is paused: turn it on in Settings → MCP. This connection was removed: add a new connection and update the app’s settings. After a Locus update, quit the AI app and open it again.
Pause or disconnect at any time.
Turning a connection or MCP off stops the next read. Text an app already received stays with that app.
Pause one app
Turn off the switch on its row. The line reads Paused. Turn it on again when you want.
Pause every app
Turn off Turn on MCP. The page says Off, and every row reads Paused by MCP. Your connections stay, ready for later.
Disconnect
Choose Disconnect on the row, then Disconnect again. The app can no longer read your meetings. To use it again, add a new connection.