memo-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createMemoC | Create a new memo |
| getMemosC | Get all memos |
| getMemoA | Get a single memo by ID |
| updateMemoC | Update a memo |
| deleteMemoB | Delete a memo |
| searchMemosB | Search memos by keyword and date range |
| createCategoryC | Create a new category |
| getCategoriesA | Get all categories |
| getCategoryA | Get a single category by ID |
| updateCategoryD | Update a category |
| deleteCategoryC | Delete a category |
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 11 tools
Each tool targets a distinct resource (category or memo) and action (create, read, update, delete, search), with no overlap or ambiguity.
All tool names follow a consistent verb+noun pattern using camelCase (e.g., createCategory, getMemos, deleteCategory), making them predictable.
11 tools provide full CRUD for two resources plus search, which is well-scoped for a memo management server without excess.
Covers complete lifecycle for categories and memos (create, read, update, delete) plus search, with no obvious missing operations.