Episodic memory and architectural policy for AI agents. Frames, Atlas, and Policy.
Episodic memory and architectural policy for AI agents. Frames, Atlas, and Policy. Exposed over MCP by the lex mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Your agent can read the code. Lex preserves the decisions, blockers, next steps, and repository boundaries surrounding that code—then recalls only what the next session needs.
The server ships on npm as @smartergpt/lex, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
Project — ResponsibilityLex — Durable work context, repository policy, optional neighborhood context, instructions, and scoped Frame storageYou will need 4 environment variables: LEX_DB_PATH, LEX_POLICY_PATH, LEX_DB_KEY, LEX_DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Lex's toolset — Project, Lex — is a fair guide to whether it matches your workflow. It is maintained by dev.smartergpt; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Project | Responsibility |
| Lex | Durable work context, repository policy, optional neighborhood context, instructions, and scoped Frame storage |
{
"mcpServers": {
"lex": {
"command": "npx",
"args": ["-y", "@smartergpt/lex"],
"env": {
"LEX_DB_PATH": "your-value",
"LEX_POLICY_PATH": "your-value",
"LEX_DB_KEY": "your-value",
"LEX_DATABASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| LEX_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| LEX_POLICY_PATH | Filesystem location the server is allowed to use. | Optional |
| LEX_DB_KEY | Credential the server authenticates with. | Yes |
| LEX_DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.