Using Chirp with AI Tools

After a while, the most useful thing Chirp builds isn't any single transcript. It's the pile of them. Every note you dictated, every meeting you recorded, all of it sitting on your Mac. The catch is that a pile of text in an app is hard to actually use. You remember saying something about pricing last week, but finding it means scrolling.

So Chirp runs a local MCP server. MCP is an open standard that lets an AI tool connect to a source of information. With it turned on, the AI tools you already use, like Claude and Cursor, can search and read your Chirp history directly on your Mac. You ask Claude what you decided in Monday's call, and it pulls the answer from your own transcripts instead of you digging for it.

What you can do with it

• Ask about something you said. "What did I tell the team about the launch date?" and the answer comes from your own recordings.
• Turn a recording into a draft. Have Claude summarize last week's call, or shape a dictated brain-dump into a clean email.
• 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

The server ships inside Chirp and stays idle until you point an AI tool at it. There's no account and no API key. The quickest way is the bundled installer, which writes the right config for each tool. Run it once in Terminal, then restart the tool:

/Applications/Chirp.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 Chirp transcripts."

Claude Code

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

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

Anything else that speaks MCP

Run /Applications/Chirp.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 Chirp 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 Chirp keeps everything private.