Clay Memory System - MCP Server in JavaScript with Python Bridge. Robust stdio handling for Windows + Python bridge with support for claude/, projects/, misc/ tale structure
Clay MCP Server exhibits significant gaps in tool definition quality. While 17 tools are registered with names, descriptions, and basic schemas, the quality is inconsistent. Naming follows action-verb conventions reasonably well (remember, recall, classify_cxd, reflect, etc.), but several tools lack clear, actionable descriptions (e.g., 'reflect', 'bootstrap_synthetic_memories', 'debug_python', 'analyze_memory_patterns' have generic or vague descriptions). Parameter documentation is sparse, many tools have undescribed inputs or rely on implicit semantics. Output schemas are not documented at all in the visible source. Error handling guidance is absent. The Python bridge architecture and memory transplant/direct insert operations suggest complex state manipulation, but descriptions do not warn about side effects or recovery procedures. Most tools score in the 30-50 range; a few (remember, recall, context_tale) reach 50-60 due to slightly better schema completeness.
Analyze patterns in memory usage and content
Load foundational synthetic memories
Classify text using CXD cognitive framework
Generate fluid narratives from memory fragments - perfect for onboarding new Claude instances
Create a new personal autobiographical tale (v2.0: claude/, projects/, misc/)
Debug which Python interpreter is being used
Delete a memory with contextual analysis and confirmation
Output schemas are not documented. Tools have input schemas but no visible documentation of returned fields, structure, or types. LLMs cannot predict what data is returned or how to chain tools.
Destructive operations (delete_memory_guided, memory_transplant, direct_insert) lack confirmation/dry-run patterns and do not describe error recovery steps. No guidance on how to undo or verify before execution.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 43 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 22 | - | v1 |
Direct insert memory in specific ID slot
Transplant memories to fix ID sequence holes
Search and retrieve relevant memories
Search memories with CXD cognitive filtering
Trigger offline reflection and pattern analysis
Store information in persistent memory
Engage in Socratic self-questioning
Get Clay system status and statistics
Process input with full contextual memory
Update a memory with contextual guidance and Socratic questioning
Vague or missing descriptions on 8 tools: 'reflect', 'status', 'bootstrap_synthetic_memories', 'analyze_memory_patterns', 'debug_python', 'memory_transplant', 'direct_insert' have descriptions under 50 characters or lack actionable WHEN/WHY guidance. LLMs cannot determine when to invoke these tools.
Parameter documentation is incomplete. 'status', 'reflect', 'bootstrap_synthetic_memories', 'analyze_memory_patterns', 'debug_python', 'memory_transplant', 'direct_insert' have empty input schemas ({}), providing no guidance on what they accept or what side effects they have.
No error handling guidance. Tools do not describe retryability, expected failure modes, or recovery steps (e.g., what if Python bridge crashes, what if memory store is corrupted). Error messages will not guide LLM recovery.
Complex multi-tool workflows (memory_transplant, direct_insert, update_memory_guided, delete_memory_guided) lack clear composition guidance. No documentation of what IDs/references are needed or what fields are returned to enable chaining.
Python bridge dependency is not self-documenting in tool descriptions. It is unclear from tool metadata that calling these tools spawns child Python processes, which could fail, hang, or timeout. No guidance on performance, latency, or failure modes.
No enumeration constraints on memory_type, function_filter, or style parameters. 'memory_type' accepts 'interaction, reflection, synthetic, socratic, golden, milestone, etc.', 'etc.' is not actionable. LLMs will guess invalid values.