MCP Notes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_ACCESS_KEY_ID | No | AWS access key ID for DynamoDB access | |
| AWS_SECRET_ACCESS_KEY | No | AWS secret access key for DynamoDB access |
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 |
|---|---|
| listNotesB | Lists all notes, or search notes with tags you seen in previous list operation. |
| getNoteB | Retrieves a specific note by its ID. |
| writeNoteC | Creates or updates a note with a unique ID suffixed by a random number. |
| deleteNoteC | Deletes a specific note by its ID. |
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 4 tools
Each tool has a clearly distinct purpose: deleteNote removes notes, getNote retrieves single notes, listNotes lists or searches notes, and writeNote creates or updates notes. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern in camelCase (e.g., deleteNote, getNote, listNotes, writeNote). This uniformity enhances readability and predictability across the toolset.
With 4 tools, this server is well-scoped for a notes management system. Each tool serves a distinct CRUD operation (create, read, update, delete), which is appropriate and efficient for the domain without being overly sparse or bloated.
The toolset provides complete CRUD coverage for notes: writeNote handles creation and updates, getNote and listNotes cover retrieval, and deleteNote handles deletion. There are no obvious gaps, enabling agents to perform full lifecycle operations on notes.