Skip to main content
Anarlog gives agents three ways to access meeting context. The Anarlog plugin prefers the local CLI or local MCP when the agent can access your database. Remote agents use Cloud MCP through OAuth. 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. Honor an explicit source request. Otherwise, use local MCP or check local CLI readiness with anarlog --json doctor; use Cloud when local access is unavailable.
  2. List recent meetings or search by a short title fragment. If a meeting is missing, check an already-connected alternate source unless the user restricted access.
  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.
Keep each meeting’s reads on the source where it was found and label the source in the answer. Report database errors instead of silently falling back to Cloud.

​
Freshness

Local reads work offline and include unsynced changes. They do not require Cloud Sync to finish. Cloud Sync is encrypted; Cloud API & Connectors uploads a separate readable snapshot after opt-in. Sync completion does not establish snapshot freshness. Report freshness only when an interface provides it. A meeting’s updated_at records a content change, not a completed sync or snapshot upload. If freshness matters and cannot be verified, say it is unknown.

​
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

Run local stdio or connect a remote agent through OAuth.

Cloud API and remote MCP

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

Webhooks

Receive signed meeting events at your endpoint.