MCP Notes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| logC | Create or update today's daily log file. Optionally add notes to the log. |
| evaluateInsightB | |
| rollupA | Synthesize my daily note to create an organized rollup of the most important notes with clear categories, connections, and action items. Optionally specify a date (YYYY-MM-DD). Only include notes that actually add long-term value. If you are unsure, call the /evaluateInsight tool to evaluate the long-term value of the thought. If you do not have enough information, stop and ask the user for more information. It is better to not log anything than log something that is not useful. |
| write_noteC | Create a new note or overwrite an existing note with content. Path should be relative to your notes directory. Optionally include tags that will be merged with any existing tags in the note. |
| search_filesA | Recursively search for files and directories matching a pattern in your notes directory. The search is case-insensitive and matches partial names. Returns full paths to all matching items. Great for finding notes when you don't know their exact location. |
| read_noteA | Read the complete contents of a note file from your notes directory. Specify the path relative to your notes directory (e.g., 'Log/2023-01-01.md'). Returns the full text content of the note file. |
| read_multiple_notesA | Read the contents of multiple note files simultaneously. Specify paths relative to your notes directory (e.g., ['Log/2023-01-01.md', 'Rollups/2023-01-01-rollup.md']). Returns each file's content with its path as a reference. |
| list_directoryA | List the contents of a directory in your notes. Shows all files and directories with clear labels. Specify path relative to your notes directory (e.g., 'Log' or 'Rollups'). |
| create_directoryB | Create a new directory in your notes. Can create nested directories in one operation. Path should be relative to your notes directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| end-of-day | Engage in a thoughtful reflection on the day's activities, accomplishments, and insights. |
| system-prompt | Personal pair programmer and frictionless note-taker focused on capturing insights, tracking accomplishments, and remembering useful information |
| idea-smasher | SMASH your big ideas into smaller, more digestible atomic notes! 💥 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as create_directory for directory creation, read_note for reading single files, and rollup for synthesizing daily notes. However, there is some overlap between read_note and read_multiple_notes, as both handle reading files, which could cause minor confusion, but their descriptions clarify the distinction (single vs. multiple files).
The naming conventions are mixed, with most tools using snake_case (e.g., create_directory, list_directory) and one using camelCase (evaluateInsight). This inconsistency reduces predictability, but the names are still readable and generally follow a verb_noun pattern, except for evaluateInsight which deviates in style.
With 9 tools, the count is well-scoped for a notes management server, covering core operations like creating, reading, writing, listing, searching, and synthesizing notes. Each tool serves a clear purpose, and there is no bloat or missing essential functions, making the set appropriately sized for the domain.
The tool set provides comprehensive coverage for notes management, including CRUD-like operations (create, read, write), directory handling, searching, and advanced features like rollup and insight evaluation. A minor gap exists in update operations for notes or directories, as write_note only allows overwriting, but agents can work around this with existing tools.