Skip to main content
Glama

Related Servers

Alternatives to Vibe Board VE

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    Persistent, cross-session task management for Claude Code. 24 MCP tools for tasks, projects, dependencies, and docs. 7 skills for planning, standups, and handoffs. Event-sourced storage with per-project isolation.
    5
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Gives Claude Code a persistent, fully local long-term memory by automatically capturing session activity, indexing past conversations, projects, scheduled tasks and Obsidian notes, and recalling relevant context through hybrid keyword-plus-semantic search with progressive disclosure. It also writes session handoffs that are injected into later sessions, so work resumes with prior decisions and next steps already in context.
    60 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Gives Claude Code persistent, local-first project memory: it records sessions, compresses them into searchable observations and summaries, and injects a compact project brief plus prompt-time recall at session start. It also exposes tools for recalling observations and timelines, managing durable tasks and notes, and reading any project's context, all backed by a local SQLite file with compression run on a local LLM.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Persistent, shared memory for Claude across sessions and clients (Code, Desktop, Cowork) — deterministic diff reads, checkpoints, cross-client task handoff, and project-wide search. 100% local and deterministic, no API keys, no LLM summarization.
    4
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Persistent knowledge base tools for Claude Code that store project context, decisions, and patterns locally across sessions, eliminating cold starts.
    8
    21 PyPI
    MIT

TDQS

A4.4/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a unique resource/action combination—project, session, task, activity, and handoff—with no overlap. Singular vs plural 'get' tools clearly separate single-fetch from list-fetch.

Naming Consistency5/5

All tools follow the 'board_verb_noun' snake_case pattern consistently. Verbs like create, get, update, delete, end, log, bulk_update are uniformly applied, and noun forms (singular/plural) match their function.

Tool Count5/5

14 tools is well-scoped for a board management server covering tasks, projects, sessions, and activity logging. The count feels neither bloated nor sparse—each tool serves a clear, necessary purpose.

Completeness4/5

Core CRUD operations are present for tasks and projects, plus session lifecycle and activity tracking. Minor gaps exist: no project deletion (only status update), no single-project fetch by ID, and no session list endpoint. These are non-critical for typical workflows.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues