mothermachine

Browse / Notes and knowledge

Tolaria

Files-first markdown second brain with git built in and an in-repo MCP server for Claude Code and Codex.

Operable Business appDesktop app Hybrid TypeScriptJavaScript MCP server License: AGPL-3.0

Tolaria is a desktop app for macOS, Windows, and Linux that manages a vault of markdown notes with YAML frontmatter, each vault a git repository. The Builder bundles an MCP server (mcp-server/) that lists and attaches vaults and lets an agent search, read, create, update, and open notes in the running app.

Use it when
  • you want your notes as plain markdown in git and an agent that can search and write them from Claude Code
  • you run a 10,000-note personal vault and want keyboard-first navigation with AI on the side
Gotchas
  • AGPL-3.0-or-later
  • The MCP server talks to the running desktop app over a websocket bridge; open_note and vault attach need the app open
  • No paid or hosted edition; sync is whatever git remote you choose

Last activity Sep 3, 2026. Fit: adaptable 1, operable 3.

Editions

Free · Free open source

  • Clonegit clone https://github.com/refactoringhq/tolaria
  • DownloadDownload

For agents: JSON · Markdown

Operable: what an agent can drive

Interface

OfficialMCP serverpublished by the builderlocal

How an agent can drive an Operable Listing, in five levels: native (built for the agent as the primary interface), official (the Builder ships an agent interface), wrapped (a third party wraps the software's API), config (an agent can only drive it by editing files), gui (screen control only). An interface is official only when it is published by the same organization that ships the software. GUI-level Listings are allowed and sorted last.

Docs
github.com/refactoringhq/tolaria/tree/main/mcp-server
Tools
list_vaults attach_vault clone_vault refresh_vault get_vault_context search_notes get_note create_note update_note append_to_note open_note

Reach

Partial coverage. 4 of 8 jobs reachable through the stated interface.

JobThrough the interfaceEvidence
Create, read, update, and append to notesReachablecreate_note, get_note, update_note, append_to_note in mcp-server/index.js
Search notesReachablesearch_notes tool
Manage vaults (list, attach, clone, refresh)Reachablelist_vaults, attach_vault, clone_vault, refresh_vault
Open a note in the appReachableopen_note tool over the ws-bridge to the desktop app
Types and note relationshipsUndeterminedget_vault_context likely returns vault metadata; not verified
Git commit, push, and historyNot reachableno git tool in mcp-server; the vault is a plain git repo an agent can drive with shell
In-app AI chat over note contextNot reachablehuman UI feature
Inbox and web-resource captureNot reachablewalkthroughs describe UI workflows; no capture tool

Code stack

Languages
TypeScriptJavaScript
Frameworks
Vite
Package manager
npm
Database
none
Hosting target
local
Built
Mixed (recorded, never ranked)

Model stack

Providers
local agents (Claude Code, Codex, OpenCode, Pi, Gemini CLI)API model providers for in-app chat
Models
none
Keys you need
none
Prompts live in
none

Evidence and confidence

FieldWhere it was seenConfidence
formFactorREADME: desktop app for macOS, Windows, and Linux95%
executionModeltolaria.md: chat with local or API model providers over note context; note editing needs no model70%
operabilitymcp-server/ directory in the same repo; tool names read from mcp-server/index.js90%
effort.env.example holds only LARA_ACCESS_KEY_ID, LARA_ACCESS_KEY_SECRET, VITE_POSTHOG_KEY, VITE_POSTHOG_HOST, VITE_SENTRY_DSN: build-time telemetry, not a behavior surface for an Adopter, so Adaptable is not claimed70%
editionstolaria.md: 'Free forever', no account; releases on GitHub90%
activepushedAt 2026-09-03; Show HN 2026-04-23 with 318 points–
provenanceREADME: sponsors keep the project 'ready for AI-assisted development'; CLAUDE.md and AGENTS.md at root50%
reach85%

Open questions

  • Does get_vault_context expose types and relationships?
  • Is there an app-level config file (mcp-server/app-config-policy.json suggests a policy surface) that would justify an Adaptable capability?

Sources