everlog-mcp
Related Servers
Alternatives to everlog-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for Day One journal on macOS, enabling search and browsing of entries, photos, and metadata.2-
- AlicenseBqualityCmaintenanceEnables MCP clients to read and search Apple Journal entries on macOS, including recent entries, date ranges, photos, locations, links, and audio transcripts, while remaining read-only.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to query a local MoneyWiz SQLite database through a permanently read-only, local-first interface with Decimal-safe per-currency results for accounts, transactions, categories, payees, tags, budgets, scheduled transactions, and cashflow summaries.MIT
- AlicenseAqualityCmaintenanceLets MCP clients search iMessages, read Apple Notes including checklist state, and look up Contacts on macOS.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to search and read macOS Messages history from a local chat database, including conversations, unread messages, and Contacts-based names. It is read-only, runs over stdio, and cannot send, edit, or delete messages.674 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to read and search macOS Messages history through a read-only MCP interface.-
TDQS
Scored across 7 tools
Each tool targets a distinct resource or operation: journal/tag listing, entry search, full-entry fetch, attachment retrieval, date-based recall, and aggregates. The only near-neighbors (search_entries vs on_this_day) are clearly separated by the 'same month/day in prior years' semantics.
Five of seven names follow a clean verb_noun pattern (list_journals, list_tags, search_entries, get_entry, get_attachment_image). on_this_day and journal_stats break the pattern but are readable and unambiguous, so this is a minor deviation rather than a problem.
Seven tools is well-scoped for a journaling server: metadata lists, search, fetch, attachment access, a recall view, and stats. No tool appears redundant or filler.
The surface is purely read-only and covers browsing, retrieval, and stats well, but there is no way to create, update, delete, or tag entries. Agents can read the journal completely but cannot write to it, which is a notable lifecycle gap.