Skip to main content
Anarlog gives agents three ways to access meeting context. The Anarlog plugin uses hosted Cloud MCP. Use the local CLI when Cloud is missing a meeting. Local CLI and MCP reads are bounded; both can also stage proposals for human review. Hosted Cloud API and remote MCP are read-only.
  1. List recent meetings on Cloud MCP, or search by a short title fragment.
  2. If Cloud has no match, search again with the local CLI.
  3. Use a returned meeting ID. Never infer or invent one.
  4. Fetch the meeting detail before requesting transcript text.
  5. Fetch recurring history only when earlier meetings are relevant.
  6. Read transcript pages only until the task has enough evidence.
Prefer connected Cloud MCP because each tool carries its input schema. Fill gaps with the CLI. Optional local MCP is for agents that stay fully on-device.

​
Safety boundary

Agents should use an Anarlog interface, not SQLite. The supported interfaces apply Anarlog’s rules for canonical notes, generated summaries, excluded participants, recurring meetings, and transcript text. Meeting reads stay bounded. An agent cannot apply a note or summary change. It can stage a proposal with CLI proposals commands or the local MCP propose_* tools. A human reviews the unified diff in the desktop app and applies or declines it. Hosted Cloud API and Cloud MCP stay read-only. CLI export can create a separate file; replacing a file requires --force. Local CLI and MCP access stays on your computer. Cloud access uploads a separate server-readable copy of your meeting data. Review the Cloud API disclosure before enabling it.

CLI for agents

Use JSON output and resolve meeting IDs deliberately.

MCP for agents

Connect Cloud MCP through the Anarlog plugin, or run local stdio as an option.

Cloud API and remote MCP

Enable hosted access and connect with OAuth or a connector key.

Webhooks

Receive signed meeting events at your endpoint.