Using Enzo with AI Tools

Enzo has two ways to work with your local context using AI. Built-in Enzo Intelligence runs on your Mac. It can summarize a meeting, clean up a dictated note, draft an email, or answer a typed or spoken question using saved recordings, attached files, current-screen text when allowed, and relevant retained Recall. Original sources stay unchanged, and each answer shows the context it used.

Start with Enzo Intelligence

Open Chat directly or start from a completed recording in Speak. Meeting recordings offer a summary. Solo recordings offer a cleaned note or email draft. Ask Enzo stays grounded in the sources shown under Context used, and the one-time Intelligence download keeps the work local.

When an external AI tool helps

After a while, the most useful thing Enzo builds is the pile of transcripts. If you want to search across that history, combine several meetings, or feed your recordings into a coding or research workflow, Enzo's local MCP server connects tools like Claude and Cursor to it. MCP is an open standard that lets an AI tool connect to a source of information.

What external tools add

• Ask about something you said. "What did I tell the team about the launch date?" and the answer comes from your own recordings.
• Combine several recordings. Ask for the decisions that changed across a week of meetings.
• Search by person. "Find where Sarah talked about the budget" works across every meeting she was in.
• Feed your notes to what you're building. If you write your own agents, your voice history becomes context they can read.

How to connect it

First, you'll need an MCP-capable AI tool installed, like Claude Desktop, Cursor, or the OpenAI Codex CLI. That's what Enzo connects to.

The server ships inside Enzo and stays idle until you point an AI tool at it. There's no account and no API key. Its helper keeps the legacy chirp-mcp filename so existing connections survive the rename. The quickest setup is the bundled installer; run it once in Terminal, then restart the tool:

/Applications/Enzo.app/Contents/Helpers/chirp-mcp install claude-desktop

Swap claude-desktop for cursor or codex to set those up instead. Then ask the tool to "search my Enzo transcripts."

Claude Code

Claude Code manages MCP through its own CLI, so add it directly:

claude mcp add chirp /Applications/Enzo.app/Contents/Helpers/chirp-mcp

Anything else that speaks MCP

Run /Applications/Enzo.app/Contents/Helpers/chirp-mcp print-config to get a snippet to paste into any other MCP client. It always points at the same local server.

It stays on your Mac

This isn't a cloud integration, and Enzo still needs none to work. The server only reads your transcripts, never writes or deletes, and never uploads. Nothing about your history leaves the machine, with one honest exception. If you ask a question through a cloud AI like Claude or ChatGPT, the piece of the answer it needs is sent to that service, the same as any prompt you type into it. Use a local model and even that stays on your Mac. Either way, you decide what each tool sees, one question at a time.

Common questions

Do I need an account or an API key?

No. The server runs on your Mac and reads the history that's already there. Nothing to sign up for, nothing to paste in.

Which AI tools work with it?

Any that support MCP. That covers Claude Desktop, Claude Code, Cursor, and the OpenAI Codex CLI today, and since the standard is open, more keep adding it. Each one connects with the same one-line setup.

Is my history safe if I connect a tool?

The connection only reads, and only when you ask it something. A tool can't reach your transcripts unless you've pointed it at the server yourself. With a fully local AI model, nothing leaves your Mac at all. There's more on the on-device design in how Enzo keeps everything private.