eywa-mcp
Related Servers
Alternatives to eywa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory for Claude Code, automatically extracting and surfacing relevant context from past sessions to avoid re-explaining issues and decisions.MIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent codebase memory for Claude Code, enabling semantic understanding of the project structure and action history across sessions to reduce redundant file reads.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides local-first, cross-session memory for Claude Code, enabling semantic search across past sessions to retrieve procedures, decisions, or answers without exposing secrets.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides persistent memory for AI coding agents across sessions by saving and loading session context like tasks, decisions, and blockers.115 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent cross-session memory for Claude Code, enabling it to remember user preferences, decisions, and project context across new sessions.Apache 2.0
- AlicenseAqualityDmaintenancePull Deep Memory from across your Claude Code Sessions — when you need it.158 npm11MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: eywa_extract saves a handoff from a session, while eywa_get retrieves past handoffs. There is no functional overlap.
Both tools follow the same pattern: 'eywa_' prefix followed by a descriptive verb (extract, get). This is consistent and predictable.
With only 2 tools, the surface is minimal. While it covers the core extract and retrieve operations for handoffs, it feels thin; additional management tools like delete or list could be expected.
The tools cover the primary operations of creating (extract) and reading (get) handoffs. Gaps include update and delete, but those may not be necessary for immutable handoffs. Minor missing features like listing all handoffs are partially addressed by querying.