ClaudeX
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Path to Claude Code conversation logs | /root/.claude/projects |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_contextA | Get a condensed context snapshot for the current project. Call this at the START of every session to load project memory: recent sessions, favorited sessions, and project stats. This is your primary memory tool — use it before doing any work. |
| list_projectsA | List all Claude Code projects on this machine. Shows which project is currently active. |
| list_sessionsA | List sessions for a project. Defaults to the current project. Pass projectId to target a different project. Use this when the user asks about previous conversations, or when you need to find a specific session. |
| search_conversationsA | Search conversations using full-text search. Defaults to the current project. Set allProjects=true to search across all projects, or pass a specific projectId. Use this when the user asks "did we discuss X before?" or references past work, decisions, or code changes. |
| get_sessionA | Get the full conversation from a session. Defaults to the current project. Use this when you need to read the actual messages from a past session — e.g., to recall implementation details, decisions made, or code that was written. |
| get_session_summaryA | Get a quick summary of a session — title, message count, dates, tags, favorites, and token stats. Defaults to the current project. Cheaper than get_session when you only need metadata, not full messages. |
| store_memoryA | Store a structured memory for the current project. Use this when you discover important codebase patterns, conventions, decisions, or architecture details that should persist across sessions. Memories are stored in SQLite and survive restarts. |
| recall_memoryA | Recall stored memories for the current project. Returns memories sorted by priority and recency. Use this to retrieve codebase knowledge, conventions, decisions, and context from previous sessions. |
| list_memoriesA | List all stored memories for the current project with stats. Shows namespace, type, key, priority. Useful for understanding what knowledge is stored. |
| delete_memoryA | Delete a specific memory by namespace, type, and key. Use when a memory is outdated or incorrect. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| recall | Search your conversation history for something discussed before |
| catchup | Get a summary of recent work in this project |
| history | Browse recent sessions with titles and dates |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects | All Claude Code projects on this machine (current project highlighted) |
TDQS
Scored across 10 tools
Each tool has a clear, distinct purpose. Overlap exists between list_memories and recall_memory, but they serve different retrieval needs (stats vs. priority/recency). Similarly, get_session_summary is a cheaper alternative to get_session. Overall, no two tools are ambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., delete_memory, list_sessions, search_conversations). The pattern is predictable and easy to parse.
10 tools is appropriate for this domain, covering memory management, session tracking, and project awareness. Each tool serves a necessary function without unnecessary bloat.
The tool set covers the core lifecycle of memories (create, read, delete) and sessions (list, read, search, summarize). A minor gap is the lack of an explicit memory update tool, though store_memory can overwrite. Overall, the surface is complete for its stated purpose.