Skip to main content
Glama

Related Servers

Alternatives to Learning MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables developers to maintain a local engineering journal, log work manually or from git history, and let AI assistants query, summarize, and draft standup updates, changelogs, and retro notes.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to maintain a persistent developer logbook with notes, TODOs, reminders, code TODO scanning, and full-text search, while keeping all data local and optionally syncing with Obsidian.
      56 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides AI coding assistants persistent engineering memory stored as Markdown files in an Obsidian vault, enabling project context retrieval, session capture, decision recording, and memory search without requiring Obsidian to be running.
      7
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Turns AI coding conversations into structured Markdown notes in an Obsidian vault, and retrieves that knowledge in later sessions so assistants can reuse prior conclusions.
      5
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to document a code repository inside an Obsidian vault, capturing tasks, incidents, feature guides, architecture decisions, and release notes with per-claim evidence and cited sources. It reads the repo read-only through a configurable allowlist and previews every change before a single-use confirmation code applies it.
      MIT

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the learning workflow: feature lifecycle, context, decision records, debug attempts, session sync, manifest retrieval, evidence details, and final review. There is no meaningful overlap that would cause an agent to pick the wrong tool.

    Naming Consistency5/5

    All tool names follow a clear snake_case verb_noun pattern, with get_, record_, start_, save_, finish_, and sync_ as predictable action prefixes. The naming is internally consistent and easy to navigate.

    Tool Count5/5

    Ten tools is well-scoped for a learning-tracking MCP server covering feature lifecycle, context, decision/debug capture, Codex session synchronization, evidence retrieval, and review export. Each tool has a clear purpose and none feel redundant.

    Completeness4/5

    The core lifecycle is well covered: start a feature, capture decisions and debugging, sync sessions, retrieve evidence, save reviews, and finish. The main gap is the lack of update/correction or delete/abandon operations for recorded data, though this can be worked around by appending new records.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues