MCP Notes Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NOTES_DIR | Yes | Absolute path to the notes workspace directory | |
| MCP_NOTES_LOG_LEVEL | No | Logging level (e.g., DEBUG, INFO, WARNING, ERROR) | INFO |
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_notesA | List note titles and workspace-relative Markdown paths. |
| read_noteA | Read one Markdown note by its workspace-relative filename. |
| search_notesA | Search note titles and contents, returning short matching snippets. |
| create_noteA | Create a Markdown note using a safe filename derived from its title. |
| append_to_noteA | Append text to an existing workspace-relative Markdown note. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_note | Create a reusable instruction for summarizing a note. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| notes_index | Return a read-only JSON index of the notes available to this server. |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: listing, reading, searching, creating, and appending. There is no overlap or ambiguity between the operations.
All tool names follow a consistent verb_noun pattern in snake_case. Collection-level operations use plural (list_notes, search_notes) while single-item operations use singular (read_note, create_note, append_to_note), which is a clear and predictable convention.
With 5 tools, the server is well-scoped for a notes management purpose. Each tool covers an essential operation without unnecessary bloat.
The server provides create, read, list, search, and append, but it lacks a delete operation and does not support full overwrite updates. These are notable gaps for a notes domain, limiting the completeness of the tool surface.