clawmem-mcp-server
OfficialRelated Servers
Alternatives to clawmem-mcp-server
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.6 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that gives AI agents persistent, searchable memory with importance scoring, knowledge graphs, and autonomous memory consolidation.1-
- AlicenseAqualityAmaintenanceA self-hosted MCP server that gives AI agents shared, long-term memory over a git-backed folder of markdown, enabling persistent knowledge search, read, and write without a database.1620 npm11MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.1 npmMIT
- AlicenseAqualityBmaintenanceMCP server that gives AI agents human-like persistent memory, with auto-encoding, proactive recall, and memory rooms for cross-agent context.11MIT
TDQS
Scored across 39 tools
Tools are grouped into clear categories (collaboration, issue, memory) with distinct purposes. However, 'collaboration_admin_invoke' is a catch-all for rare operations and could be confused with specific collaboration tools, and there is slight overlap between 'issue_create' and 'memory_store' though descriptions clarify.
All tools follow a consistent pattern: category_subcategory_action with underscores, no camelCase or mixed styles. Verbs like list, get, create, update, etc., are used uniformly across categories.
With 39 tools, this exceeds the 25+ threshold considered too many. While the server covers multiple subdomains (collaboration, issues, memory), the number feels heavy and could overwhelm agents without clear need for such granularity.
The tool surface covers CRUD for issues and memories, plus extensive collaboration features (teams, orgs, repos, invitations). Minor gaps: no tool to delete memories (only mark as closed) and no explicit issue label management (handled via update). Overall, the domain is well-covered.