agent-postit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTIT_LOG | No | Log destination. Defaults to '-' (stderr). | |
| POSTIT_HOST | No | Host/interface to bind. Defaults to 127.0.0.1. | |
| POSTIT_PORT | No | Port to listen on. Defaults to 8000. | |
| POSTIT_ROOT | No | Path to the data directory where notes are stored. Defaults to ~/.agent-postit. | |
| POSTIT_TRANSPORT | No | Transport protocol: 'http' (default) or 'stdio'. |
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 |
|---|---|
| topic.createB | Create a topic dir + TOPIC.md description. |
| topic.readB | Read a topic's TOPIC.md description. |
| topic.writeB | Overwrite a topic's TOPIC.md description. |
| postit.createC | Create a new postit note. |
| postit.update_bodyB | Append or overwrite a postit's body. |
| postit.renameB | Rename a postit within the same dir. |
| postit.deleteA | Delete a postit note (dir survives). |
| postit.readC | Read a postit's full body. |
| postit.read_sectionA | Read a markdown section by heading text (case-insensitive, exact). |
| postit.read_linesA | Read a 1-based inclusive line range from a postit body. |
| postit.lsA | List dir contents (ls -la style) or list headings of one postit. |
| postit.searchA | Regex search across postit names and/or bodies (grep-like). |
| postit.recentB | Return most-recently-modified postits (always recursive under dir). |
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 13 tools
Each tool targets a distinct resource and operation: topics have create/read/write, postits have create/read/update/delete/rename/list/search/recent, with read subdivided into full, section, and line-range variants that are clearly differentiated. No two tools overlap in purpose.
Tool names follow a consistent dot-separated resource.action pattern (e.g., topic.create, postit.read_section), but there are minor deviations: 'ls' is an abbreviation rather than a verb, 'recent' is not a verb, and 'update_body' contrasts with 'write' for topics.
With 13 tools, the set is well-scoped for a note/topic management server. Each tool provides a distinct capability, and the count is within the ideal range—neither too sparse nor overwhelmingly large.
The postit lifecycle is fully covered (create, read, update, delete, rename, list, search, recent), and topics have create/read/write. Notable gaps include no topic delete or rename, and postit rename is restricted to the same directory, preventing moves. These are minor but slightly limit full lifecycle management.