A
licenseNot graded
qualityB
maintenanceAutomatically captures project state on git commits, detects context drift, and delivers structured token-budgeted briefings to AI agents, ensuring project continuity without manual effort.
86 npm
2
MIT
continuity
by vikcena01
Related Servers
Alternatives to continuity
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to maintain Git-backed long-term project memory over MCP, supporting on-demand retrieval, curated writes, conflict-safe versioning, idempotency, and crash recovery so new sessions or machines can recover context and continue working.6Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides AI coding assistants with persistent project memory by capturing development checkpoints during git commits, branch switches, and inactivity. It enables seamless task resumption through tools that retrieve session history, momentum, and synthesized re-entry briefings.12 npm3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persist context across sessions by saving, searching, checkpointing, restoring, and organizing decisions, progress, files, and Git-related state.250 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persistently save, search, checkpoint, and restore project context across sessions, including decisions, progress, and file state. It supports shared channels, git-aware organization, and batch operations for long-running or parallel development workflows.250 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persistently save, search, and restore project context across sessions, including decisions, progress, file caches, checkpoints, and channel-based memory. It supports git-aware organization, batch operations, and shared memory across parallel sessions.250 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append validated, audited, idempotent progress events that are recorded as a matching Git commit. This keeps project truth in Git so work stays visible, resumable, and safely handable between humans and agents through scoped, short-lived credentials.-
TDQS
A4.4/5.0
Scored across 13 tools
Disambiguation4/5
Most tools target a distinct claim type or action, with record_constraint/decision/rejection/open/mission clearly scoped by their descriptions. The main ambiguities are record_open acting as a catch-all for four different item kinds (question, risk, milestone, next action) and capture partially overlapping with the individual record_* tools, though it is explicitly positioned as a batch reconciliation entry point.
Naming Consistency4/5
The record_* family gives a strong consistent prefix for append operations, and most other tools use verb_noun snake_case like resume_context, search_claims, freeze_claim, and list_projects. The outliers are 'capture' as a bare verb and 'why' as a question word, plus a slight singular/plural mismatch between freeze_claim, resolve_claim, and search_claims.
Tool Count5/5
At 13 tools, the surface is well-scoped for a persistent project-memory domain: every tool addresses a distinct part of the lifecycle including record, batch, query, freeze, resolve, explain, and project management. No tool feels redundant, and the count stays inside the ideal range.
Completeness5/5
The set covers the full lifecycle: project initialization, recording constraints, decisions, rejections, open items, and missions; batch capture with deduplication and conflict handling; freezing; resolving and archiving; and historical explanation. The append-only model deliberately omits destructive updates, but superseding via capture and unfreezing via resolve_claim fill those gaps without missing operations.
Maintenance
ActivityMaintained
ResponsivenessNo issues