Pocket Notes MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POCKET_NOTES_FILE | No | Path to the notes JSON file. Defaults to data/notes.json in the current working directory. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | List note summaries, optionally filtered by an exact tag. |
| create_note | Create a local note. This changes the notes JSON file but does not delete data. |
| analyze_notesA | Count notes by tag while demonstrating MCP progress notifications and cancellation. |
| summarize_noteA | Read a note and ask the MCP client's language model to summarize it using MCP sampling. |
| create_note_interactiveA | Ask the user for non-sensitive note fields through MCP form elicitation, then create the note. |
| list_workspace_rootsA | Ask the MCP client which workspace roots it has made available to this server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_note | Create a reusable learning prompt for one saved note. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| note-catalog | A compact JSON catalog of every note. |
| MCP Host와 Client | #mcp #architecture |
| Tools, Resources, Prompts | #mcp #concepts |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing notes with optional tag filter, analyzing notes by tag, summarizing a note via sampling, interactively creating a note, and listing workspace roots. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_notes, analyze_notes, summarize_note, create_note_interactive, list_workspace_roots), making them predictable and easy to parse.
With 5 tools, the server is well-scoped for its purpose of demonstrating MCP features (progress notifications, sampling, form elicitation, workspace roots) while maintaining a manageable tool surface.
As a notes management server, essential operations like updating, deleting, or searching notes are missing. The tool set is incomplete for actual note management, likely because it prioritizes demonstrating MCP capabilities over full CRUD coverage.