Session Buddy
Related Servers
Alternatives to Session Buddy
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides long-term memory and lossless context management for Claude Code, enabling automatic context compression, cross-session memory sharing, and semantic search across all history.10MIT
- FlicenseNot gradedqualityCmaintenanceProvides persistent local memory of Claude Code sessions with TODO management and searchable activity logs via MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code sessions to automatically capture and retrieve architectural decisions, code changes, bug fixes, and configuration context across sessions using local SQLite storage and hybrid semantic/keyword search.49 PyPI1MIT
- AlicenseAqualityDmaintenanceProvides Claude Code with programmatic session awareness to track context usage, session history, and task progress. It enables intelligent context reset recommendations and automatic synchronization of project planning documentation.5MIT
- AlicenseNot gradedqualityBmaintenanceGives Claude Code a persistent, fully local long-term memory by automatically capturing session activity, indexing past conversations, projects, scheduled tasks and Obsidian notes, and recalling relevant context through hybrid keyword-plus-semantic search with progressive disclosure. It also writes session handoffs that are injected into later sessions, so work resumes with prior decisions and next steps already in context.58 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory for Claude Code, automatically extracting and surfacing relevant context from past sessions to avoid re-explaining issues and decisions.MIT
TDQS
Scored across 6 tools
The tools have overlapping purposes that could cause confusion, particularly between analyze_code and the more specific tools like check_complexity and check_coupling. While descriptions clarify their focus, an agent might struggle to choose between analyze_code (which includes complexity and coupling) and the dedicated tools, leading to potential misselection.
All tool names follow a consistent verb_noun pattern (e.g., analyze_code, check_complexity, detect_clones), using snake_case throughout. This predictability makes it easy for agents to parse and understand the naming conventions without confusion.
With 6 tools, the count is well-scoped for a code analysis server, covering key aspects like complexity, coupling, clones, and dead code. Each tool appears to earn its place without feeling excessive or insufficient for the domain.
The tool set provides good coverage for code quality analysis, including metrics, clone detection, and dead code. A minor gap exists in areas like code style or security analysis, but agents can likely work around this with the available tools for core workflows.