Reasonbook
Related Servers
Alternatives to Reasonbook
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA lightweight, local-first MCP server and CLI that helps developers and AI coding agents store and retrieve lessons learned during development, using SQLite and context-aware filtering.6MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that provides offline-first, persistent memory for AI coding assistants. It captures project decisions and conventions into a local SQLite database and syncs them to tool-specific memory files like CLAUDE.md and AGENTS.md.15 npmMIT
- FlicenseNot gradedqualityAmaintenanceA 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-
- AlicenseBqualityAmaintenanceMCP server providing persistent project memory via SQLite, tracking tasks, decisions, notes, sessions, and context. Includes a Kanban board and session briefs with git activity, enabling LLMs to resume work seamlessly.24153 npm9Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that records decisions, rejected alternatives, and justifications, and retrieves them later to avoid re-litigating past choices. It stores data locally in SQLite and Markdown.263 PyPIApache 2.0
- AlicenseAqualityCmaintenanceMCP server providing structured continuity memory for AI coding agents, tracking decisions, open loops, and session state in local SQLite. Enables agents to resume work from verified state across sessions without replaying transcripts.17Apache 2.0
TDQS
Scored across 15 tools
Each tool broadly maps to a domain, but several orientation/health tools overlap heavily: rbook_review, rbook_agent_onboard, rbook_status, rbook_context's view, and rbook_project's sweep all expose startup/status/queue information. Capture paths for decisions, learnings, next steps, and constraints are split across rbook_session, rbook_decisions, rbook_learnings, and rbook_context, so an agent can hesitate between valid options. Descriptions help, but the multi-action tools keep boundaries fuzzy.
All tools consistently use a snake_case rbook_ prefix with noun-oriented names; there is no camelCase or chaotic mixing. Minor deviations exist: plural nouns like rbook_decisions and rbook_learnings, and a multiword exception like rbook_agent_onboard, rather than a uniform verb_noun scheme.
15 tools is within a reasonable range, and each tool corresponds to a recognizable area such as projects, missions, sprints, context, or DB admin. However, many tools are kitchen-sink interfaces exposing a dozen or more actions, so the effective surface is much larger than the count suggests.
The surface is broad: projects, missions, sprints, context, decisions, learnings, sessions, feedback, auth, messaging, DB admin, onboarding, and review are all covered. Minor gaps remain, such as feedback creation being only indirectly exposed through rbook_agent_onboard's agentFeedback and some lifecycle deletes not being explicit.