Clarik Mcp Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| clarik_memory_learnA | Extract and store facts from conversation. Strips thinking blocks. Only learns from final assistant responses and user-confirmed facts. |
| clarik_memory_recallA | Retrieve relevant memories ranked by relevance, recency, and importance for the current query. |
| clarik_memory_listB | Show all memories for the current project, optionally filtered by category. |
| clarik_memory_editB | Update a specific memory fact by ID. |
| clarik_memory_clearB | Clear memories by category or clear all memories for the current project. |
| clarik_context_trimC | Intelligent memory injection — returns the most relevant facts and context within a token budget. |
| clarik_checkpoint_saveB | Generate a structured checkpoint of the current session state for resuming later. |
| clarik_checkpoint_resumeA | Load the most recent checkpoint (or a specific one) to resume work. |
| clarik_project_indexB | Build and query a file-to-purpose map for the project. Understands what each file does. |
| clarik_token_monitorA | Estimate token usage for the current session. Warns at 70% context usage. |
| clarik_memory_archiveA | Move stale memories to archive. Keeps active memory lean and fast. |
| clarik_conflict_resolverC | Surface and resolve conflicting memories. Shows both sides for user decision. |
| clarik_change_scope_guardB | Check if a file is protected before editing. Asks for confirmation, never hard blocks. |
| clarik_assumption_checkerB | Flag when Claude is making assumptions instead of asking. Reviews a response for unverified claims. |
| clarik_diff_reviewerB | Review a code diff with structured explanations of each change. |
| clarik_hallucination_detectorA | Cross-check claims against known project files. Uses targeted file list only, never full repo scan. |
| clarik_decision_timelineB | Track and query architectural decisions with dates, reasons, and affected files. |
| clarik_prompt_libraryC | Save and retrieve reusable prompt templates. |
| clarik_session_searchC | Full-text search across past session data. |
| clarik_export_sessionB | Export session data to ./clarik-exports/ directory. Never exports to ~/Downloads. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| clarik-session-start | Load project context and recent memories to start a Clarik-enhanced session. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| clarik-memory |
TDQS
Scored across 20 tools
Each tool has a clearly distinct purpose, from memory operations (learn, recall, edit) to session management (checkpoint, export) and quality checks (hallucination detector, assumption checker). There is no ambiguity or overlap in their descriptions.
All tools follow a consistent pattern with the prefix 'clarik_' followed by a descriptive noun or verb-noun combination in snake_case (e.g., clarik_memory_learn, clarik_diff_reviewer). No mixing of conventions.
20 tools is on the higher end but justified by the server's broad scope covering memory, sessions, quality checks, and project indexing. Each tool serves a specific, non-redundant function.
The toolset covers memory lifecycle (save, edit, clear, archive, recall), session management (checkpoint, export, search), and quality assurance (hallucination, assumption, diff review). Minor gaps like undo for memory edits are present but not critical.