
Clarik Mcp Server
Persist workspace clarity and memory across Claude sessions so long-running solo projects do not lose decisions and context.
Overview
clarik-mcp-server is an MCP server for the Build phase that provides persistent clarity and memory as a workspace context manager for Claude.
What is this MCP server?
- Persistent workspace context manager for Claude
- Clarity and memory focus across sessions
- npm package clarik v0.1.1 with stdio MCP transport
- GitHub: Mikerichardmail/clarik-mcp-server
- Lightweight add-on for multi-day agent coding workflows
- Version 0.1.1
- Transport: stdio
- npm identifier: clarik
Community signal: 1 GitHub stars.
What problem does it solve?
Long Claude coding sessions lose thread when workspace decisions and memory reset every time you open a new chat.
Who is it for?
Solo builders running extended Claude Code projects who want session-spanning memory without building a custom vector store first.
Skip if: Teams that already centralize truth in Notion or Linear with strict sync requirements and do not want another context layer in the agent.
What do I get? / Deliverables
Claude can draw on persisted workspace context so you spend less time re-briefing and more time shipping features.
- Stdio MCP server for workspace clarity and memory
- Persisted context usable across Claude sessions
- Reduced re-briefing overhead on long build cycles
Recommended MCP Servers
Journey fit
How it compares
Claude workspace memory MCP, not a full RAG pipeline or team knowledge base product.
Common Questions / FAQ
Who is clarik-mcp-server for?
Indie developers using Claude who need persistent workspace context and memory across coding sessions on one product.
When should I use clarik-mcp-server?
Add it during build when multi-day agent work makes you repeat specs, architecture, or decisions that should stick in the workspace.
How do I add clarik-mcp-server to my agent?
Install the npm package clarik, configure the stdio MCP server in Claude Desktop or Claude Code, and connect it to your workspace per the GitHub README.