Skip to main content
Anarlog gives agents three read-only ways to access meeting context. Choose based on where the agent runs.
  1. List recent meetings or search by a short title fragment.
  2. Use a returned meeting ID. Never infer or invent one.
  3. Fetch the meeting detail before requesting transcript text.
  4. Fetch recurring history only when earlier meetings are relevant.
  5. Read transcript pages only until the task has enough evidence.
Prefer MCP when it is connected because each tool carries its input schema. Use the CLI when the agent only has shell access. Both support the same bounded transcript workflow.

​
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 local and 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 remote 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

Configure the stdio server and use bounded transcript pages.

Cloud API and remote MCP

Enable hosted access and create a connector key.

Webhooks

Receive signed meeting events at your endpoint.