talat ships an MCP (Model Context Protocol) server so that AI tools running on your machine can work with your meeting data. The server runs locally and talks to the AI tool over stdio. talat sends nothing anywhere itself; what an assistant reads goes wherever that assistant sends it. Claude Code, Codex and Claude Desktop send it to their makers’ servers, while LM Studio and Bionic run a model on your computer.
To ask talat’s own assistant about a meeting, see Assistant.
What the server can do
A connected assistant can both read and change your meetings, all against the same local database the app uses, so its edits show up live in talat:
- Read. List and open meetings, search across every transcript, and read a meeting’s transcript, summary, and action points, including the one currently recording.
- Write. Update a summary or title, add and remove tags, edit chapters, and create or update action points.
- Import. Hand it a local audio or video file and it transcribes it offline through talat, the same as any other import.
Connecting an assistant
Settings → MCP lists the assistants talat knows about: Claude Code, Codex, Claude Desktop, LM Studio and Bionic. Each one found on your computer has a Connect button that adds talat to its settings, and a Disconnect button that takes it out again. talat changes only its own entry; your other settings keep their values.
- Claude Code gets talat in every folder. Connecting replaces any setup you made for a single folder.
- Claude Desktop reads its settings only at launch, so quit it fully and reopen it after connecting. It shows as Not on this computer until it has been opened at least once, because that first launch creates the settings folder talat looks for.
- Points at another copy of talat means the entry runs a different talat: one that has moved or been removed, or another edition. Reconnect points it at this one.
- Set up by an older version of talat means the entry works but uses the name every copy of talat used to share. Reconnect gives it this copy’s own name.
- Set up for some folders only means Claude Code has talat only in the folders where it was added. Reconnect makes it available in every folder.
If you’d rather set it up yourself, these do the same for Claude Code and Codex, using the name and path shown under Other MCP clients. The name is talat for the standard app and differs for other editions, such as Setapp:
claude mcp add --scope user <name> -- <path>codex mcp add <name> -- <path>
If Claude Desktop still shows Not on this computer after it has been opened, talat could not find its settings folder. Create the folder %APPDATA%\Claude on Windows, or ~/Library/Application Support/Claude on a Mac, and open Settings → MCP again: talat finds the folder, and Claude Desktop reads a settings file there when it has no copy of its own.
To add the snippet from the settings page by hand instead, the file is in one of these places on Windows, and the first that exists is the one Claude Desktop reads:
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json
On a Mac there is one place:
~/Library/Application Support/Claude/claude_desktop_config.json
Don’t use the Edit Config button in Claude Desktop’s own settings for this: on Windows it opens the second file even when Claude Desktop reads the first.
Other MCP clients
Any MCP client that speaks stdio can connect to talat. Copy the snippet under Other MCP clients on the settings page into its MCP configuration and it will be able to query your meeting data the same way.