Skip to main content
Glama

Related Servers

Alternatives to Memory Journal MCP Server

No user-submitted related servers found.

    Related Servers

    TDQS

    C2.8/5.0

    Scored across 113 tools

    Disambiguation2/5

    The set has many overlapping tools: search_entries overlaps with semantic_search and search_by_date_range, personal and team variants mirror each other, and read_resource/mj_read_resource/memory_read_resource are essentially fallback aliases. Team-prefixed tools are distinguishable, but an agent faces real misselection risk across search, backup, import/export, vector-index, and GitHub issue/PR/kanban operations.

    Naming Consistency3/5

    Most tools use snake_case and the team_* subset is consistently prefixed, which helps. However, personal tools are unprefixed, GitHub tools use mixed patterns (get_github_issues vs move_kanban_item vs close_github_issue_with_entry), and a few names use kebab-case or test/fallback conventions, making the overall naming only moderately predictable.

    Tool Count1/5

    With 113 tools, the surface is far beyond a reasonable scope even for a feature-rich memory journal server. The extensive mirroring between personal and team databases, plus test/fallback handlers and auxiliary GitHub/git tools, makes the set heavy and hard to navigate.

    Completeness4/5

    The memory-journal domain is covered very thoroughly: CRUD, batch operations, search modes, tagging, relationships, imports/exports, backups, restore, vector indexing, statistics, and team collaboration all exist. Minor gaps remain, such as no obvious team restore-backup counterpart and limited GitHub issue lifecycle operations beyond close-with-entry.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data