upnote-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPNOTE_DB | No | Path to upnote.sqlite3. Set only if auto-detection fails. | |
| UPNOTE_URL_LIMIT | No | Refuse notes longer than this, to avoid silent truncation. | 100000 |
| UPNOTE_SNAPSHOT_DIR | No | Where the note snapshot is kept. | |
| UPNOTE_DEFAULT_NOTEBOOK | No | Where notes go when you don't name a notebook. | Claude Notes |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upnote_create_noteA | Create a new note in UpNote. Use this to save a summary, plan, snippet or session output. If no notebook is given it goes to "Claude Notes". Content is Markdown. Cannot set tags and cannot edit an existing note. |
| upnote_create_notebookB | Create a new notebook in UpNote. |
| upnote_list_notebooksA | List every UpNote notebook with its live note count. |
| upnote_list_notesA | List the notes in one notebook, newest first. |
| upnote_search_notesA | Full text search across note titles and bodies. Optionally scoped to one notebook. |
| upnote_get_noteB | Get the full text of one note by id. |
| upnote_recent_notesC | The most recently updated notes across the whole library. |
| upnote_list_tagsA | List all tags in UpNote. |
| upnote_open_noteC | Open a note in the UpNote app by id. |
| upnote_open_notebookA | Open a notebook in the UpNote app by title. |
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 10 tools
Each tool targets a distinct resource and action: search, list, get, open, create, and tag/notebook operations are clearly separated. Even similar tools like search_notes and list_notes differ by query-driven search versus notebook enumeration, so an agent should not confuse them.
Almost all tools follow a consistent upnote_verb_noun pattern, such as upnote_list_notebooks, upnote_create_note, and upnote_get_note. The exception is upnote_recent_notes, which is a noun phrase rather than a verb_noun action, creating a minor deviation.
Ten tools is a well-scoped set for a note-taking integration. Each tool covers a meaningful part of the workflow without redundancy or bloat.
The set covers search, retrieval, opening, listing, and creation of notes and notebooks, but it lacks update/delete operations for notes and notebooks. The description of upnote_create_note explicitly notes that existing notes cannot be edited, which is a notable lifecycle gap for a note management server.