Skip to main content

list_notes

List all project-level notes. These are rich notes (title + content) for capturing project context, decisions, patterns, and reference material.

Parameters

project_id
string
Project ID (auto-detected from working directory if omitted)
pinned_only
boolean
If true, only return pinned notes
global
boolean
Set to true to list global planner notes instead of project notes

Returns

notes
array
Array of note objects with ID, title, pinned status, update time, and content preview

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_notes",
    "arguments": {
      "pinned_only": true
    }
  }
}
Response:
Notes (2):
  #5 [pinned] Architecture Decisions
    Updated: Mar 4, 14:30
    Chose PostgreSQL for database, Next.js for frontend. Using Supabase for auth...
  #3 [pinned] API Patterns
    Updated: Mar 3, 09:15
    All API routes follow REST conventions. Use /api/v1/ prefix...

get_note

Get the full content of a project note by ID.

Parameters

note_id
integer
required
Note ID

Returns

id
integer
Note ID
title
string
Note title
content
string
Full note content (supports Markdown)
pinned
boolean
Whether the note is pinned
created_at
datetime
Creation timestamp
updated_at
datetime
Last update timestamp
session_id
string
Claude session ID that created this note (if applicable)

Example

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_note",
    "arguments": {
      "note_id": 5
    }
  }
}

create_note

Create a new project-level note. Use for capturing architectural decisions, discovered patterns, session learnings, or any context that should persist.

Parameters

title
string
required
Note title
content
string
Note content (supports Markdown)
project_id
string
Project ID (auto-detected if omitted)
pinned
boolean
Pin this note to the top (default: false)
session_id
string
Claude session ID that created this note (optional)
global
boolean
Set to true to create a global planner note

Returns

Confirmation message with the created note ID.

Example

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "create_note",
    "arguments": {
      "title": "Database Migration Strategy",
      "content": "## Overview\n\nWe use Prisma for schema management...\n\n## Process\n1. Update schema.prisma\n2. Run `npx prisma migrate dev`",
      "pinned": true
    }
  }
}
Response:
Created note #8: Database Migration Strategy

update_note

Update a project note’s title, content, or pinned status.

Parameters

note_id
integer
required
Note ID
title
string
New title
content
string
New content
pinned
boolean
Pin/unpin the note

Returns

Confirmation message listing the updated fields.

Example

{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "update_note",
    "arguments": {
      "note_id": 8,
      "content": "## Overview\n\nWe use Prisma for schema management...\n\n## Process\n1. Update schema.prisma\n2. Run migration\n3. Deploy to staging first",
      "pinned": true
    }
  }
}
Response:
Updated note #8: content updated, pinned

delete_note

Delete a project note by ID.

Parameters

note_id
integer
required
Note ID

Returns

Confirmation message.

Example

{
  "jsonrpc": "2.0",
  "id": 5,
  "method": "tools/call",
  "params": {
    "name": "delete_note",
    "arguments": {
      "note_id": 7
    }
  }
}
Response:
Deleted note #7

search_notes

Full-text search across all project notes (titles and content).

Parameters

query
string
required
Search query
project_id
string
Project ID (auto-detected if omitted)
global
boolean
Set to true to search global notes instead of project notes

Returns

results
array
Array of matching notes with ID, title, and content preview

Example

{
  "jsonrpc": "2.0",
  "id": 6,
  "method": "tools/call",
  "params": {
    "name": "search_notes",
    "arguments": {
      "query": "database migration"
    }
  }
}
Response:
Search results for 'database migration' (2):
  #8 [pinned] Database Migration Strategy
    We use Prisma for schema management... Process: 1. Update schema.prisma 2. Run migration...
  #12 Rollback Procedure
    When a migration fails in production, follow these steps...

Build docs developers (and LLMs) love