notebook

nb MCP Tools

The nb MCP server provides LLM-friendly access to the nb note-taking system with proper escaping and project-specific notebook context.

When to Use

• Project coordination: Record handoffs, document project policies and procedures, maintain task lists.
• Issue tracking: Create and manage todos with status tracking.
• Knowledge sharing: Document patterns, APIs, and project-specific knowledge.
• Meeting notes: Record discussions and action items.

Scope and Noise Control

• Prefer to update an existing related note/todo over creating a new one when context already exists.
• Avoid logging routine, immediately completed mechanical actions in separate notes.
• Create new notes/todos when information is likely to be useful across sessions or for other collaborators.

Tagging Conventions

Use consistent tags for discoverability:

• Project Component: #component-<name> (e.g., #component-data-models)
• Task Type: #task-<type> (e.g., #task-design, #task-bug)
• Status: #status-<state> (e.g., #status-in-progress, #status-review)
• Coordination: #handoff, #coordination
• Assignment: Avoid owner tags (for example #llm-*) for task ownership. Use lane/folder ownership and explicit owner text in the note body when needed.

Common Patterns

• Check for handoffs: use search with #handoff and #status-review tags.
• Find active component work: use search with #component-<name> and #status-in-progress tags.
• Track todos: use the todo, tasks, do, and undo tools.
• Organize with folders: use folders and mkdir.

Choosing todo vs add

• Use the todo tool for any item with actionable state (open/done): todos, bugs, and issues. This gives the note a checkbox, enables do/undo state tracking, and makes it appear in tasks output.
• Use the add tool for everything else: coordination notes, decisions, designs, ideas, reference material, handoffs, and meeting notes.
• Always specify a folder when creating a note. A note created without a folder lands at the notebook root and is invisible to folder-scoped list views.
• Do not duplicate: if a bug or task is already tracked in issues/<component>/ or todos/<component>/, do not also create a matching todo. Reference the existing selector in coordination notes or related todo bodies instead.