Daisy

Read your Daisy sessions from Claude, Cursor, or any MCP client

Daisy ships a local MCP server (Model Context Protocol). Turn it on and any compatible AI client running on the same Mac can list, search, and read your finished sessions — transcripts, summaries, action items, the lot. Everything stays on127.0.0.1; nothing leaves the machine.

What you get

Four read-only tools the client can call:

list_sessions
Metadata for every session — title, date, duration, preview. Filterable by folder / date range / limit.
get_session
Full content of one session: transcript, summary, action items, attendees, screenshots.
search_sessions
Substring search across titles, transcripts, and summary fields. Returns snippets so the AI can decide which sessions to fetch in full.
list_folders
The folder slugs you’ve set up. Use as thefolderargument to list_sessions.

No write surface — the AI can read, not delete or edit. That’s by design.

Setup — Claude Desktop

One-click flow from inside Daisy:

  1. Daisy → Connections → MCP server → flip the toggle ON. Status badge should turn green (Running) within a second.
  2. Click Add to Claude Desktop. Daisy writes the right snippet into ~/Library/Application Support/Claude/claude_desktop_config.json (merges with anything else you already have there).
  3. Fully quit Claude Desktop (⌘Q — not just close the window) and reopen. Claude only re-reads the MCP config on cold start.
  4. In a new chat, ask: “List my last 5 Daisy meetings.” First call takes a few seconds whilenpxfetches the mcp-remotebridge. After that it’s instant.

Requires Node.json your Mac (any recent version). Claude Desktop’s MCP config expects a stdio transport, so Daisy’s SSE server is wrapped through the mcp-remote bridge that npx auto-fetches.

Manual config (if the in-app button doesn’t work)

Open ~/Library/Application Support/Claude/claude_desktop_config.json in any editor (Claude Desktop → Settings → Developer → Edit Config creates it if missing). Add Daisy under mcpServers:

{
  "mcpServers": {
    "daisy": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:54321/sse",
        "--transport", "sse-only",
        "--allow-http"
      ]
    }
  }
}

The two extra flags after the URL aren’t optional —--transport sse-onlypins mcp-remoteto the transport Daisy speaks (no failover to newer Streamable HTTP that doesn’t exist on the server), and--allow-httppermits plain HTTP on loopback (mcp-remote defaults to HTTPS-only).

Then ⌘Q and reopen Claude Desktop.

Setup — Cursor / Cline / Continue

Cursor, Cline (VS Code extension), Continue, and most other MCP clients accept the same stdio config Claude Desktop does. Drop the same snippet into the MCP-servers section of their settings JSON. Daisy’s Copy snippet button gives you the exact block, formatted right.

Some clients support direct SSE without the bridge — in that case skip mcp-remote and point them at http://127.0.0.1:54321/sse directly.

What to actually ask the AI

Once Daisy shows up in your AI’s tool list, the interesting prompts aren’t “use the list_sessions tool.” They’re natural-language asks that the model decomposes into multiple tool calls on its own:

Quick lookup

  • “Show me the transcript of my most recent meeting.”
  • “What did I talk about on Tuesday?”
  • “Pull the last 10 sessions tagged 'Mediacube'.”

Cross-session synthesis

  • “Compile all the action items from my last 10 meetings into one list, grouped by owner.”
  • “What did Maria say about pricing across our last three calls?”
  • “Summarise everything happening with the Garna deal across every Daisy session that mentions it.”

Drafting

  • “Draft a follow-up email based on yesterday's Mediacube meeting.”
  • “Write a Slack post for the team summarising this week's customer calls.”
  • “Turn the action items from the last sprint planning session into Linear-ready ticket titles + descriptions.”

Analytics

  • “How many meetings did I have last week? How long, on average?”
  • “Which client takes up the most meeting time in my calendar?”
  • “List every meeting where I committed to sending something, but the email never went out.”

Troubleshooting

Claude says “Some MCP servers could not be loaded”
The config schema is wrong — likely an old {"url": ...} entry from a previous Daisy build. Use the manual snippet above (command/args shape) and restart Claude.
Claude doesn’t show Daisy in the tool list
You didn’t fully quit Claude — close the window isn’t enough. ⌘Q or force-quit in Activity Monitor, then reopen.
First tool call hangs for 10+ seconds
Expected on first run — npx is downloading the mcp-remote package (~2 MB). Subsequent calls are instant.
“Connection refused” / no Daisy data comes back
Daisy app needs to be running AND the MCP toggle ON. Check Daisy → Connections → MCP server: the badge should read Running. If it says Error, hover for the specific message.
Port 54321 already taken
Change the port in Daisy’s settings, then click Add to Claude Desktop again — the config gets rewritten with the new port. Restart Claude.
Sanity-check the bridge from Terminal
curl -sN http://127.0.0.1:54321/sse should open a streaming connection that hangs (correct — it’s SSE). Ctrl+C to close. If you see Connection refused, the Daisy server isn’t listening.

Privacy reminder

The Daisy MCP server only binds to 127.0.0.1(loopback). Other machines on your network can’t reach it. Cross-origin browser requests are blocked. Your transcripts never leave your Mac — Claude (or whichever client you use) pulls them locally through the bridge and processes them under its own rules. See the Privacy page for the full posture.