For a new MCP connection, the first operation should be get(key='README'). This README is the canonical documentation entry point; follow its links for detailed guidance instead of relying on the small connection bootstrap.
This document is the short entry point for the public notes-store conventions. Follow links for detailed rules rather than expanding this page.
• Format Details — JSONHTL block and inline syntax.
• Workflow - Creating and Updating Notes — how to plan, create, link, and update notes without partial states.
• Avoiding Orphaned Notes and Information Loss — preserve discoverability, metadata, and index links.
Connector index (what each MCP server actually exposes — including misc, whose name doesn't say what it does) is at plugins.
• MCP Tools — MCP tools and safe edit strategy for agents.
• Metadata Conventions — standard top-level fields and visible routing guidance.
• Read before writing. Preserve existing links, metadata, and domain-specific fields.
• Create complete child notes first, then link them from their parent and any relevant index.
• Increment version and set updated when changing content.
• Prefer focused notes over large multi-topic documents.
• For MCP edits, read MCP Note Editing Guide before multi-block or structural changes.
Tooling documentation starts at README/tools. Command-line usage is in README/command-line-tools; MCP usage for agents is in README/mcp-tools.
Agent process rules live in Agent Working Practices. Read TRIGGERS to decide which rule notes apply to a task.
Private information — including all db.com work and any other sensitive content — belongs in the private notes store, not here. CLI users: connect to the private store at https://www.critchley.biz/private/mcp (port 8120 internally, stunnel 18121).