Other · Local MCP server
Lex
Episodic memory, Frames, Policy Neighborhoods, and policy enforcement for AI agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.smartergpt/lex- Version
- 4.4.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-18
- Updated
- 2026-09-18
- Publisher
- dev.smartergpt · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain smartergpt.dev · how
- Repository
- github.com/SmarterGPT/lex
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @smartergpt/lex-mcp | 4.4.1 | stdio |
How to connect Lex
Lex runs locally from a Node.js package published to the npm registry: @smartergpt/lex-mcp version 4.4.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @smartergpt/lex-mcp@4.4.1. It reads these environment variables: LEX_WORKSPACE_ROOT, LEX_STORE, LEX_DB_PATH, LEX_MEMORY_DB, LEX_DATABASE_URL (secret), LEX_POSTGRES_PASSWORD (secret), LEX_POSTGRES_POOL_MAX and LEX_DEBUG; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lex": {
"command": "npx",
"args": [
"-y",
"@smartergpt/lex-mcp@4.4.1"
],
"env": {
"LEX_WORKSPACE_ROOT": "<value>",
"LEX_STORE": "<value>",
"LEX_DB_PATH": "<value>",
"LEX_MEMORY_DB": "<value>",
"LEX_DATABASE_URL": "<secret>",
"LEX_POSTGRES_PASSWORD": "<secret>",
"LEX_POSTGRES_POOL_MAX": "<value>",
"LEX_DEBUG": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from dev.smartergpt
| Server | Runs |
|---|---|
| AXFAgent eXoskeleton Framework control plane for workspace-native agent capabilities over MCP. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| Let Agents InScan agent readiness, or find measured providers an unattended AI agent can finish with. | Remote · HTTPLive check: ✓ handshake |
| LetmepostMCP server for letmepost.dev. Publish across 8 social platforms from any agent. | Local · stdio |
| LetterboxFile-based comms protocol for AI-to-AI dialogue between terminal agents. | Local · stdio |
| Level MCPEvery Level RMM endpoint, plus a local SQLite fleet store and offline cross-entity rollups no Level. | Local · stdio |
| LexIA Juris (EDIVIA)MCP droit & fiscalite francais: 76 codes, jurisprudence, BOFiP. LexIA Juris, EDIVIA. Abonnement. | Remote · HTTPLive check: sign-in required |
| LexIA Pro (EDIVIA)MCP foncier & urbanisme officiels francais (cadastre, PLU, DVF). LexIA Pro, EDIVIA. Abonnement. | Remote · HTTPLive check: sign-in required |
| LexilintOffline spell checker + BYOK grammar for AI assistants. Works with Claude Desktop, ChatGPT, Cursor. | Local · stdio |
| Leximo Ai Call Assistant MCP ServerSchedule AI phone calls, manage assignments, and check credits from Claude. | Local · stdio |