A
licenseNot graded
qualityB
maintenanceA local persistent memory and developer scratchpad MCP server that allows AI assistants to store, search, and manage notes across chat sessions.
MIT
agent-postit
by gerelef
Related Servers
Alternatives to agent-postit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI agents persistent, file-based memory stored as plain markdown files in a local git repository, enabling agents to remember, recall, and build on information across sessions.221MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that gives AI assistants long-term memory by storing, searching, and recalling notes as Markdown files on your machine.10MIT
- AlicenseAqualityBmaintenanceAn MCP server that gives AI models a persistent notebook backed by a folder of Markdown files, with tools to discover, read, write, edit, and delete notes.9MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives LLM agents persistent, directory-scoped memory using markdown files, supporting workspace-specific notes and read-only shared memories.MIT
- AlicenseAqualityCmaintenanceMCP server that exposes an Obsidian-style markdown vault as a shared memory for AI agents, with tools for searching, reading, writing, and querying notes and wiki-links.123MIT
TDQS
A3.5/5.0
Scored across 13 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivitySlowing
ResponsivenessNo issues