everkeep
Related Servers
Alternatives to everkeep
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceA second brain in one cloud-drive folder that your AI agent reads, writes and keeps tidy.3126 npmApache 2.0- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI agents to search, file, and manage personal records such as IDs, insurance, prescriptions, and leases that stay in your own local, NAS, or cloud-synced folders, with expiry reminders and approval-gated writes. Also supports switching between agents without lock-in via an embedded OAuth server, audit trail, and tunnel relay.8 npmMIT

OpenMyMemoofficial
AlicenseNot gradedqualityAmaintenanceGives AI apps a shared, plain-folder memory on your own machine, so whatever you tell one model the others can read, and you can inspect, review and undo every change they make. Memory stays portable across vendors, models and account changes instead of living on a provider's servers.312 PyPI29Apache 2.0- AlicenseAqualityBmaintenanceEnables saving, searching, retrieving, linking and importing AI work as plain markdown files with automatic provenance in a local folder the user owns. Runs entirely on the user's machine with no account, key or network calls, and never deletes anything.11AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceOne shared memory for every AI you use, in plain Markdown files you own. Teach one AI something and the rest know it, with per-AI folder permissions so each assistant only sees what you allow.41 npm11Apache 2.0
- AlicenseAqualityBmaintenanceEnables LLMs to maintain persistent memory by reading and writing Markdown notes and sibling image assets in a user-selected local or sync folder, with no cloud service, account, or server to run.60MIT
TDQS
Scored across 20 tools
Most tools have clearly distinct purposes, and descriptions explicitly cross-reference alternatives (e.g. list_directory vs list_directory_with_sizes vs directory_tree; search_files vs grep_files). There is still mild overlap in the four directory-listing tools and five read/PDF/media tools, but the descriptions resolve it well enough for an agent.
Nearly all names use consistent snake_case with a verb_noun pattern (list_directory, read_text_file, write_file, move_file, search_files, grep_files). A few are noun-only or noun-prefixed (directory_tree, sqlite_schema, sqlite_query), which is a minor deviation rather than a breakdown.
At 20 tools the server is slightly heavy but each surface—filesystem, listing, reading, PDF/media, SQLite—has a legitimate role. The multiple list/read variants are justified by distinct use cases, though a couple could arguably be optional modes.
The vault lifecycle is well covered: create, write, edit, copy, move, trash, read, search, metadata, plus PDF/media and SQLite inspection. Deletion is intentionally replaced by trash_file and SQLite access is read-only by design; minor gaps like no dedicated rename are handled by move_file.