Vibe Board VE
Related Servers
Alternatives to Vibe Board VE
- AlicenseAqualityDmaintenanceMost Google Workspace MCPs let you read. This one lets you write — 28 authoring tools on top of taylorwilsdon/google_workspace_mcp, including markdown-to-Docs, smart chips, and recursive Drive copy.1002MIT
Related Servers
- AlicenseAqualityDmaintenancePersistent, 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.5MIT
- AlicenseNot gradedqualityCmaintenanceGives 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 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceGives 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
- AlicenseNot gradedqualityCmaintenancePersistent, 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.4MIT
- AlicenseAqualityCmaintenancePersistent knowledge base tools for Claude Code that store project context, decisions, and patterns locally across sessions, eliminating cold starts.821 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceProvides persistent local memory of Claude Code sessions with TODO management and searchable activity logs via MCP tools.-
TDQS
Scored across 14 tools
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.
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.
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.
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.