Skip to main content
Glama
Sign In
cairn

cairn

by juw12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cairn

No user-submitted related servers found.

    Related Servers

    • Global Agent Memory

      ozankasikci
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides local-first, project-aware durable memory for coding agents, with a human-reviewed Markdown vault, MCP daemon, and dashboard for managing and retrieving shared knowledge.
      39 PyPI
      15
      MIT

    • memex

      jurgentaylor0309
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents persistent, cross-session memory by storing task insights as interlinked markdown knowledge cards and recalling relevant ones before new work begins. Uses plain files and git sync instead of a vector database or embeddings, and exposes this through MCP tools for Claude Code, Cursor, VS Code Copilot, Codex, Windsurf, and other clients.
      5 npm
      ISC
    • papi

      papiofficial

      getpapi
      A
      license
      Not graded
      quality
      B
      maintenance
      A structured project memory MCP server that persists plans, builds, reviews, and decisions across AI coding sessions and tools, enabling continuous project management with a dashboard.
      11
      MIT

    • wadachi

      EliaCinti
      A
      license
      B
      quality
      C
      maintenance
      Persistent memory for AI agents built on the LLM Wiki pattern: a plain-Markdown brain (also a valid Obsidian vault) with SQLite metadata, local semantic search via fastembed (no API keys), one-call session context with project auto-detection, and a decision log with rationale. Works with Claude Code, Claude Desktop, Cursor, and any MCP client.
      31
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: read_note (single full note), list_notes (filtered enumeration), search (keyword match), capture (create), update_note (mutate). The main overlap is between summary-style tools — context, recent, precedent_brief and queue_next all answer variants of 'what should I look at' — but the descriptions draw usable boundaries (project brief vs. recent activity vs. pre-goal history vs. next queue item).

    Naming Consistency3/5

    There is a loose family pattern (read_note, list_notes, update_note, queue_add, queue_next, precedent_brief, precedent_log) but it is mixed with bare nouns/verbs: search, context, recent, capture, log, code_todos. The prefix grouping (note/queue/precedent) helps readability, yet the overall convention is inconsistent.

    Tool Count4/5

    13 tools sits comfortably in the sensible range for a notes/tasks/decisions server and each maps to a real operation. A few (precedent_brief, precedent_log) are narrow, workflow-specific additions rather than core surface, so the set is slightly heavier than strictly necessary.

    Completeness3/5

    Creation (capture, log, queue_add), retrieval (search, read_note, list_notes, context, recent) and in-place mutation (update_note) are covered, but there is no delete, archive, or supersede-by-removal operation for notes, and journal entries appear append-only. Queue items can only be completed indirectly via precedent_log's queue_path, leaving dead ends for basic lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources