Daisy App

What daisy-app does

daisy-app MCP server makes Daisy’s meeting library available to MCP clients. Daisy records meetings on Mac, transcribes and separates speakers on-device, and stores audio, transcripts, summaries, and related data locally. Through MCP, an agent can query those sessions instead of relying on a separate cloud meeting database.

The server is useful for questions such as what was decided in recent calls, which follow-up actions were identified, or which meetings match a topic. It also exposes configured folders and destinations. Daisy’s broader app includes meeting recording, push-to-talk dictation, voice notes, summaries, action items, and draft follow-ups; MCP access focuses on the session data and related actions.

How it works

Daisy runs the MCP server inside the macOS app and binds it to 127.0.0.1, keeping network access on the local Mac. The default endpoint is:

http://127.0.0.1:54321/mcp

Requests use a bearer token stored in the macOS Keychain. Daisy rejects requests whose Host or Origin is not local. The port can be changed in the app’s Advanced settings.

Daisy’s connection screen can configure Claude Desktop, Claude Code, Cursor, and Codex. Claude Desktop receives a local command-based configuration entry, while clients that support Streamable HTTP can use the endpoint directly. Claude Code can also be configured with its MCP command and an authorization header.

Setup and configuration

Install the signed, notarized Daisy DMG from the latest GitHub release or mydaisy.io. The app requires an Apple Silicon Mac running macOS 14 Sonoma or later. In Daisy, open Settings → Connections → MCP server, enable the server, and use the relevant Connect button for the client.

For manual HTTP configuration, copy the access token from Privacy → Access token → Copy and send it as:

Authorization: Bearer <access token>

Claude Desktop needs Daisy’s generated command configuration or a stdio-to-HTTP bridge such as mcp-remote, rather than a URL entry directly.

Tools and capabilities

Read-only tools include:

• list_sessions for listing recorded sessions
• get_session for reading a session
• search_sessions for finding relevant sessions
• list_folders for reading available folders
• list_destinations for reading configured destinations

Local editing tools are set_session_title and rename_speaker. Speaker renaming can be cleared with an empty name, and title changes can be reversed by setting the previous title again.

Action tools are disabled until Privacy → Allow actions from MCP clients is enabled. resummarize_session replaces a stored summary using the selected summarizer. route_session_to_destination and route_action_to_destination send a session or one next step to destinations such as Notion, Linear, Slack, a webhook, or another MCP server. Each routing operation creates a new page, issue, or message at the destination.

Limitations and notes

The server cannot delete sessions, audio, or transcripts, and MCP tools cannot change Daisy’s settings. Resummarization may send transcript text to the configured cloud summarizer; local summarization options are available in Daisy. Routing data to external services depends on the destinations enabled in the app.

Audio remains local for MCP use. Daisy’s local-only behavior can change when cloud summarization, attendee research, external routing, Google Calendar, or iPhone sync is enabled. The Apple Intelligence summarizer and Apple SpeechAnalyzer require macOS 26.