memopaper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMOPAPER_API_KEY | Yes | API key from the dashboard, starting with mp_ |
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 |
|---|---|
| memoA | Save a memo or manage existing ones. Actions and required parameters: add : text(req), group, visibility list : group, visibility, limit get : uuid(req) get_nth : index(req, 1=latest), group latest : group, visibility oldest : group, visibility pop : group — read + delete latest (destructive) delete : uuid(req) (destructive) edit : uuid(req), text(req) stats : (no params) — total and per-group count |
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 1 tool
Only one tool exists, so there is no risk of confusing separate tools. The internal actions (add, list, get, delete, etc.) are distinct and well-named, making selection unambiguous.
The tool is named 'memo' and uses simple verb-based actions. While the verb_noun pattern is not used at the tool level, the internal actions are consistently lowercase verbs, and the overall naming is predictable and readable.
A single tool is quite thin for a tool surface, even though it packs many operations. The server would benefit from splitting actions into separate tools, but the current count is not a functional problem.
The tool provides full CRUD plus list, search-by-index, latest/oldest, pop (read+delete), and stats. This covers the memo domain thoroughly, leaving no obvious dead ends.