Skip to main content
Glama

Related Servers

Alternatives to Seamless

  • A
    license
    A
    quality
    B
    maintenance
    MCP server that exposes agent-memory-daemon to any MCP-compatible client — Kiro (CLI & IDE), Claude Desktop, Cursor, and others. The daemon does the thinking (consolidation + extraction); this server is a thin filesystem bridge so agents can read, append, and search memory through the Model Context Protocol.
    4
    27 npm
    6
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Local, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates
    3
    15
    Apache 2.0

Related Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Shared memory and orchestration for coding agents, enabling persistent knowledge, multi-agent coordination, and a canonical workflow across MCP-compatible AI clients.
    83
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
    2
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    A shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client.
    4
    2
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Persistent memory for AI agents as a single Go binary: hybrid recall, self-building knowledge graph, and a live TUI dashboard. Zero infra, offline-first — works with Claude Code, Cursor, Codex, OpenCode, and any MCP client.
    5
    491
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.
    16
    91 npm
    1
    MIT

TDQS

A3.9/5.0

Scored across 30 tools

Disambiguation4/5

Resource families are clearly separated (memory, notes, tasks, sessions, projects, gardener), and most action variants are distinguished by their descriptions. However, memory_write/memory_edit/memory_append and notes_update/notes_edit/notes_append overlap as multiple mutation routes, and tasks_update can set in_progress while tasks_claim is the lease-based way to start work, so some misselection risk remains.

Naming Consistency4/5

Names are consistently snake_case and mostly resource-prefixed (notes_*, tasks_*, memory_*, gardener_*, project_*, session_*), which makes the API predictable. Minor deviations are capture_url (verb-first), recall (bare verb), and usage_summary (noun_noun), so not perfectly uniform.

Tool Count3/5

30 tools is heavy for an MCP surface and exceeds the typical 3-15 range, though the broad domain (memory, notes, tasks, sessions, projects, gardener, search, usage) justifies many of them. It is more borderline than grossly excessive because each family covers a coherent lifecycle, but consolidation could reduce cognitive load.

Completeness4/5

Core lifecycles are covered: memories and notes have create/read/update/edit/append/delete, tasks have add/claim/release/list/ready/update, sessions have start/update/end, and recall/gardener/usage close most loops. Gaps remain around project metadata lifecycle (project_create/project_list but no project update/delete/rename) and no direct list operations for some auxiliary items such as favorites or sessions.

Maintenance

ActivityActive
ResponsivenessOutdated data