Connect Codex in your IDE to Earkeep

The server is always on while Earkeep is running, and it listens on 127.0.0.1 and nothing else. That loopback binding is the security model: there is no address at which anything off your device could reach it.

It offers two tools, and both are read-only. Nothing connected here can create, edit or delete a meeting.

• search_spans finds saved meetings by a case-insensitive match on their title or notes, or lists all of them when you don't give it a query. Newest first, twenty at a time.
• read_span takes one meeting's id and returns that meeting plus the transcript lines it covers.

Worth knowing before you write a prompt: search matches titles and notes, not the words inside transcripts.

The extension reads the same config.toml the command line uses. Open it from the gear icon, then Codex Settings, then config.toml, and add:

Reload the Codex extension after saving. It reads the file when it starts, so the entry does nothing until it does.

If you changed the port. The address above is the default. Earkeep shows its real one: press MCP at the bottom of the left rail, and the Connect apps panel gives you this same block with the right port already in it, ready to copy.

Already added it in the terminal? Then it is already here. The two share this file, so the one command on the CLI page writes the same entry and you can skip this page entirely.

With Earkeep running and the extension reloaded, ask Codex for something only Earkeep can answer:

"Use the earkeep tools to find the last meeting about this project and turn what was decided into a checklist."

Real titles from your own week mean the connection is live. If you have the command line to hand, codex mcp list reads the same configuration and is the quickest way to confirm the entry parsed.

Nothing appears. Three things in order: Earkeep has to be running, the TOML has to be valid, and the extension has to have been reloaded since you saved.

The section header is wrong. It is [mcp_servers.earkeep], with an underscore and a plural. A near-miss parses as an unrelated setting and is ignored without complaint.

The port is wrong. Open Settings → General in Earkeep to see or change the MCP server port. A change takes effect when Earkeep restarts.

It connects but finds nothing. The server searches saved meetings, so a day that was captured but never had a span kept from it has nothing to find.

• Connect Codex CLI: the same server in one command, writing this same file.
• Set up Codex as an in-app agent: the other direction, where Codex runs inside Earkeep beside the meeting.
• Agents and MCP: why both exist and what each is for.
• All Earkeep how-tos.