LokalBot
Related Servers
Alternatives to LokalBot
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocal memory for coding agents. Stores Claude Code, Codex and pi conversation text and saved decisions on your machine, so agents can search them and read the source records in later sessions.6MIT
- AlicenseNot gradedqualityCmaintenanceLocal, private memory layer for notes and files with temporal reasoning and citation. Enables agents to query and persist memories via the Model Context Protocol.8 npm5MIT
- AlicenseNot gradedqualityBmaintenanceA local-first AI secretary that gathers your work context into private memory and enables AI agents to search and summarize it over MCP.10 npmMIT
- AlicenseNot gradedqualityCmaintenanceGives AI tools a persistent, local memory that survives across sessions and clients, storing each memory with a supporting quote and date in a single SQLite file. Proposed memories wait in a review queue so a human approves, replaces, or rejects them, and recall combines pinned, full-text, and recent entries.82 npmMIT
- AlicenseAqualityBmaintenanceEnables multiple AI agents on one machine to write, search, fetch, link, and give feedback on a shared local store of Markdown-backed facts, preferences, and conventions that persists across sessions. Memories gain confidence as different hosts confirm their use and can be distilled into denser ones, so agents stop re-discovering the same context.5108 PyPI1MIT
- AlicenseAqualityBmaintenanceEnables local-first, verbatim memory retrieval for AI agents, storing notes and text across sessions and retrieving original passages without generative rewriting.6115 PyPIMIT
TDQS
Scored across 16 tools
Most tools target a clearly distinct resource: meetings (list/get/search), people (list/get), files, agent notes, and screen memory each have separate entry points. The main soft spots are within the screen-memory family (get_timeline vs get_recent_activity vs get_app_usage vs search_screen) and the two meeting-answer paths (search_meetings vs ask_library), which an agent could plausibly confuse. Descriptions do enough work to resolve these in practice.
Every name follows a verb_noun pattern (get_, list_, search_, ask_) in snake_case throughout. The verb choices map predictably to intent: list_ for enumeration, get_ for single-resource fetch, search_ for query-based retrieval. No camelCase or stylistic drift.
16 tools is on the heavy side of the ideal band, but the server spans genuinely separate domains (meetings, people, action items, screen memory, files, agent notes, personal context), so the count is largely earned. Each screen-memory tool does something distinct rather than being a redundant variant.
Meetings have a full read lifecycle (list, get with pagination, search, synthesized Q&A) and people/action items/timeline have sensible entry points. Gaps are minor: search_files returns only a matching passage with no way to fetch a full document, and action items are list-only with no per-item fetch or status mutation from the agent side. These are workable around for a read-only memory server.