notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTES_MCP_ROOT | No | 笔记根目录。也可通过命令行参数 --root 指定。 | ./notes |
| NOTES_MCP_SEARCH_BUDGET | No | search_notes 的总字符预算。 | 8000 |
| NOTES_MCP_MAX_NOTE_CHARS | No | read_note 或单篇 Resource 的返回字符上限。 | 20000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | 按关键词全文检索本地笔记,返回命中行前后各若干行的片段(每篇最多 3 段),总长度不超过 8000 字符。适合先定位再精读;不要用它读整篇笔记,那是 read_note 的职责。 |
| read_noteA | 读取单篇笔记的完整正文。path 必须是相对笔记根目录的路径(如 daily/2026-10-01.md),超过 20000 字符会截断并在末尾标注。绝对路径、.. 和指向根目录外的符号链接都会被拒绝。 |
| list_recentA | 列出最近 N 天内修改过的笔记(相对路径 + 修改时间 + 首行标题),按修改时间倒序。适合回答'上周我写了什么'这类问题。 |
| notes_statsA | 返回笔记总数、总字数、标签分布(解析正文里的 #tag)和最近修改时间。用于先摸清语料规模。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly-review | 总结本周关于某个主题的所有笔记,输出 3 条带出处的要点。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| notes-index | 全部笔记的清单(URI、路径、标题、修改时间、字数、标签),JSON 格式。 |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: search_notes returns snippets, read_note returns full content, list_recent lists recently modified notes, and notes_stats summarizes corpus metadata. The descriptions explicitly clarify boundaries, especially search versus read.
Three tools follow a verb_object pattern (search_notes, read_note, list_recent), while notes_stats is noun_noun. The deviation is minor and still readable, but it breaks strict consistency.
Four tools are well-scoped for a focused notes retrieval server. Each tool earns its place and covers a distinct query pattern without bloat.
The read-only surface covers search, full read, recent listing, and stats, but there are no create, update, append, or delete operations. For a notes server, this is a notable gap if agents are expected to manage notes rather than only inspect them.