caprock
Related Servers
Alternatives to caprock
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for reading Claude Code session history from the local filesystem, exposing project and session data to MCP-compatible clients.657 PyPIMIT
- AlicenseAqualityDmaintenanceMCP server for local-first project memory, enabling AI agents to log, search, and retrieve structured project history, summaries, and per-file dossiers with client-specific configuration and diagnostics.151MIT
- FlicenseNot gradedqualityCmaintenanceCentral MCP server for storing and querying lessons learned and project-specific implementation details, compatible with MCP-capable AI clients like Cursor, Claude Code, and Google Antigravity.-
- FlicenseNot gradedqualityBmaintenanceMCP server that indexes local Claude Code transcripts and provides keyword, phrase, semantic, and date-range search, plus full context/session recall.-
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server that lets clients list recent opencode sessions and render any session's full transcript — metadata, messages in seq order, and tool calls with outputs — as clean Markdown straight from opencode.db.MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables Claude session to retrieve full project context in a single call by listing projects, reading per-project handoffs, searching the local knowledge base and indexed code, recording cross-project lessons, and rebuilding the searchable rollup — all from a fully local store.MIT
TDQS
Scored across 12 tools
Most tools target clearly distinct resources: sessions (recent_sessions, session_summary, session_prose), memories (search_memories, get_memory, current_decisions, memory_topics), and diagnostics (loop_alerts, cost, ci_status). The only confusable pairs are search_prose vs session_prose (cross-session search vs one-session read) and recent_sessions vs session_summary (list vs detail), but the descriptions explicitly differentiate both.
Two conventions coexist: noun-phrase names (ci_status, cost, loop_alerts, recent_sessions, session_summary, memory_topics, current_decisions, next_session_handoff) and verb_noun names (search_prose, search_memories, get_memory). The verb tools are internally consistent, but the overall set mixes styles, and bare `cost` is noticeably vaguer than its siblings.
Twelve tools is squarely in the well-scoped range, and each one maps to a distinct question an agent would ask about sessions, spend, CI, or stored memories. Nothing appears redundant enough to cut.
The read surface is broad: session lifecycle (list, detail, prose, loops, cost, CI, handoff) and memory retrieval (search, full read, topics, in-force decisions) are both covered. Gaps are minor and likely intentional for an observability server — no way to write a memory, record a decision, or enumerate projects directly.