A structured memory layer for Claude: live state, a full event history, and lessons that compound. One account, every Claude surface.Structured memory for Claude. One account, every surface.
npx -y @clawtex/mcp-serverWorks with Claude Code, Claude Desktop, and any MCP client
Built for the Anthropic Connectors Directory
Claude.ai·Desktop·Mobile·Claude Code
One account. Every surface. Memory follows the conversation.
The problem
You re-explain the same context every session.
Your agent repeats mistakes you already corrected.
Last week's decisions vanish by Monday.
It's not your agent's fault. It has no persistent memory.
The fix
What is true right now. Clients, projects, repos, goals, structured as queryable entities your agent reads at the start of every session. Types form around the way you work, not a fixed schema.
What happened, captured as it happens. Decisions, milestones, blockers, deploys, each one timestamped, typed, and linked to an entity. A full, queryable record across every Claude session.
What to do differently. Clawtex reads your history, finds the patterns you keep repeating, and turns them into structured guardrails with enforcement. Your agent stops making the same mistake twice.
Getting started
Find Clawtex in your Claude settings. Click Connect. Authorize with your Clawtex account. Done. Works on Claude.ai, Desktop, and Mobile.
// Claude.ai / Desktop / Mobile: // Settings > Connectors > Search "Clawtex" > Connect // // OAuth handles authentication automatically. // No config files. No API keys to paste. // // Claude Code (CLI): // claude mcp add clawtex --transport streamable-http \ // --url https://mcp.clawtex.io/api/mcp
Prefer a local MCP server? Add the npm package to Claude Code or Claude Desktop. Same 17 tools, same memory.
// Claude Code / Desktop config:
{
"mcpServers": {
"clawtex": {
"command": "npx",
"args": ["@clawtex/mcp-server"],
"env": {
"CLAWTEX_API_KEY": "tkr_..."
}
}
}
}Start a new session. Your agent loads state, logs events, and updates context automatically. Memory builds with every session.
// State and lessons auto-load at session start. // Your agent also has tools for: // // clawtex_log_event - log decisions, milestones, tasks // clawtex_update_state - track projects, clients, goals // clawtex_get_events - query your full history // // No curl commands. Native tool calls.
Clawtex analyses your event history and extracts lessons from recurring patterns. Each lesson includes numbered correction steps and an enforcement mechanism. Approve or reject. Your agent improves every week.
// From any Claude session: // "Extract lessons from this week's events" // // Clawtex proposes lessons like: // [L001] When deploying code changes // CONTEXT: Skipped visual audit before submission // CORRECTION: // 1. Run full visual audit checklist // 2. Verify all screens on device // 3. Check edge cases before marking complete // ENFORCEMENT: Checklist before submission
Architecture
Most memory tools dump text into a vector store and hope the model retrieves what matters. Clawtex keeps each layer distinct, structured, and queryable, so the right context is there by design, not by chance.
Every session starts from zero. No memory of what happened yesterday, last week, or last month.
Solved by
Bootstrap. One API call at session start loads full structured context. State tells the agent what exists. Events tell it what happened.
The agent makes the same mistakes. Lessons from last month are forgotten. Quality degrades over long horizons.
Solved by
Lessons. Clawtex analyses event history, extracts patterns from recurring mistakes, and injects structured guardrails at every session start.
State tells your agent what exists. Events tell it what happened. Lessons tell it what to do differently. Each layer has a job. Together they compound.
The difference
Before Clawtex
Re-explain context every session
Agent repeats the same mistakes
Decisions lost after compaction
Context resets when you switch devices
No improvement over time
After Clawtex
Agent starts every session with full context
Mistakes caught and corrected automatically
Complete queryable event history
Same memory on web, desktop, mobile, and CLI
Weekly improvement cycle. Extract, approve, inject.
We run our studio on it
“Clawtex is the memory our own studio runs on. Multiple agents, in production, every day, sharing one source of truth. We built it because nothing else held up under real work. Then we opened it up.”
Paul Evans, Founder, Evans Studio
Pricing
Free to start. Upgrade when you need more.