Give your agent context
Three ways to hand what you captured to an AI agent, by pasting, by pointing it at your folder, or over MCP.
Your agent didn't see the call, the screenshot or the message you copied. Eavesy keeps those as Markdown, and there are three ways to hand them over.
Paste it
Copy a brief, a transcript or a note from the launcher or the web app, and paste it into your agent's chat. Briefs are already split into a summary, decisions and action items, so the agent spends less effort finding what matters.
Add a short instruction with the paste, like "Here's the brief from my design review. Turn the action items into a checklist."
Point it at your folder
The Mac app writes every capture as plain files in ~/Eavesy/Recordings. An
agent that can read files, like a coding agent in your terminal, can search
and read them directly. No account or API is needed.
~/Eavesy/Recordings/2026-06-15 Meeting recording/
├── summary.md
├── transcript.md
├── notes.md
├── meeting.json
└── audio.m4aScreenshots and clipboard captures sit in the same place as screenshot.png,
image.png or note.md. See your files for
the full format.
You can also point your recordings folder at a notes vault, so captures show up next to your other notes.
Connect over MCP
Let the agent look things up itself. Add https://mcp.eavesy.com as a
connector, sign in to Eavesy, and approve it. The agent can then search and
read your recordings, dictations, notes and screenshots. Connections are
read-only unless you allow writes, which also lets it save notes and tick off
action items.
claude mcp add --scope user --transport http eavesy https://mcp.eavesy.comMCP reads from your account, so it only sees what has synced. See Connect an agent over MCP for each client.
Shape the brief for the agent
A coding agent wants file paths and TODOs. A research assistant wants findings and open questions. Regenerate a brief with a built-in format, or make your own template.
Next
Choose the right handoff
These docs are open source. Spotted something wrong or missing?