quern
Related Servers
Alternatives to quern
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLets an AI coding agent declare a system's layered dependency graph up front as ghost nodes, then light each node up as code is built and verified, with a live terminal pane showing spinners on active work and red on cracked foundations. It exposes eight mmap_* tools so structural rules — downward-only edges and unique ranks — are enforced as the design ledger.58 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to keep a self-managing rulebook and memory in plain Postgres, turning statements their owner makes in passing into binding rules once stated explicitly, about one client, or twice in distinct contexts within 90 days. Rules are recalled widest-first across a tree of spaces and task kinds with the narrower rule winning, while an append-only fact store tracks confidence, salience, and near-duplicate restatements, and everything added on its own is listed with an undo.MIT
- AlicenseNot gradedqualityCmaintenanceA permissioned memory tree for you and your AI — served over MCP.26 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables agents to store documents and atomic facts with provenance in a local SQLite knowledge base, then search them through fused keyword, exact, semantic, entity, graph and fact retrieval arms that return one ranked list where every result carries its address, trust level and a reason for its rank. A read-only terminal and loopback web view let humans inspect the same searches, timelines, entity neighbourhoods and agent-written pages without being able to alter the knowledge base.-
- AlicenseAqualityCmaintenanceA structured, persistent reasoning workspace for AI. 20 tools for thought chains, branching, revision, search, tagging, and SQLite session persistence that survives context window resets and server restarts.20161 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to navigate users through pre-defined decision trees by submitting answer labels, returning deterministic next instructions without extra LLM calls. Supports domain-independent procedural workflows with state tracking, handling of unknown responses, and a read-only Web UI.MIT
TDQS
Scored across 14 tools
Most verbs have distinct purposes, and the descriptions sharply separate read modes (tree_get, tree_brief, tree_find, tree_roll) from write modes (tree_set, tree_commit). However, tree_solver versus tree_solve and the adjacent semantic tools (tree_vocabulary, tree_rule, tree_solver, tree_package) could cause brief hesitation.
All 14 tools consistently use the tree_ prefix plus a snake_case verb/noun, e.g. tree_get, tree_set, tree_commit, tree_vocabulary. The convention is predictable across reads, writes, checks, and semantic operations.
Fourteen tools are well-scoped for a rich tree workspace covering CRUD, search, validation, atomic commits, semantics, solvers, packages, and UI. Each tool maps to a distinct operational layer without feeling padded.
The surface covers the core lifecycle: read/search, create/update/delete, validation, atomic commit, semantic vocabulary/rules, solvers, and package sharing. Minor gaps exist around explicit move/rename/copy or import/export operations, though these can be approximated with existing set/delete and package tools.