GoodNotes MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOODNOTES_DB_DIR | No | Path to GoodNotes SQLite databases | ~/Library/Containers/com.goodnotesapp.x/Data/Library/Databases |
| GOODNOTES_TRACKING_FILE | No | Path to processing state file | ~/.goodnotes-mcp/processed.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notebooksA | List all GoodNotes notebooks with their names, IDs, page counts, and last modified dates. Filters out templates (documents with epoch-zero timestamps). Returns a formatted list of user notebooks sorted by last modified date. |
| read_notebookA | Read OCR text from a GoodNotes notebook. Returns the handwriting-recognized text for each page, with multiple word candidates separated by | so Claude can pick the best word from context. Args: notebook_id: The document UUID from list_notebooks page_start: First page to read (1-indexed, default: 1) page_end: Last page to read (0 = all pages, default: 0) |
| read_pageA | Read OCR text from a single page of a GoodNotes notebook. Args: notebook_id: The document UUID page_number: Page number (1-indexed) |
| search_notesA | Search across all handwritten notes using case-insensitive text search. Splits multi-word queries so each word is matched independently — necessary because GoodNotes OCR stores words in separate groups delimited by special chars. Args: query: Search term (each word matched independently, case-insensitive) |
| get_unprocessedA | Get notebooks and pages that haven't been processed yet or changed since last processing. Compares the tracking file against current FTS index to find new/changed content. |
| mark_processedA | Mark pages as processed after they've been written to Obsidian. Args: notebook_id: The document UUID page_ids: Comma-separated page UUIDs to mark as processed |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
read_notebook and read_page overlap significantly, as read_notebook can read a single page using page_start/page_end, causing potential misselection. The other tools (list, get_unprocessed, search, mark_processed) are clearly distinct.
Tool names follow a snake_case verb_noun pattern, but verbs vary (list, read, get, search, mark) and 'get_unprocessed' and 'mark_processed' use adjectives rather than clear nouns, creating minor inconsistency.
With 6 tools, the set is well-scoped for the server's purpose of reading, searching, and tracking GoodNotes content. It is neither too sparse nor overly heavy.
The core workflow of listing notebooks, reading pages, searching, retrieving unprocessed pages, and marking them processed is covered. Minor gaps include redundancy between read_notebook/read_page and no explicit tool for listing page IDs independently.