samsung-notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --exports | No | Path to the folder where you exported notes from your phone (used on Mac, Linux and anywhere other than Samsung Notes for Windows). Put new exports in the same folder any time; Claude sees them on the next question. | |
| --save-dir | No | Folder where Claude saves copies of attached photos and PDFs when you ask it to. Defaults to the "Samsung Notes" folder in Documents. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notes_overviewA | Start here. Shows where notes are read from, every folder with its note count, totals, and any problems such as locked or unreadable notes. |
| list_notesA | Find notes: newest first, filtered by words, folder, modified dates, attachments or handwriting. Returns note ids for the other tools, and next_offset while more remain. |
| read_noteA | Read one note: title, folder, dates, pages, attachment list, typed text with tables, and which pages hold handwriting or drawings. |
| get_page_imageA | See one page as an image. Use it for handwriting, drawings and layout, which read_note's text leaves out. Very tall pages come in overlapping parts: read them all, and count a repeated line once. |
| get_attachmentA | Open a photo or PDF attached to a note, such as an invoice, receipt or scan. Photos come back as images; PDFs as text, plus images of pages without a text layer. Very tall photos and pages come in overlapping parts: read them all before taking figures, and count a repeated line once. |
| save_attachmentsA | Save copies of photos and PDFs attached to notes, such as invoices, receipts and scans, into a folder inside the user's Save folder, under names you choose. Use it only when the user asks to save, collect or organise files. Notes are never changed and no file is overwritten: a taken name gets “ (2)”, and a file whose contents are already in the folder is skipped, so repeating a call is safe. With check_only=true nothing is written: it says which files are already there, so a continued job skips them without opening them. |
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
Each tool has a distinct role in a clean read pipeline: overview, list, read text, render page image, open attachment, save attachments. The only mild overlap is get_page_image vs get_attachment (both return images), but the descriptions clearly separate handwriting/layout on a page from attached files. read_note vs get_page_image is also well delineated as text versus visual.
All names are snake_case and almost all follow verb_noun (list_notes, read_note, get_page_image, get_attachment, save_attachments). notes_overview is the lone noun-first outlier, a minor but noticeable deviation from the pattern.
Six tools is well-scoped for a read-oriented notes server: orientation, discovery, text content, page rendering, attachment access, and export. Each tool covers a step that would otherwise be a dead end, with no filler.
The read path is thorough (overview, paginated listing, text, images, attachments, safe export), but there are no operations to create, edit, move, or delete notes or folders. An agent asked to modify a note has no tool path, which is a notable lifecycle gap even if read-only behavior is intentional.