mcp-lab-01-notes-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTES_SERVER_DIR | No | Directory where notes are stored. If not set, defaults to ~/.mcp-lab/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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteA | Cria uma nova nota (ou tarefa pendente, se is_task=True). |
| list_notesA | Lista todas as notas e tarefas salvas, com título e status. |
| read_noteB | Lê o corpo completo de uma nota pelo slug. |
| mark_doneB | Marca uma tarefa como concluída (status vira 'done'). |
| delete_noteA | Apaga uma nota permanentemente pelo slug. |
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 5 tools
Each tool has a clear primary action, and the CRUD operations are distinct. However, create_note doubles as a task creator via is_task, and mark_done applies only to tasks, which could cause slight ambiguity about whether notes also support status changes.
Most tools follow a clear verb_noun pattern (create_note, list_notes, read_note, delete_note), but mark_done breaks the pattern by using verb_adjective instead of verb_noun. This is a minor inconsistency that still leaves the intent understandable.
Five tools is appropriately scoped for a simple notes/tasks server. The set covers the essential operations without unnecessary bloat, making it easy for an agent to navigate.
The set lacks an update_note/edit_note operation, which is a notable gap for a notes domain. It also has no way to unmark a task or filter tasks from notes, limiting full lifecycle management for tasks.