Choose MCP, CLI, or the Notes API
Pick the safest way for an app, agent, or script to work with your Monologue notes.
Monologue offers several ways to use Voice Notes outside the app. Choose based on where the work will happen.
| Use case | Choose |
|---|---|
| Chat or desktop app with hosted connectors | MCP |
| Terminal workflow or local coding agent | Monologue CLI or agent setup |
| Your own application or automation | Public Notes API |
| Event delivery to a server, when enabled | Webhooks |
All of these connections should receive only the access they need. None of them can edit or delete your notes.
| Connection | Read notes | Turn share links on or off |
|---|---|---|
| MCP | Yes | Yes, for notes you own with notes:write |
| Monologue CLI | Yes | No |
| Public Notes API | Yes | No |
Every connection that reads notes also sees whether a note has a public share link.
MCP
Use MCP when the AI app supports a hosted MCP connection. The browser authorization flow avoids copying an API key into the client and lets you revoke that connection later. MCP is the only connection that can publish or revoke a note’s public share link; see Share links from an agent.
CLI and local agents
Use the Monologue CLI for terminal searches, scripts, and local agents. It uses a personal Notes API key stored on your computer.
On Mac, Settings → Notes → Connect an AI Agent can copy a current setup message for supported local agents. The message includes installation, authentication, and a verification step.
Public API and webhooks
Use the Public Notes API when you are building your own integration. Create a separate key for each integration so you can revoke one without interrupting the others.
Webhooks deliver note-processing events to a server. They are not enabled for every account. If Webhooks appears in your settings, read the webhook guide before accepting events in production.