coldstart
Related Servers
Alternatives to coldstart
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent, cross-session memory by saving insights as atomic markdown cards with bidirectional links and recalling relevant ones before new work. Requires no vector database or embeddings, and cards can be shared across clients or synced between devices via git.13 npmISC
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to keep persistent, verifiable memory of a codebase, including the reasons behind code, prior rejected approaches, and invariants, anchored to the code and carried along as the code moves.-
- AlicenseNot gradedqualityAmaintenanceProvides AI coding agents with persistent memory that survives across sessions, letting them recall prior insights before starting work instead of starting from scratch. Knowledge is stored as plain markdown cards with bidirectional links and synchronized via git, requiring no vector database or embeddings.13 npmISC
- AlicenseBqualityAmaintenanceGit-native memory for coding agents, so every session starts warm. Gotchas, decisions, dead ends and bookmarks are saved as plain JSONL in your repo; Claude Code, Cursor and Copilot read them, and teammates get them through git.9396 npm8MIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent cross-session memory by storing atomic markdown knowledge cards with bidirectional wiki-links that agents recall before starting work. Syncs across clients and devices via git without any vector database or embeddings.13 npmISC
- AlicenseAqualityAmaintenanceOne local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.34,875 PyPI1MIT
TDQS
Scored across 8 tools
Each tool has a distinct trigger and output: find is repo-wide discovery, gs is drill-down into a known file, kb_search is fuzzy concept lookup, kb_lookup is exact-path lookup before edits, and kb_write/status/repair/repair_aliases each own a separate notebook lifecycle concern. The superficially similar pairs (kb_search/kb_lookup and kb_repair/kb_repair_aliases) are explicitly contrasted in their descriptions.
The kb_* tools share a clean, predictable prefix and snake_case convention, and find is a readable imperative. gs is an opaque abbreviation that does not fit the pattern, but it is a single isolated exception rather than a systemic inconsistency.
Eight tools is well-scoped for a code-intelligence-plus-notebook server: two navigation/analysis tools and six notebook read/write/maintenance tools. Every tool addresses a concrete workflow step, and the count sits comfortably in the ideal 3-15 range.
The notebook surface is fully covered: create/read/update/delete via kb_write, fuzzy search, exact-path lookup, status, and two repair paths for notes that become unreachable or stale. find and gs cover discovery and structural drill-down, and the only omitted action (git publishing) is intentionally documented as human-only.