syntheo executable and read the app’s local database. Neither goes through a remote server.
A Syntheo skill teaches the agent when and how to use these two access methods.
Start by installing the CLI.
Recommended approach
- Check that local access is ready with
syntheo --json doctor, or use an MCP server that is already connected. - List recent meetings or search for a short fragment of the title. For a project or a client, list the folders and filter by folder path.
- Use a meeting ID returned by the tool. Never guess one.
- Read the meeting details (note, summaries, participants, action items) before asking for the transcript.
- Only ask for the history of a recurring series if previous meetings matter.
- Read the transcript page by page, and stop as soon as you have enough information.
Data freshness
Reads cover the local database as it is at the time of the call. They work offline. A meeting’supdated_at field shows when its content was last changed.
Security boundaries
Agents go through the CLI or the MCP, never directly through SQLite. These interfaces apply Syntheo’s rules: canonical note, generated summaries, recurring meetings, transcript text. Reads stay bounded. An agent can’t edit a note or a summary directly. It can only prepare a proposal with the CLI’sproposals commands or the MCP’s propose_* tools. You then review it in the app: the “1 pending edit” banner appears on the meeting, with “Review memo” or “Review summary”. You then choose “Apply to memo”, “Apply to summary” or “Decline”.
The CLI export can create a file; replacing an existing file requires --force.
The CLI and the MCP send nothing to a Syntheo server. However, what the agent reads is sent to the language model it uses. Choose an agent and a model provider that match the confidentiality of your meetings.
CLI for agents
JSON output and meeting IDs.
MCP for agents
Local stdio MCP server.
Syntheo skill
Install the skill in your agent.
Errors and exit codes
Diagnose a failure.