never4ga-mcp
OfficialRelated Servers
Alternatives to never4ga-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables people and AI assistants to share one persistent Markdown-in-Git memory, so any MCP client can load current context, save sessions and decisions, search notes, and work from a team's real knowledge across machines.AGPL 3.0
- AlicenseAqualityCmaintenanceProvides AI coding agents with a local, Markdown-first shared memory, enabling them to record decisions, failures, progress, and handoffs and retrieve them across sessions via MCP tools.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain lossless, queryable long-term project memory through local SQLite storage, bi-temporal history, hybrid retrieval, and Git-backed Markdown mirrors, exposed via MCP tools and resources.131 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.MIT
- FlicenseNot gradedqualityBmaintenanceA local-first MCP server and CLI that gives coding agents structured project memory, task contracts, context packs, backlog workflows, and verification evidence, storing data in reviewable Markdown/YAML with a fast SQLite index.4-
- AlicenseAqualityBmaintenanceUnifies cited transcript search, auto-compressed session context, and hand-curated notes behind a single MCP server, letting AI coding agents look up past discussions, check what was just happening, and store or recall durable facts across projects.7MIT
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose: session lifecycle (startup, checkpoint, wrap), vault retrieval (search, get_concept, context_focus), and work tracker operations (search, get, create, update, comment) are separated by domain prefixes and descriptions. Overlap is minimal, and the descriptions clarify boundaries.
All tools share the never4ga_ prefix and snake_case, which makes them groupable, but the action ordering varies: some use noun_verb (work_get, workspace_resolve), others verb_noun (get_concept), and several are bare verbs/nouns (wrap, decide, search). This is mostly consistent with minor deviations.
15 tools is at the upper end of the ideal range, but each tool maps to a distinct operation in session management, vault access, and work tracking. The set is well-scoped with no obvious redundancy.
Core lifecycle and retrieval workflows are covered, including session start/checkpoint/wrap, vault search and concept retrieval, and work item create/read/update/comment. Minor gaps exist (e.g., no work item delete or direct concept update/delete), but these may be intentional or manageable via other tools.