A
licenseA
qualityC
maintenanceMost 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.
100
2
MIT
Vibe Board VE
by HuntsDesk
Related Servers
Alternatives to Vibe Board VE
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 gradedqualityBmaintenancePersistent, 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
- AlicenseNot gradedqualityCmaintenancePersistent knowledge base tools for Claude Code that store project context, decisions, and patterns locally across sessions, eliminating cold starts.MIT
- FlicenseNot gradedqualityBmaintenanceProvides persistent local memory of Claude Code sessions with TODO management and searchable activity logs via MCP tools.-
- AlicenseAqualityAmaintenancePost-hoc session handoff and project memory for Claude Code: MCP tools list_sessions and handoff turn any session — even crashed or usage-limit-hit ones — into a clean handoff.md another model can continue from, with secrets redacted from every output. Zero dependencies, fully local; also distills a project's entire session history into one cited memory brief.2102 PyPI1MIT
- AlicenseAqualityDmaintenanceCross-surface persistent memory for Claude. Bridges context between Claude Chat, Code, and Cowork via local SQLite with full-text search.68 npm6MIT
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
ActivityMaintained
ResponsivenessNo issues