MCP tools reference
The 22 tools the local MCP server exposes (18 without Jira): what each one reads, and the six that write locally.
The local MCP server exposes 22 tools. Sixteen read data that is already on the Mac; six write, and every write is local — to-dos and agent-memory notes. There is no Jira write tool and no delete tool, so an agent cannot change Jira or remove anything.
Without Jira, the four tools that only mean something with it — jira_search, jira_issue,
jira_projects and sessions_for_issue — are not listed and cannot be called, so an agent sees 18 tools.
How to use it
Tool names are what the agent calls. In practice you describe the task and the agent chooses; the table is here for checking what it can reach.
| Tool | What it returns | Writes |
|---|---|---|
jira_search | Issues from the local Jira copy, by text or key | — |
jira_issue | One issue by key, with its fields and its place in the hierarchy | — |
jira_projects | Projects with issues in the local cache, with their issue counts — mostly the projects of the boards you added | — |
meetings_list | The meetings in the archive, newest first | — |
meeting_get | One meeting by id, with its stored text | — |
todos_list | The to-do list, with groups, parent links and done state | — |
todo_get | One to-do | — |
todo_create | The new to-do, created locally for you to review | Local to-do |
todo_update | The updated to-do | Local to-do |
timeline | The Timeline for a day: meetings, sessions and commits | — |
sessions_for_issue | The coding-agent sessions linked to a ticket | — |
sessions_search | One row per matching Claude Code conversation, best match first | — |
kb_list | The knowledge bases you added | — |
kb_search | Notes matching the words | — |
kb_read | One note's text | — |
memory_recall | The memory note most relevant to a task, by words and meaning | — |
memory_search | Memory notes matching the words | — |
memory_read | One memory note | — |
memory_write | The new memory note | Memory note |
memory_update | The edited memory note | Memory note |
memory_forget | Confirmation; the note moves to Archive/ | Memory note |
memory_feedback | Confirmation; recall feedback is recorded | Feedback record |
Staging a group. A parent to-do and its sub-items can be staged with the to-do tools in one go — a story with its sub-tasks. They are still local drafts until you send them, exactly like a single one.
The vault. For a kind kept in the encrypted vault, the tools return in_vault instead of the
text: a sealed transcript is null with transcript_in_vault: true. meetings_list still lists such
meetings by date — the agent learns that the meeting exists, not what was said. The MCP server cannot read
the vault (see The encrypted vault).
Settings
There are no per-tool settings. Access is decided by what exists on the Mac: the meeting archive, the Jira copy, the knowledge bases and the memory base.
| Setting | Where | Why it matters |
|---|---|---|
| Coding agents | Settings → Coding agents | Adds or removes the server for an agent |
| Agent memory | Settings → Knowledge → Agent memory | Which base the memory tools use |
| Repositories | Settings → Repositories | What the timeline tool can see |
What is stored
| Tool family | Reads from |
|---|---|
jira_* | ~/Library/Application Support/Sonavia/jira.sqlite3 |
meetings_*, meeting_* | ~/Library/Application Support/Sonavia/Meetings/ |
todo_*, todos_* | ~/Library/Application Support/Sonavia/workspace.sqlite3 |
timeline, sessions_* | Timeline.json, HarnessSessions.json and claude-search.sqlite3 |
kb_* | The knowledge-base folders you added |
memory_* | Markdown notes in the base marked as agent memory |
The only writes land in workspace.sqlite3 (to-dos) and in the memory base (notes).
What leaves your Mac
Nothing leaves the Mac. Every tool answers from local files over the agent's own stdio pipe. The server
makes no internet request and cannot call Jira; memory search asks the local Ollama on 127.0.0.1 for
embeddings.
When it is off or fails
- An agent that is not connected: it sees no tools at all; the local MCP server page shows which agents are set up.
- A missing tool or bad arguments: the client gets a JSON-RPC error, not a crash.
- A to-do written by an agent: it appears in the app as a local draft. Nothing reaches Jira until you send it.
- A memory note written by an agent: it appears in the memory base, or in
Proposed/under it if that base asks you to review agent writes first. Either way it is indexed at once. - Jira is unreachable:
jira_*tools still answer from the last local copy. - No Jira account: the four Jira tools are not offered, and calling one gets the same answer as an unknown tool. The server decides this when it starts, so after connecting Jira, restart the agent.
Related
- The local MCP server — setup and status.
- Agent memory — the notes the memory tools read and write.
- Knowledge bases — the
kb_*tools.
The local MCP server
Your coding agent reads meetings, to-dos, tickets and notes locally, over a server where nothing leaves the Mac.
Chats
Every Claude Code and Codex conversation on your Mac in one place: newest first, searchable as you type, formatted to read and copy. Read on your Mac, after you allow it.