Documentation menu
DocsIntegrations
Use your notes from Claude Code and Codex
Humla's MCP server lets Claude Code, Codex or any other MCP client search and read your meeting notes, from wherever you work.
On this page
Humla includes a Model Context Protocol server. Once you connect it, the agent you already work in can look things up in your meetings. Ask Claude Code "what did we agree with Acme about the renewal?" and it searches your notes for the answer, instead of asking you to paste them in.
Before you start
You need:
- Humla, installed in your Applications folder. The server comes with the app, so there is nothing else to install.
- An MCP client: Claude Code, Codex, or anything else that can start an MCP server over stdio.
Turn it on in Humla
The server is off until you turn it on, so an update never opens your meetings to anything on its own.
- Open Humla and go to Settings → General.
- Under Integrations, turn on Model Context Protocol server.
Humla then shows the exact command for Claude Code and the configuration for Codex, with the path to the server on your Mac filled in. Copy from there. The examples below use the usual path, /Applications/Humla.app/Contents/MacOS/humla-mcp.
Connect Claude Code
Run this once in a terminal:
claude mcp add --scope user humla -- "/Applications/Humla.app/Contents/MacOS/humla-mcp"
--scope user makes Humla available in every project, not just the folder you ran the command in. Start a new Claude Code session, then run /mcp inside it: humla should be listed as connected. claude mcp list in a terminal shows the same.
Connect Codex
Add this to ~/.codex/config.toml:
[mcp_servers.humla]
command = "/Applications/Humla.app/Contents/MacOS/humla-mcp"
Start a new Codex session so it reads the file. /mcp inside Codex, or codex mcp list in a terminal, should list humla.
Other MCP clients
Any client that starts MCP servers over stdio can run the same command directly, with no arguments. There is no port, no URL and no token: the server is a small program that reads Humla's database on your Mac, and the file permissions on your Mac are what keep other people out.
Check that it works
Ask your agent something only your meetings can answer, for example:
What did we decide in our last meeting about the launch?
A working answer names the meetings it found and quotes or summarises what was said. If the agent says Humla's integration is turned off, go back to Settings and turn it on: the change applies to the next question, no restart needed.
What the agent can do
The server has six tools, and all of them only read:
| Tool | What it does |
|---|---|
search_notes | Searches your typed notes, the AI summaries and the transcripts, and says which of the three each match came from. |
list_notes | Lists your notes, newest first, with date, client, who spoke and a one-line summary. |
get_note | Reads one note, or up to ten at once: your notes and the summary. |
get_transcript | Reads one note's transcript, with speaker names, when the exact words matter. |
list_folders | Lists your folders, so the agent can narrow a search to one. |
list_clients | Lists your clients, so the agent can narrow a search to one. |
Searches and lists can be narrowed by folder, client, who spoke, language and dates, either relative (the last 30 days) or fixed (June 2026).
What it can't do:
- Change anything. Nothing an agent does through the server can edit or delete a note.
- Reach your recordings. No tool returns or points to audio.
- Cross workspaces. It reads the workspace you have open in Humla, Personal or a team workspace. Switch workspace in Humla to change what the agent sees; the agent can't ask its way into another one.
It works whether Humla is open or not.
Search matches words, not meaning
The server searches by keyword. That keeps it free, offline and without an API key, but it has one consequence worth knowing: a search in the wrong language finds nothing. If your meetings are in Norwegian and the agent searches in English, it gets no results rather than worse ones.
Agents usually work this out on their own. Every result says which language its note is in, and a search that comes back empty lists the languages your notes are actually in, so the agent can try again. If an answer seems to be missing, tell the agent which language the meeting was held in.
Turn it off
Turn off Model Context Protocol server in Settings → General. It takes effect on the agent's next question. The server then answers that the integration is turned off, and reads nothing until you turn it on again. To remove it from your client as well, run claude mcp remove humla, or delete the [mcp_servers.humla] section from ~/.codex/config.toml.