F
licenseA
qualityD
maintenanceProvides persistent memory for MCP-compatible agents (like Copilot CLI) to save and recall knowledge across sessions, plus long-running monitoring tools.
9
-
limai
by win10ogod
Related Servers
Alternatives to limai
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocal-first memory MCP server that captures macOS screen and app context into persistent Markdown, enabling any tool-capable LLM agent to query its working history.MIT
- FlicenseBqualityCmaintenanceAn all-in-one MCP server that enables AI agents with local system capabilities like filesystem navigation, command execution, desktop automation, and a continuity memory suite for persistent cross-session project context.37-
- AlicenseNot gradedqualityFmaintenancePersonal AI cognitive exobrain server providing long-term, emotionally-tagged memory and task management for LLMs via MCP.1MIT
- FlicenseNot gradedqualityDmaintenanceA personal desktop automation MCP server providing tools for screen/mouse/keyboard control, Windows UI automation, headless browser automation, file management, app execution, clipboard management, and a personal SQLite database for todos, notes, and habits.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage SQLite-backed TODOs and schedule durable coding-agent jobs over stdio, with persistent job memory, run history, and a read-only dashboard.MIT
TDQS
A3.5/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a distinct resource and action—monitoring (screen, windows, clipboard, heartbeat), memory (add/search/list/forget), todo (add/list/update), web (search/fetch), and filesystem (ls/read/write/edit/find/grep). There is no meaningful overlap; even fs_write vs fs_edit are clearly separated by create/overwrite vs precise replacement.
Naming Consistency5/5
All tool names follow a consistent 'domain_action' pattern with snake_case (e.g., memory_add, web_fetch, fs_grep). The verb is consistently after the domain, and every name is lowercase, making the API predictable and easy to navigate.
Tool Count4/5
With 21 tools, the server is slightly above the ideal range but each tool serves a clear purpose across multiple domains (system monitoring, memory, todos, web, filesystem). The count is justified given the broad scope, though a few tools could potentially be consolidated without losing clarity.
Completeness3/5
The server covers most core operations for its domains—memory and todo have full CRUD-ish coverage, web has search and fetch, and filesystem has read/write/edit/find/grep. However, the absence of a file deletion tool (e.g., fs_delete) leaves the filesystem incomplete, and there is no explicit tool for renaming or moving files. This gap could cause agent failures when cleanup is required.
Maintenance
ActivitySlowing
ResponsivenessNo issues