Lex
Give Claude Code or Cursor durable episodic memory and workspace policy so multi-session agent work stays coherent.
Overview
Lex is an MCP server for the Build phase that stores episodic memory and workspace architectural policy for AI coding agents via Frames, Atlas, and Policy.
What is this MCP server?
- Episodic Frames for what happened across sessions
- Atlas for architectural/context mapping in the workspace
- Policy layer for enforceable agent behavior in the repo
- Local SQLite store via LEX_MEMORY_DB under workspace root
- stdio npm package @smartergpt/lex-mcp v2.1.2
- Server version 2.1.2
- npm package @smartergpt/lex-mcp with stdio transport
- Three conceptual surfaces: Frames, Atlas, and Policy
What problem does it solve?
Agents forget prior sessions and ignore informal architecture notes, so you re-explain the same constraints every time you open a new chat.
Who is it for?
Solo builders running long-horizon agent sessions on one repo who want on-disk memory and policy without a cloud memory product.
Skip if: Teams that only need one-off answers with no persistence, or anyone who cannot run a local stdio MCP process with Node/npm.
What do I get? / Deliverables
After registering Lex, your agent can recall framed episodes and apply declared policy against a local SQLite memory DB rooted in your workspace.
- Local episodic memory store for agent sessions
- Atlas-linked architectural context in the workspace
- Policy-guided agent behavior aligned to repo rules
Recommended MCP Servers
Journey fit
Memory frames, Atlas, and Policy attach where you wire and run coding agents, before you depend on the model alone to remember architecture decisions. Agent-tooling is the canonical shelf for MCP surfaces that shape how assistants remember and obey repo-level rules.
How it compares
Persistent agent memory MCP, not a generic documentation skill or hosted task board.
Common Questions / FAQ
Who is Lex for?
Indie and solo developers using Claude Code, Cursor, or other MCP clients who need cross-session memory and repo policy for agent work.
When should I use Lex?
Use Lex while building or operating agent-heavy projects when architectural decisions and past episodes must survive chat resets.
How do I add Lex to my agent?
Install @smartergpt/lex-mcp from npm, set LEX_WORKSPACE_ROOT (and optionally LEX_MEMORY_DB), add the stdio server entry in your MCP config, then restart the client.